| Message Content |
This Message center post outlines some of the reasons why users may remain on classic Teams and what steps the administrators need to take to transition users to new Teams or address existing problems. This applies to Commercial, EDU, Government cloud customers as well as VDI environment users. Reference to our last MC post regarding End of Support and End of availability (MC783985 April ’24)
[How this will affect your organization]
As we transition users to new Teams, there may be a small number of users in your organization that may remain on classic Teams. These users do not yet meet the necessary requirements for the update and need deliberate action from you to transition them. There could be one or multiple of these issues preventing them from receiving new Teams. Please review the list below and suggested mitigations to avoid any work stoppage for your users. (More details are available in our new Teams checklist)
- Operating system: The following operating systems do not meet requirements for installing new Teams: Windows 10 version 10.0.19041 or lower, Windows 10 LTSC or Mac OS lower than macOS Monterey (12).
- Policies blocking app installations: Organizational Policies blocking app installation (MSIX) and the Teams Meeting add-in (MSI).
- Other software blocks: Any management software including firewalls, Antivirus or AppLocker that references classic Teams or prevents app installations. For third-party products, please refer to the manufacturer’s documentation.
- Missing WebView 2: Users without the latest version of WebView 2 deployed.
- Users on old version of classic Teams client: If users are using classic Teams application versions lower than 1.6.00.27573 (windows), 1.6.00.35956 (Mac).
[What you need to do to prepare:]
- Update operating system: Users running classic Teams Windows desktop on Windows 10 version that is less than 10.0.19041 or running macOS versions on Big Sur(11) or lower should work on updating your OS as soon as possible. Microsoft recommends updating Windows 11 and macOS Sonoma (version 14). The prerequisites for new Teams can be found here.
- VDI Customers should plan to update to Windows Server 2019 (10.0.17763) or Windows Server 2022 (10.0.20348) or higher to get started on their new Teams journey. For details on VDI system requirements, visit this page.
- Resolve device policy restrictions: Policies must not block new Teams installation (MSIX) and the Teams Meeting add-in (MSI) or the Webview2 updater. We strongly recommend mitigating by either updating to Evergreen Webview2 installer or leveraging deployment options such as bulk deployment
- Fix other software blocks: For any other firewalls, Antivirus or AppLocker issues that are preventing app installation, we strongly recommend mitigating these issues or leveraging deployment options such as bulk deployment to get new Teams for users.
- Update Teams client version: Users on Teams versions that are older than the supported versions (any versions released over 90 days prior to the current version’s release date) must update their desktop client to the latest version. Administrators should plan for a regular update cadence to remain current and within the compatibility window. Please visit this page to learn more.
- Note: Please refer to our checklist for more information on new Teams requirements: Deployment checklist for new Teams client – Microsoft Teams | Microsoft Learn;
- Classic Teams end of availability details can be found here: End of availability for classic Teams client.
|