![]() ![]() We’re now at the point where the majority of Exchange and SharePoint activity is cloud-based, and the number of on-premises customers for Office servers continues to fall year over year. Microsoft has increased quotas for Exchange Online and SharePoint Online (for instance, the standard enterprise mailbox is now 100 GB instead of 25 GB) and many ISVs make products to help customers move data from on-premises apps into the cloud. The Office 365 datacenters store enormous amounts of user data. Tenants can run a multi-geo configuration for Exchange Online, SharePoint Online, and OneDrive for Business, and Microsoft is steadily moving app data closer to customers as it builds out its datacenters. The datacenters are connected by a dark fiber network linked to a huge set of local connection points to make it easy for users to work no matter where they are. Where Microsoft had three datacenter regions in 2011, it now delivers Office 365 services from 17, a development that resolved the initial fears some customers had about data sovereignty. The Office 365 ecosystem also needed to be built out. Microsoft’s engineering groups were still working out how to transform the on-premises software to work at cloud scale, and it’s fair to say that this process didn’t finish until a few years later. The software was based on the 2010 on-premises versions of Exchange, SharePoint, and Lync knitted together with a licensing and administration portal. ![]() Looking back from today’s perspective, it’s hard to remember just how limited Office 365 was in 2011. In the next, I describe some of the Office 365 successes and failures in the last decade. In this article, I look back at the roots of Office 365 and discuss the three major issues that initially spooked customers about the cloud. ![]() After a slow start, Office 365 has gathered pace and overcome G Suite, its major rival to become the leader in cloud office systems. Thankfully, Microsoft transformed its cloud office system with the introduction of Office 365 on 28 June 2011. Because BPOS used software designed for on-premises use, it struggled to cope with cloud operations. BPOS was unreliable and didn’t work particularly well. At the start of the decade, Microsoft’s cloud offering was the deservedly maligned Business Online Productivity Services (BPOS: a name only its inventor could love). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |