Bulk upgrade to the new Microsoft Teams client

Direct or "bulk" upgrades are helpful because users don't need to manually download and install the Teams client. Microsoft provides an executable (.exe) file for the new Teams client so you can upgrade the application directly to the computers in your organization using your choice of software management tools, such as Intune or Configuration Manager.

The Teams installer installs the Teams MSIX package on a target computer, making sure that Teams can interoperate correctly with Office and other Microsoft software.

How it works

TeamsBootstrapper is a lightweight online installer with a headless command-line interface. It allows admins to provision (install) the app for all users on a given target computer.

When teamsbootstrapper.exe is run on a computer:

• The installer downloads the latest Teams MSIX package from Microsoft
• The installer installs the Teams application for all users on the computer, and any users who may be added afterwards.

• Modifies the registry to allow Teams to work with Office and other computer applications.
• Displays success or failure message on the command line

Prerequisites for target computers

For new Teams to be successfully installed, computers must meet the minimum requirements listed here.

Required system and app requirements

Step 1: Upgrade the new Teams application

All steps must be completed to successfully upgrade to the new Teams.

Option 1A: Download and install new Teams for a single computer

To install new Teams on a single computer with many users, follow these steps:

1. Download the .exe installer. If you have downloaded this file previously confirm you have the latest version by comparing the properties on each file.
2. Open the Command Prompt as an Admin.
3. At the prompt enter: .\teamsbootstrapper.exe -p
4. A success or fail status displays. If you receive an error, learn more at Common HRESULT values.
   

Option 1B: Download and install new Teams using an offline installer

Admins can also use a local teams MSIX to provision new Teams. This option minimizes the amount of bandwidth used for the initial installation. The MSIX can exist in a local path or UNC.

1. Download the .exe installer.. If you have downloaded this file previously confirm you have the latest version by comparing the properties on each file.
2. Download the MSIX:
   - MSIX x86
   - MSIX x64
   - ARM64
3. Open the Command Prompt as an Admin.
4. Depending on where your MSIX is located, do the following:
   

For local path, enter: .\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"

Example:

For UNC, enter: .\teamsbootstrapper.exe -p -o "\unc\path\to\teams.msix"

Example:

Option B: Upgrade to the new Teams across your organization

To deploy this installer to a group of computers, or your entire organization, follow these steps:

1. Download the .exe installer. If you have downloaded this file previously confirm you have the latest version by comparing the properties on each file.
2. Use Intune, Microsoft Endpoint Configuration Manager, Group Policy, or third-party distribution software, to distribute the installer to your target computers.
3. Run the installer on each computer.

Gov cloud updates for PC and Mac

PC update

If the customer tenant is on the GCCH, DoD, or Gallatin, the customer may need to set the initial cloud endpoint through the registry key listed below. Setting the endpoint with the registry key restricts teams to connecting to the correct cloud endpoint for pre-sign-in connectivity with Teams, as shown in the following:

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Teams
Value = CloudType
value type = DWORD
  1 = Commercial, 2 = GCC, 3 = GCCH, 4 = DOD, 7 = Gallatin

Mac update

If the customer tenant is on the GCCH, DoD, or Gallatin, the customer may need to set the initial cloud endpoint through the .plist configuration key listed below. Setting the endpoint with the .plist configuration restricts teams to connecting to the correct cloud endpoint for pre-sign-in connectivity with Teams, as shown in the following:

Domain: com.microsoft.teams2
Key: CloudType
Data Type: Int
Value: {Enter number associated with the cloud}
  1 = Commercial, 2 = GCC, 3 = GCCH, 4 = DOD, 7 = Gallatin

The .plist configuration can be propagated to managed devices using Intune as described in Add preference file settings to macOS devices in Microsoft Intune.

Step 2: Set new Teams as the default

1. Sign in to the Microsoft Teams admin center.
2. Select Teams > Teams Update policies from the left navigation pane.
3. Select Add to create a new policy or select an existing policy to open Update policy.
4. Name the update policy, add a description, and select the setting for “Use new Teams client”, as shown below.

5. Once the policy is defined, you can assign it to a user or user group with the Group policy assignment. To assign it to a group, select Group policy assignment and then Add, or select one of the groups listed. Select a policy to assign to the group.
6. Once the policy is defined, you can assign it to a specific user under Users> Manage users.

Remove new Teams for all users

To uninstall and deprovision the new Teams for all users, use the following command:

./teamsbootstrapper -x

Remove classic Teams for all users

Once the new Teams version has been installed, use the following command to uninstall the classic Teams machine-wide installer and classic Teams app for all users on the device:

./teamsbootstrapper -u

End user experience: Launching the new Teams

After new Teams is deployed to your target computers, users will sign in as usual. For first use, the user can launch new Teams in one of two ways:

Option 1: Users can launch classic Teams, and then switch the toggle to go to new Teams.

Option 2: Users can directly launch new Teams:

1. In Windows, select Start > new Microsoft Teams.
2. Select "Yes" at the confirmation prompt screen.
3. Once confirmed, the new Teams launches and is the default version.