Keep your Microsoft Teams desktop client compliant by updating it
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredSince Microsoft Teams is governed by the Modern Lifecycle Policy, the Teams desktop client needs to be up to date. Users who are on old versions of classic Teams app will receive in-app notifications to encourage them to update to the latest version of Teams. This is to ensure that users have the latest capabilities, performance enhancements, security features, and service reliability.
This in-app notification will not apply to users on machine wide (non-persistent setup) Virtual Desktop Infrastructure (VDI) deployments. Admins will need to regularly update those users to remain supported on Teams.
Per MC298823 (November '21), a version that is too far out of date will become incompatible with the service until it’s updated. Also see MC783985 for Classic Teams Timelines regarding end of support and end of availability.
When this will happen
This will be enforced on June 19th, 2024.
How this will affect your organization
Classic Teams- Windows Versions less than 1.6.00.18681
- Beginning August 20th, 2024, the Teams desktop client may present a blocking page for users and request them to update to the latest version of Teams from this page.
Classic Teams- Windows Versions less than 1.7.00.3653
- Beginning June 19th, 2024, the Teams desktop client may present a banner notifying users that they are on an unsupported version of Teams.
Classic Teams - Mac Versions less than 1.6.00.35956
- Beginning August 20th, 2024, the Teams desktop client may present a blocking page for users and request them to update to the latest version of Teams from this page.
Classic Teams - Mac Versions less than 1.7.00.3856
- Beginning June 19th, 2024, the Teams desktop client may present a banner notifying users that they are on an unsupported version of Teams.
Note: as the service progresses old Teams version will be missing features and may have significant service degradation, though basic features will likely continue to function.
The risks of not updating to the most recent version are:
- Your Teams desktop client may miss important security and quality updates.
- The reliability of your Teams desktop client may suffer without recent bug fixes.
- Your Teams desktop client may not be compatible with the Modern Lifecycle Policy, resulting in unpredictable behavior and missing functionality.
- Client versions with release dates that are more than 90 days older than the current version's release date may be blocked because the above is incompatible with the service.
Note: Teams desktop clients on GCC High, DoD and 21Vianet currently have an exception to this servicing agreement until further notice.
What you can do to prepare
To avoid disruption to end-users, the admins with users on Teams versions older than the supported versions (any versions with release dates that are more than 90 days older than the current version's release date) should update their users to the most recent version. Admins should plan for a regular update cadence to stay current and within the compatibility window. Please visit this page to learn more.
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Learn more
Links from the notice and their documentation checksNotices it cites
Other posts named in this one- MC298823 · Cited notice · metadata unavailableCoverage gap · We haven't seen Microsoft's notice.
- MC783985 · Classic Teams Timelines for end of support and end of availabilityPlan for change · changed 23 Apr 2024From Microsoft 365 Message Center Archive by Merill Fernando
Related public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.