Deploy Microsoft Teams for Microsoft 365 Enterprise

This workload is included in both the E3 and E5 versions of Microsoft 365 Enterprise

Microsoft Teams brings together chat, conferencing, document sharing, and threaded conversations in a way that makes it easy to create and share content across groups. Teams is the way you do teamwork and collaboration for Microsoft 365 Enterprise and is a key element of the Built for Teamwork value of Microsoft 365. If you are brand new to Teams, see Overview of Microsoft Teams.

If you’re currently using Skype for Business, we’re building Skype for Business capabilities into Teams. This will happen over time, and ultimately Teams will become the single client experience. As a valued Skype for Business customer, Microsoft is here to support you. See the Journey from Skype for Business to Microsoft Teams for more information.

The following phases and steps guide you through the process of envisioning the role of Teams in your organization, onboarding your organization to Teams through a series of progressive rollouts, and driving usage of Teams and its value to your end users.

Before you begin, make sure you've configured the right foundation infrastructure phases so that your teams have the security capabilities you need.

Phase 1: Envision

In this phase, you gather the people for your Teams deployment and determine how your organization will use Teams to address its business needs.

Step 1: Gather your Teams deployment members

For a successful deployment of Teams on top of the Microsoft 365 foundation infrastructure, you need to get the right people for input and feedback. Key people include business decision makers, IT staff such as architects and implementers, and advocates for your end users.

These three groups ensure that your Teams deployment includes considerations that address business needs, technical aspects of licensing and security, and that Teams will be something that your typical users will use.


A list of people that represent the business, technical, and end user aspects of your organization.

Step 2: Determine and prioritize your Teams business scenarios

Teams can be used for many different purposes. You need to figure out which purposes map to your business needs on the separate levels of your organization, your business groups, your departments, and individual working and project teams. Take a look at the Microsoft 365 Productivity Library for examples to help you define Teams scenarios.

You should target Teams to address fast-moving and highly collaborative teams that work closely together and require many more facilities than just email with Exchange Online can provide. Examples are live group chats with a recorded history and a common and easy-to-find place to store files and notes.

One way to see the benefits of Teams is to examine how a team or v-team interacts today, and then find an appropriate Teams scenario that replaces the interaction and provides easier ways to collaborate and provide additional capabilities.

Teams enables these strategic business scenarios for Microsoft 365 Enterprise:

  • Communicate with your team to stay informed, solicit input, and build cohesion and consensus
  • Engage your firstline workers to enable your Digital Transformation
  • Understand your work habits to improve your influence and impact

For more information, see the Digital transformation using Microsoft 365.

Microsoft Teams for highly regulated data

Highy regulated data is subject to regional regulations or is the most valuable data for your organization, such as trade secrets, financial or human resources information, and organization strategy. You can configure a team for restricted access, data classification, data loss prevention, and encryption for this type of data. For the details, see Microsoft Teams and SharePoint Online sites for highly regulated data.


A list of Teams scenarios that address your organization’s needs for collaboration and teamwork.

Phase 2: Onboard

In this phase, you plan for the technical aspects of a Teams deployment and start rolling out Teams to selected groups of users.

Prerequisites: Identity and device access configuration

To protect access to teams, ensure that you have configured identity and device access policies and the recommended SharePoint Online access policies.

Step 1: Complete your technical planning

Before you begin technical planning, determine whether you want to use FastTrack. If your organization has over 50 seats and is participating in an eligible plan, you can use FastTrack for Microsoft 365, available at no additional cost to guide you through planning, deployment and service adoption. Or, you can complete this work yourself using our FastTrack Onboarding Wizards, which are available from FastTrack once you sign in with your Office 365 account.

If you are doing your own planning (or in conjunction with FastTrack), you need to determine if your network and organization are ready for Teams. It is especially important that you meet the exit criteria for networking in your foundation infrastructure, with special attention to bandwidth, throughput, and traffic delays to maximize performance for Teams-based meetings.

Use these resources to prepare the technical aspects of your organization for a Teams rollout:

