Like Windows Enterprise, Microsoft 365 Apps makes use of the concept of update channels. Update channels determine the update schedule for endpoints. There are currently three update channels:
- Current Channel: Current Channel receives updates at a monthly cadence, including both feature, performance, and security updates. Microsoft recommends configuring a very small percentage of your user base to subscribe to Current Channel to test upcoming features. Current Channel is not recommended for business users who have a heavy reliance on macros, app integrations, or third-party add-ins as part of their daily work. Current Channel builds are supported until the next release. While Current Channel is typically updated once a month, the deployment date varies.
- Monthly Enterprise Channel: Monthly Enterprise Channel is recommended for users that want the newest features and are willing to provide feedback to Microsoft regarding new features. Like Current Channel, Monthly Enterprise Channel is not intended for broad deployment and should be limited to a very small percentage of your user base. Monthly Enterprise Channel builds are released on the second Tuesday of the month. Unlike Current Channel, however, they are supported for two release cycles.
- Semi-Annual Enterprise Channel: Semi-Annual Enterprise Channel is the default and recommended channel for Microsoft 365 updates. Users in this channel will receive feature updates twice a year (in January and July). These updates will include new feature updates that have been made available in Monthly Enterprise Channel. Critical security updates are deployed during the normal monthly security update release cycle, however. Microsoft recommends configuring most of your users for this channel, including users that rely on plugins and complex macros. Semi-annual releases are supported for 14 months.
Now that you understand some of the deployment options, let’s look at some deployment options.
Implementing Microsoft 365 Apps deployment
So far, you’ve learned about the requirements for Microsoft 365 Apps, as well as the servicing and configuration options. In this next section, we’ll talk about deployment methodologies and then work through a sample deployment.
Deployment methods
Microsoft 365 Apps uses Click-to-Run (C2R) packaging. There are five deployment options available, each with advantages and requirements:
- Self-install: With this option, users can self-deploy Microsoft 365 Apps on their workstations by using the Download link on the Microsoft 365 portal (https://portal.office.com).
- Deploy from the cloud with the Office Deployment Tool (ODT): Administrators can use Microsoft’s ODT to deploy Office from the Office CDN. In this scenario, administrators already have management of end user devices. An administrator can connect the client devices to the Office CDN using the ODT for distributing media. The ODT will allow IT administrators to manage Microsoft 365 App options such as languages, update channels, and selected products (for example, excluding Word or including PowerPoint).
- Deploy from a local source using the ODT: Using a local source for installation media, administrators can use their infrastructure to create a local source repository to store the latest Office updates and services. This reduces the need for managed endpoints to individually download files over the internet. The ODT is used to manage which configurations are delivered to endpoints.
- Deploy from a local source with Configuration Manager: Finally, if organizations have a current version of Microsoft Endpoint Configuration Manager (formerly System Center Configuration Manager), they can use it to deploy and update Microsoft 365 Apps.
- Deploy from the cloud using Microsoft Intune: Microsoft’s recommended solution is to use Intune inside of Microsoft Endpoint Manager to deploy and manage Microsoft 365 Apps.
Once you have selected an update and servicing cadence for Microsoft 365 Apps, you’ll need to decide on how to deploy the software to endpoints, as well as any customization.