This month, February 2016, is when more users are starting to get the Office 2016 apps as part of their Office 365 ProPlus subscriptions.
A quick refresher on Microsoft's new Office-as-a-service delivery model: Last fall, Microsoft execs said the company was making changes to the Office update model that would parallel, in many ways, how the company is updating Windows 10. As with Windows 10, Office updates and security fixes would be available at different frequencies depending on which "branch" of which users were part.
Office Current Branch subscribers -- both consumer (Home and Personal) and new business customers -- are on tap to receive Office updates and security fixes monthly. But Office 365 business users on the Current Branch for Business (CBB) will get updates and fixes three times per year, officials announced last fall.
If administrators have configured their users to get updates directly from the Office Content Delivery Network on the Internet, the Office 2016 upgrade will begin this month and Office 2016 files will be automatically downloaded to users' computers. (Admins can block this by using the Office Deployment Tool or Group Policy and the Update Path policy setting.) Those who've configured users to get updates from their internal networks have more control as to when Office 2016 will be rolled out to those with Office 365 ProPlus.
Office 365 ProPlus, at $12 per user per month, includes the ability to install Word, Excel, PowerPoint, Outlook, OneNote, Project, Access and Skype on up to five PCs or Macs, plus use Office on up to five additional smartphones and tablets.
In other Office 365 Pro Plus news of potential interest, Microsoft has just changed the requirements for customers and hosting companies who want to deliver Office to multiple users sharing the same hardware. Microsoft is now allowing hosting partners who are first tier Microsoft Cloud Solution Provider (CSP) participants to deploy multi-tenant remote desktop workloads with Office 365 ProPlus and/or E3, E4 or E5 SKUs on premises or in Azure. Before now, these workloads could only be run on-premises with dedicated hardware.