Workloads and scenarios-Describe Microsoft 365 apps and services

Once the Microsoft 365 infrastructure is in place, administrators can implement the workloads and scenarios that utilize its services. The workloads of Microsoft 365 typically involve Microsoft Teams, Exchange Online, and SharePoint. The deployment process for each workload consists of three phases, as follows:

• Envision Assemble a team representing the enterprise΄s business, IT, and user interests. Then, brainstorm and prioritize the scenarios in which the organization will make use of the capabilities the service provides.
• Onboard Prepare a detailed plan for the service rollout, including any necessary account creation and data migration planning and whether help from Microsoft’s FastTrack program will be needed. Then, create a pilot deployment, preferably including some or all the representatives involved in the envision phase.
• Drive value Deploy the service to the rest of the enterprise, encourage its adoption as needed, and carefully monitor activity reports and user feedback to determine the success of the deployment.

Once the Microsoft 365 workload services are in place, administrators can develop scenarios that utilize them, such as implementing data protection technologies and building team websites.

Identify deployment and update channels for Microsoft 365 apps

There are several ways to install the Microsoft 365 productivity applications in a Microsoft 365 deployment, but they all should be preceded by a preliminary assessment and planning process. The assessment consists of a review of the target workstations with regard to the system requirements for Microsoft 365, languages, licenses, and compatibility with other applications.

In the planning stage of the deployment, administrators must make decisions such as the following:

• What deployment tool to use
• What installation packages will be needed
• Where the source files will be located (cloud or local source)
• Which update channel the workstations should use

In some cases, these decisions will vary for different parts of the enterprise, depending on the workstation equipment used, the availability of Internet connectivity, and the administrative personnel available.

Note Creating a Pilot Deployment

Whichever deployment method an organization uses, Microsoft’s best practices recommendations call for creating at least two separate Microsoft 365 deployment groups, such as a pilot group and a broad group. Depending on the deployment method, this will call for creating two or more collections or ODT scripts. Administrators should deploy the pilot group first and test it for compatibility before deploying the broad group.