Windows - Software Lifecycle - Upgrade to the New Microsoft Teams (MSIX)

What the Teams Classic to New Teams Migrator does

This Automox Worklet™ performs a complete migration from Microsoft Teams Classic to the New Teams (MSIX) client. Microsoft deprecated Teams Classic with an end-of-availability date of March 31, 2024. The Worklet automates the transition by removing all existing Teams installations and deploying the modern MSIX-based client.

Teams Classic exists in multiple installation forms: user-context installations in AppData, machine-wide MSI installer, and AppX packages. The Worklet identifies and removes each variant. It scans all user profiles on the endpoint, uninstalls Teams from both AppData and ProgramData locations, removes the Teams Machine-Wide Installer MSI, and cleans up Teams AppX and provisioning packages.

The Worklet examines registry keys including HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\.

After cleanup, the Worklet downloads the Microsoft Teams bootstrapper and architecture-appropriate MSIX package directly from Microsoft. The bootstrapper handles the MSIX installation silently, deploying the 64-bit or 32-bit New Teams client based on the endpoint's architecture.

Why migrate to New Teams through Automox

Microsoft ended support for Teams Classic, meaning no further updates, security patches, or feature enhancements. Organizations continuing to use Teams Classic face increasing security risks and eventual loss of functionality as Microsoft deprecates backend APIs. Migrating to New Teams maintains support coverage and access to modern collaboration features.

The New Teams client offers performance improvements including faster startup, reduced memory usage, and improved meeting experiences. The MSIX packaging model provides cleaner installation and updates compared to the legacy Squirrel-based installer that created multiple installation locations and update mechanisms.

Automating this migration through Automox lets you schedule the transition during maintenance windows, track progress across your fleet, and handle the complexity of cleaning up multiple Teams installation variants. Manual migration at scale is time-consuming and error-prone given the various places Teams Classic installs files.

How Teams Classic to New Teams migration works

1. Evaluation phase: The Worklet uses Get-AppxPackage -AllUsers to check for the MSTeams_8wekyb3d8bbwe package. If the New Teams package exists, the endpoint is compliant. If not found, the endpoint is flagged for remediation to install the New Teams client.

2. Remediation phase: The Worklet first removes Teams Machine-Wide Installer via msiexec /x with /qn flag. It then iterates through all user directories, running Update.exe --uninstall /s for Teams installations found in AppData\Local\Microsoft\Teams or ProgramData. AppX packages named MSTeams, MicrosoftTeams, or Microsoft.MSTeams are removed for all users. Residual files and Start Menu shortcuts are deleted. Finally, the Worklet downloads bootstrapper.exe and MSTeams.msix from Microsoft, then runs the bootstrapper with -p -o flags to install New Teams.

Teams migration requirements

• Windows workstations or servers meeting Microsoft's New Teams prerequisites

• Internet connectivity to download bootstrapper and MSIX from Microsoft (go.microsoft.com/fwlink URLs)

• AppX/MSIX installation capabilities enabled on the endpoint

• Users will need to sign in to New Teams after installation

• Default timeout: 300 seconds for installation and uninstallation processes

Expected state after Teams migration

After successful remediation, the New Microsoft Teams client is installed via MSIX packaging. The MSTeams_8wekyb3d8bbwe package appears in Get-AppxPackage output. All Teams Classic installations are removed from user profiles and program files. Start Menu shortcuts point to the New Teams client.

Users must launch New Teams manually and sign in with their Microsoft 365 credentials. Once launched, the application appears as "Microsoft Teams Meeting Add-in for Microsoft Office" in Add or Remove Programs. Chat history, settings, and cached data from Teams Classic are not migrated, but users can access their full message history through their Microsoft 365 account.

How to validate upgrade to the new microsoft teams (msix) changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for upgrade to the new microsoft teams (msix).

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Get-AppxPackage, Where-Object, Write-Output.

4. Validate remediation effects from script operations such as Start-Process, Wait-Process, Stop-Process, then rerun evaluation for compliance.