Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
As part of the deployment for the new Teams update, there are changes that need to be made to the executables, locations and installer package of the client. Organizations may have different settings in their environment, such as antivirus, network settings, QoS, and so on. Enterprises that have deployed classic Teams should review their configurations to account for the new Teams and make sure devices are on the latest OS update.
- Name and location: New Teams uses different files [ms-teams.exe & ms-teamsupdate.exe] and is located in: "Program Files\WindowsApps\MSTeams_[appversion]_[cpu arch]__8wekyb3d8bbwe".
- MSIX Installer technology stays current with the newest OS patches. Customers with installation problems in the past could resolve them with the latest OS updates.
Note
Adjust any third-party software that works with classic Teams app to use new Teams.
Checklist
- OS/WV2 prerequisites: Make sure the device has an updated Operating System (OS) and WebView2 (WV2) version. see the Windows, Mac, and VDI articles for more information. NOTE: New Teams doesn't work on lower OS versions.
- Device policies restrictions: Policies must not block new Teams installation (MSIX) and the Teams Meeting add-in (MSI) or the Webview2 updater.
- Network considerations: Review any configuration explicitly using classic Teams file paths or binary name for a good meeting experience. Some examples include configurations for:
- Local Firewalls: If you're using Windows Firewall policies to define inbound/outbound rules specific to the Teams application, you need to update them to reference the new executable name and path. With each update, the new Teams executable path changes. One approach for creating rules that account for the path change is to use Windows Defender Application Control (WDAC) application tagging policies. For an example, refer to the following guidance: WDAC Application Tagging for New Teams.
- Split Tunneling/Proxy: If you're referencing a split tunneling and/or proxy configuration, ensure that any references to the Classic Teams executable and path are updated to include the new Teams executable and path.
- Quality of Service (QoS): If your organization has set up QoS, please refer to the following guidance related to new Teams:
- Software blocks: Any management software including Antivirus or AppLocker that references classic Teams should be updated to include new Teams. For third-party products, please refer to the manufacturer's documentation.
- Machine-wide deployment or multi-user devices: Use Microsoft 365 apps or teamsbootstrapper to deploy new Teams machine-wide.
- Classic Teams minimum application version: Version 1.6.00.27573 or higher is required to deploy the in-app update to new Teams. Otherwise, the admin should review their deployment and use Microsoft 365 apps or manually install new Teams through the teamsbootstrapper.
- Make sure all users have updated to new Teams: As new Teams is deployed, track usage to validate that intended users and systems are updated via the usage report for new Teams client.
- Review to make sure your deployments replace any classic Teams installation references: This includes new machine images, device management configuration, scripts, old builds of Microsoft 365 apps, documentation, and so on.