The reasons customers might have not to move to Office 365…
Although Office 365 offers a great amount of benefits to almost all customers, not all customers will want to move to the cloud for their E-mail solutions or SharePoint environments. Some of the reasons why somebody might not want to move to a cloud environment is because of the basic principles of the cloud and regarding Office 365 a Software as a Service Solution in particular.
- All services are highly configurable, not customizable. With Microsoft software that is installed on premise you can change almost everything in the environment. Next to this it is possible to implement add-ons in the environment or install fully trusted code which basically modifies On Premise Software. Because thousands of companies use the same environment with Office 365, it is not possible to customize a single environment. This shared environment by the way is the reason Microsoft van offer these cloud services against such an interesting price.
- Services are run under the security policies governed by Microsoft: Microsoft has determined the security policies under which all services run. These security policies are the same for each customer and cannot be changed for individual customers. Security probably is one of the most important assets Microsoft can offer in the cloud. If Microsoft cannot guarantee safety, who would want to use their services?
- Microsoft can transfer data between data centers: Data stored in Microsoft’s data centers can be moved around between the different data centers by Microsoft. Microsoft will keep data safe according to the Safe Harbor agreement (for EU customers).
- Customers cannot audit the environment: Customers nor third parties assigned by customers can audit the Microsoft environment. Microsoft has assigned several auditing organizations who produce documents regarding the environment. Individual auditing requests are not granted.
- The liability of Microsoft is capped: The total liability of Microsoft is capped at 12 months.
- Customers must remain current: Customers must remain current to the new versions introduced by Microsoft. This is the case for all minor releases at release date of a specific feature. Because releases of specific features within a minor release typically don’t interfere with the overall availability/functionality of an environment this should not be a problem. The requirement a customer must remain current however also is the case for major releases. In this case a customer typically will get 12 months to ‘adopt’ the new version.
- Microsoft sets release timing and retires features: Microsoft determines which features will be release at which specific date and act accordingly.
- The deployment life cycle and Microsoft’s release timing need to fit each other: The internal customer deployment life cycle and the deployment life cycle which Microsoft uses need to fit each other. With Office 365 for example Windows XP is no longer supported. Customers should have moved away from Windows XP before they will want to adopt Office 365.
Do you have any other reasons? Please let me know!