For a better understanding of security in Teams, review the following additional resources:

Next, use these resources to understand Teams licensing and to perform the setup of Teams for your organization:


Your network, security, and Office 365 licensing planning is done and you are ready to begin rolling out Teams to selected groups in your organization.

Step 2: Run an IT pilot

In most medium-sized and large organizations, you should run an IT pilot with your stakeholders from Phase 1 and early adopters and technical enthusiasts. During the IT pilot:

  • Choose a Teams business scenario in which your IT pilot participants can practice. See the Microsoft Teams getting started kit for ideas.
  • Give your pilot participants a set of exercises to test Teams-based chats, file storage, meetings, and other capabilities.
  • Determine your change management strategy and produce materials to drive organization-wide user adoption. Change management materials can include email announcement text, internal training plans, hallway posters, and presentations. These materials will inform your organization about Teams and its benefits with the goals of raising awareness and driving usage. See change management strategy for Microsoft Teams for some ideas.
  • Have your IT pilot participants review the change management strategy materials based on their experiences. They can provide tips on best practices and advice on how to best describe the benefits of Teams and how to use it for collaboration and teamwork.


Your Teams IT pilot is complete and the initial change management materials have been developed, reviewed, and refined.

Step 3: Roll out to a business group

After completing your IT pilot, roll out Teams to a business group or department in your organization. This rollout should include:

  • Identification of key business scenarios for Teams within the business group.
  • Announcement activities to inform users of the expectations and timelines for Teams usage for departmental, work, or project teams.
  • Direct user training on Teams or links to resources to introduce Teams and how to use it.
  • A feedback mechanism, such as a central team containing everyone in the business group, to collect comments and issues from users in the business group.

During the rollout, you can refine your change management materials in preparation for the organization-wide rollout.


A business group is up and running with Teams and the change management materials have been tested and refined.

Phase 3: Drive value

In this phase, you complete the rollout of Teams to your organization and support your users so that they are realizing its benefits.

Step 1: Roll out Teams to the rest of your organization

After completing your rollout to a targeted business group, roll out Teams to the rest of your organization. This rollout should include:

  • Identification of key business scenarios for Teams within your separate business groups.
  • Use of your refined change management materials for announcement activities to inform your organization of the expectations and timelines for Teams usage for departmental, work, or project teams.
  • Delivering user training on Teams or links to resources to introduce Teams and how to use it. See the training resources at End user training for Microsoft Teams.
  • A feedback mechanism, such as a central team containing everyone, to collect comments and act on issues from organization users. If your organization has less than 2500 individuals, use a public channel in Teams. Otherwise, use a public group in Yammer.


Your organization is up and running and your change management strategy is in place to inform, train, and enable users to begin using Teams.

Step 2: Measure usage, manage satisfaction, and drive adoption

After rolling out Teams to your entire organization, you must continue to employ your change management strategy to:

  • Have your leadership promote Teams as the teamwork and collaboration tool for the organization.
  • Encourage individuals to use it for business group, departmental, work, and project team communications and collaboration.

Here are some suggested activities:

  • See Office 365 adoption guidance to learn about general best practices for cloud service adoption.
  • See Office 365 activity reports to understand Office 365 service usage across your organization. If you aren’t an Office 365 global admin for your organization, ask someone who is to grant your user account Reports Reader permissions so you can access activity reports.
  • Monitor your feedback venue (a public channel in a central team or Yammer) for issues and feedback from individuals about their experiences with Teams. Address questions and issues as quickly as you can to prevent frustration and abandonment of Teams by individuals.
  • Identify and nurture your champions in each business group and highlight their accomplishments and best practices using Teams. Reflect their successes out to the organization to show project success and adoption. Endorsement by technical leaders within a business group can exert a powerful influence over leaders and peers.


Your organization has adopted Teams as its collaboration and teamwork tool.

How Microsoft does Microsoft 365 Enterprise

To peek inside Microsoft and learn how the company deployed and is using Microsoft Teams for collaboration, see:

Next steps