@Eastridge when we partner with our #Enterprise customers on a migration to Office 365 there are always risks that arise during the project. Communicating them early and across the entire project team helps us mitigate project delays and ensures a successful partnership with our customers.
Here are a few of the risks that we have encountered in the wild.
- Exchange 2003 out of the environment and removed from Active Directory.
- Project priority has not been appropriately communicated with IT Staff and the end user community. Migrating to Office 365 is an Enterprise level effort.
- ADFS Network load balancing. Using software load balancing on Virtualized Servers can require additional Hypervisor configuration. Go Hardware.
- Project team members not available for or have limited time for project working sessions, training and requirements gathering.
- Legacy OCS removed, federated or decommissioned.
- LCS removed from Active Directory.
- Delay in hardware or Virtual resources required to complete the project on premise foundations.
- Lack of documentation or knowledge relating to Active Directory, Enterprise Network and / or Infrastructure components required for an Office 365 project.
- Integration issue arising from un-patched machines and / or unsupported operating system configuration of end-points.
- Certificates needs.
- Current requirements dictate that the Exchange Hybrid server version must be 2010 SP3 or higher. 2013 recommended.
- Office 365 Pro Plus is not supported on Windows XP.
- .Net 4.x framework deployed were required.
- Up to date Windows End Points including Critical Security Fixes, Office 365 optional patches (Desktop Setup) and additional optional patches. (Eastridge and customer to determine).