Bulk install classic Teams using Windows Installer (MSI)
Important
The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See The new Microsoft Teams for more information.
Important
This article is for classic Teams only. To bulk deploy to new Teams, see: Bulk upgrade to the new Microsoft Teams client
Tip
Watch the following session to learn about the benefits of the Windows Desktop Client, how to plan for it and how to deploy it: Teams Windows Desktop Client.
Microsoft provides 32-bit, 64-bit, and ARM64 MSI files that you can use to bulk deploy Microsoft Teams to select users and computers. MSI files can be used with Microsoft Endpoint Configuration Manager, Group Policy, or third-party distribution software, to deploy Teams to your organization. Bulk deployments are useful because users don't need to download and install the Teams client manually. Rather, Teams will be deployed to computers and then auto-launch the first time users sign into a computer.
We recommend that you deploy the package to computers rather than a specific user. By targeting computers, all new users of those computers will benefit from this deployment.
Note
Teams can also be distributed to your organization as part of Microsoft 365 Apps for enterprise. For more information, see Deploy Microsoft Teams with Microsoft 365 Apps for enterprise.
MSI files
The table below provides links to 32-bit, 64-bit, and ARM64 MSI files for Teams. Download the MSI that you want to install on computers in your organization. The x86 architecture (32-bit or 64-bit) Teams supports is independent of other Office apps installed on a computer.
Note
New builds are released regularly. If you have previously downloaded the MSI, confirm if you have the most current version. Learn more: Version update history for the Microsoft Teams app
If you have 64-bit computers, we recommend installing the 64-bit Teams MSI even if the computer is running a 32-bit version of Office. The ARM64 MSI can only be installed on computers that use the ARM architecture, such as the Surface Pro X.
Important
Install the 64-bit version of Teams only on 64-bit operating systems. If you try to install the 64-bit version of Teams on a 32-bit operating system, the installation won't be successful and you won't receive an error message.
| Entity | 32-bit | 64-bit | ARM64 |
|---|---|---|---|
| Commercial | 32-bit | 64-bit | ARM64 |
| U.S. Government - GCC | 32-bit | 64-bit | ARM64 |
| U.S. Government - GCC High | 32-bit | 64-bit | ARM64 |
| U.S. Government - DoD | 32-bit | 64-bit | ARM64 |
How the Microsoft Teams MSI file works
PC installation
The Teams MSI places an installer in %SystemDrive%\Program Files\Teams Installer on 32-bit Windows and %SystemDrive%\Program Files (x86)\Teams Installer on 64-bit Windows. Whenever a user signs into a new Windows user profile, the installer is launched and a copy of the Teams app is installed in that user's %LocalAppData%\Microsoft\Teams folder. If a user already has the Teams app installed in the %LocalAppData%\Microsoft\Teams folder, the MSI installer skips the process for that user.
MSI files can't be used to deploy updates. The Teams client will auto-update when it detects a new version is available from the service. To re-deploy the latest installer, use the process of redeploying MSI described below. If you deploy an older version of the MSI file, the client will auto-update (except in VDI environments) when possible for the user. If a very old version gets deployed, the MSI will trigger an app update before the user is able to use Teams.
Important
We don't recommended that you change the default install locations as this could break the update flow. Having too old a version will eventually block users from accessing the service.
Note
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. 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
Target computer requirements
Make sure the computers you install Teams on meeting the requirements listed in Hardware requirements for Microsoft Teams.
VDI installation
For complete guidance on how to deploy the Teams desktop app on VDI, see Teams for Virtualized Desktop Infrastructure.
Uninstallation
If a user that had Teams installed via an MSI uninstalls it, a registry key is created:
HKEY_CURRENT_USER\Software\Microsoft\Office\Teams\PreventInstallationFromMsi
While this key is present, Teams won't install itself again from the Machine-Wide Installer. If a user uninstalls the Teams Machine-Wide Installer, then the install Run key is removed, and a new uninstall Run key is created:
TeamsMachineUninstallerLocalAppData REG_EXPAND_SZ
%LOCALAPPDATA%\Microsoft\Teams\Update.exe --uninstall --msiUninstall
This will cause Teams to uninstall the next time the user signs in.
Clean up and redeployment procedure
If a user uninstalls Teams from their user profile, the MSI installer will track that the user has uninstalled the Teams app and no longer install Teams for that user profile. To redeploy Teams for this user on a particular computer where it was uninstalled, do the following:
Important
The next steps contain information about how to modify the registry. Make sure that you back up the registry before you modify it and that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see Windows registry information for advanced users.
- Uninstall the Teams app installed for every user profile. For more information, see Uninstall Microsoft Teams.
- Delete the directory recursively under
%LocalAppData%\Microsoft\Teams\for each user profile. - Delete the
HKEY_CURRENT_USER\Software\Microsoft\Office\Teams\PreventInstallationFromMsiregistry value for each user profile. - Redeploy the MSI file to that particular computer.
Tip
You can also use our Teams deployment clean up script to complete steps 1 and 2.
Prevent Teams from starting automatically after installation
The default behavior of the MSI is to install the Teams app as soon as a user signs in and then automatically start Teams. If you don't want Teams to start automatically for users after it's installed, you can use Group Policy to set a policy setting or disable auto launch for the MSI installer.
Use Group Policy (recommended)
Enable the Prevent Microsoft Teams from starting automatically after installation Group Policy setting. You can find this policy setting in User Configuration\Policies\Administrative Templates\Microsoft Teams. This is the recommended method because you can turn off or turn on the policy setting according to your organization's needs.
When you enable this policy setting before Teams is installed, Teams doesn't start automatically when users log in to Windows. After a user signs in to Teams for the first time, Teams starts automatically the next time the user logs in.
To learn more, see Use Group Policy to prevent Teams from starting automatically after installation.
Caution
If you've already deployed Teams and want to set this policy to disable Teams autostart, first set the Group Policy setting to the value you want, and then run the Teams autostart reset script on a per-user basis.
Note
For information about using Administrative Templates in Microsoft Intune to configure this setting, see Use Windows 10/11 templates to configure group policy settings in Microsoft Intune.
Disable auto launch for the MSI installer
You can disable auto launch for the MSI installer by using the OPTIONS="noAutoStart=true" parameter as follows.
For the 32-bit version:
msiexec /i Teams_windows.msi OPTIONS="noAutoStart=true" ALLUSERS=1
For the 64-bit version:
msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true" ALLUSERS=1
When a user logs in to Windows, Teams is installed with the MSI. Teams won't start until the user manually starts Teams. After the user manually starts Teams, Teams automatically starts whenever the user logs in.
Note that these examples also use the ALLUSERS=1 parameter. When you set this parameter, Teams Machine-Wide Installer appears in Programs and Features in Control Panel and in Apps & features in Windows Settings for all users of the computer. All users can then uninstall Teams if they have admin credentials on the computer.
Note
If you run the MSI manually, be sure to run it with elevated permissions. Even if you run it as an administrator, without running it with elevated permissions, the installer won't be able to configure the option to disable auto start.