check before: 2024-11-12
Product:
Microsoft 365 admin center, Microsoft 365 Apps, Skype for Business, Teams, Windows, Windows Virtual Desktop
Platform:
Developer, Education, Mac, mobile, Online, Web, Windows Desktop, World tenant
Status:
Launched
Change type:
Admin impact, Updated message, User impact
Details:
Summary:
The message updates on the importance of keeping Microsoft Teams desktop clients up-to-date for security and compliance, detailing the enforcement schedule for outdated versions starting January 14th, 2025. It also advises admins to ensure automatic updates are properly configured to avoid service disruption.
Details:
Updated December 18, 2024: We've delayed further rollouts of warning banners and blocking pages in December and intend to resume in mid-January per the schedule below. Please review for updated information and timing.
In today's security climate, our work across the company and greater industry to keep this critical ecosystem secure is more important than ever. And while we also ship bug fixes and other new features via continuous innovation, in the end security is job one.
Keeping Microsoft Teams up to date is critical to ensure your devices are secure and compliant. By default, and as designed, Teams updates automatically which successfully updates most clients in the world without additional overhead for customers.
Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the Teams desktop client be kept up to date. This is not a new policy, for instance in MC298823 (November 2021), a version that is far out of date will become incompatible with the service until it's updated. As documented, when a client falls out of date, the user will see:
Recurring in-app alerts, if the app is between 30d-90d out of date. Except in VDI environments, where this will occur between 60-90 days out of date.
A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web.
As an example, if the Teams app is hypothetically on a version released on January 1 and the next update is fully available on January 15, an in-app alert would be shown on February 14th (30 days after the January 15th update).
For reference, link to the Teams app's version's release dates. Also, The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization.
Classic Teams is not in scope for this post; see MC783985 for Classic Teams Timelines regarding end of support and end of availability.
[When this will happen:]
The existing policy enforcement will be visible beginning January 14th, 2025.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
General Availability
Created:
2024-11-12
updated:
2024-12-19
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
linked item details
XXXXXXX ... free basic plan only
summary for non-techies**
Starting January 14th, 2025, Microsoft will enforce policies to ensure Teams desktop clients are updated, with notifications for updates if the app is over 30 days out of date and blocking access if over 90 days, while VDI environments will have a 60-day notification period and a 90-day blocking period.
Direct effects for Operations**
Outdated Teams Client Notifications
Users will receive recurring in-app alerts if their Teams client is between 30-90 days out of date, leading to potential frustration and decreased productivity.
- roles: End Users, IT Administrators
- references: https://docs.microsoft.com/microsoftteams/teams-client-update
Blocking Page for Outdated Clients
If the Teams client is more than 90 days out of date, users will encounter a blocking page, which may disrupt their workflow and force them to use Teams on the web.
- roles: End Users, IT Administrators
- references: https://docs.microsoft.com/microsoftteams/teams-client-update
Service Disruption Due to Non-Compliance
Failure to update Teams clients may result in service disruption, impacting communication and collaboration among users.
- roles: End Users, IT Administrators
- references: https://docs.microsoft.com/microsoftteams/teams-client-update
Increased Support Requests
Outdated clients may lead to an increase in support requests from users experiencing issues, straining IT resources.
- roles: IT Support Staff, IT Administrators
- references: https://docs.microsoft.com/microsoftteams/teams-client-update
User Experience Degradation
Users on outdated versions may miss out on new features and security updates, leading to a degraded user experience and potential security risks.
- roles: End Users, IT Administrators
- references: https://docs.microsoft.com/microsoftteams/teams-client-update
Configutation Options**
XXXXXXX ... paid membership only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2024-12-19 | MC Messages | Updated December 3, 2024: We're delaying further rollouts of warning banners and blocking pages in December and intend to resume in mid-January. We'll have a more detailed update later.
In today's security climate, our work across the company and greater industry to keep this critical ecosystem secure is more important than ever. And while we also ship bug fixes and other new features via continuous innovation, in the end security is job one. Keeping Microsoft Teams up to date is critical to ensure your devices are secure and compliant. By default, and as designed, Teams updates automatically which successfully updates most clients in the world without additional overhead for customers. Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the Teams desktop client be kept up to date. This is not a new policy, for instance in MC298823 (November 2021), a version that is far out of date will become incompatible with the service until it's updated. As documented, when a client falls out of date, the user will see: Recurring in-app alerts, if the app is between 30d-90d out of date. A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web. As an example, if the Teams app is hypothetically on a version released on January 1 and the next update is fully available on January 15, an in-app alert would be shown on February 14th (30 days after the January 15th update). For reference, link to the Teams app's version's release dates. Also, The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization. Classic Teams is not in scope for this post; see MC783985 for Classic Teams Timelines regarding end of support and end of availability. [When this will happen:] The existing policy enforcement will be visible beginning November 12th, 2024. | Updated December 18, 2024: We've delayed further rollouts of warning banners and blocking pages in December and intend to resume in mid-January per the schedule below. Please review for updated information and timing.
In today's security climate, our work across the company and greater industry to keep this critical ecosystem secure is more important than ever. And while we also ship bug fixes and other new features via continuous innovation, in the end security is job one. Keeping Microsoft Teams up to date is critical to ensure your devices are secure and compliant. By default, and as designed, Teams updates automatically which successfully updates most clients in the world without additional overhead for customers. Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the Teams desktop client be kept up to date. This is not a new policy, for instance in MC298823 (November 2021), a version that is far out of date will become incompatible with the service until it's updated. As documented, when a client falls out of date, the user will see: Recurring in-app alerts, if the app is between 30d-90d out of date. Except in VDI environments, where this will occur between 60-90 days out of date. A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web. As an example, if the Teams app is hypothetically on a version released on January 1 and the next update is fully available on January 15, an in-app alert would be shown on February 14th (30 days after the January 15th update). For reference, link to the Teams app's version's release dates. Also, The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization. Classic Teams is not in scope for this post; see MC783985 for Classic Teams Timelines regarding end of support and end of availability. [When this will happen:] The existing policy enforcement will be visible beginning January 14th, 2025. |
| 2024-12-19 | MC How Affect | New Teams - Windows & Mac Versions desktop clients (not running in a VDI environment)
Beginning November 12th, 2024, Teams desktop clients >30d out of date, will present a banner or notification to users that they are on an outdated version of Teams. For reference, Windows client versions less than 24231.512.3106.6573 are impacted on November 12. Mac client versions less than 242507.3125.3475 are impacted on Nov 12. (On hold) Beginning December 4th, 2024, Teams desktop clients older than 90d out of date, will present a blocking page. They will be shown an option to update to the latest version of Teams from this page or use Teams on the web. For reference, Windows client versions less than 24193.1805.3040.8975 are impacted on December 4th. Mac client versions less than 24215.1002.3039.5089 are impacted on December 4th. New Teams app running in a VDI environment - Windows desktop clients will follow the same policies as non-VDI environments, with enforcement starting on dates below Beginning January 13th, 2025, for clients more than 30d out of date will get a banner or notification to users that they are on an outdated version of Teams. Beginning February 3rd, 2025, for clients older than 90d out of date, the Teams desktop client will present a blocking page. Note: The enforcement policies on preview rings may start mid-November. The 30d out of date in app messaging and 90d out of date blocking dates still apply (for versions released to that ring) | New Teams - Windows & Mac Versions desktop clients (not running in a VDI environment)
Beginning January 14th, 2025, Teams desktop clients more than 30 days out of date, will present a banner or notification to users that they are on an outdated version of Teams. Beginning February 18th, 2025, Teams desktop clients older than 90 days out of date, will present a blocking page. They will be shown an option to update to the latest version of Teams from this page or use Teams on the web. New Teams app running in a VDI environment - Windows desktop clients will follow the same policies as non-VDI environments, with enforcement starting on dates below Beginning March 11th, 2025, for clients more than 60 days out of date will get a banner or notification to users that they are on an outdated version of Teams. Beginning May 6th, 2025, for clients older than 90 days out of date, the Teams desktop client will present a blocking page. Note on Deployment of Changes: Users in preview rings will experience the changes approximately 4 weeks before the specified dates (for app versions released to that ring). The experiences above will not be visible to all users right away. It will take 4-8 weeks for the deployment to reach all users. |
| 2024-12-19 | MC Last Updated | 12/03/2024 20:10:00 | 2024-12-18T20:23:55Z |
| 2024-12-19 | MC prepare | To avoid disruption to end-users, the admins with users on Teams versions older than the currently released versions, should update their users to the most recent version.
Admins should make sure Teams is automatically updating to stay current and within the compatibility window. Common configurations to validate include: Teams clients on macOS have Microsoft AutoUpdate (MAU) configured properly. Learn More Customer network settings, and any device management software e.g. antivirus, are configured properly to allow automatic updates. Windows Policies must not block new Teams or the Webview2 updater. Please visit this page to learn more. https://docs.microsoft.com/lifecycle/policies/modern https://docs.microsoft.com/officeupdates/teams-app-versioning https://learn.microsoft.com/microsoft-edge/webview2/concepts/enterprise https://learn.microsoft.com/microsoftteams/new-teams-usage-report https://learn.microsoft.com/microsoftteams/teams-client-update https://learn.microsoft.com/microsoftteams/teams-client-update#servicing-agreement https://learn.microsoft.com/microsoftteams/teams-client-update#updating-teams-on-mac-devices https://learn.microsoft.com/microsoftteams/troubleshoot/teams-administration/fix-new-teams-installation-issues#policy-settings-prevent-download-and-installation https://www.microsoft.com/microsoft-teams/download-app | To avoid disruption to end-users, the admins with users on Teams versions older than the currently released versions, should update their users to the most recent version.
Admins should make sure Teams is automatically updating to stay current and within the compatibility window. Common configurations to validate include: Teams clients on macOS have Microsoft AutoUpdate (MAU) configured properly. Learn More Customer network settings, and any device management software e.g. antivirus, are configured properly to allow automatic updates. Windows Policies must not block new Teams or the Webview2 updater. Please visit this page to learn more. https://docs.microsoft.com/lifecycle/policies/modern https://docs.microsoft.com/officeupdates/teams-app-versioning https://learn.microsoft.com/microsoft-edge/webview2/concepts/enterprise https://learn.microsoft.com/microsoftteams/new-teams-usage-report https://learn.microsoft.com/microsoftteams/teams-client-update https://learn.microsoft.com/microsoftteams/teams-client-update#servicing-agreement https://learn.microsoft.com/microsoftteams/teams-client-update#updating-teams-on-mac-devices https://learn.microsoft.com/microsoftteams/troubleshoot/teams-administration/fix-new-teams-installation-issues#policy-settings-prevent-download-and-installation https://www.microsoft.com/en-us/microsoft-teams/download-app |
| 2024-12-19 | MC Summary | The message emphasizes the importance of keeping Microsoft Teams desktop clients updated for security and compliance. Teams updates automatically, but admins should ensure this feature is properly configured. Starting November 12th, 2024, outdated clients will receive notifications, and by December 4th, 2024 (on hold), a blocking page will appear for versions older than 90 days. Admins need to prepare by updating Teams and verifying configurations. | The message updates on the importance of keeping Microsoft Teams desktop clients up-to-date for security and compliance, detailing the enforcement schedule for outdated versions starting January 14th, 2025. It also advises admins to ensure automatic updates are properly configured to avoid service disruption. |
| 2024-12-04 | MC MessageTagNames | User impact, Admin impact | Updated message, User impact, Admin impact |
| 2024-12-04 | MC Summary | The message emphasizes the importance of keeping Microsoft Teams desktop clients updated for security and compliance. Teams updates automatically, but admins should ensure this feature is properly configured. Starting November 12th, 2024, outdated clients will receive notifications, and by December 4th, 2024, a blocking page will appear for versions older than 90 days. Admins need to prepare by updating Teams and verifying configurations. | The message emphasizes the importance of keeping Microsoft Teams desktop clients updated for security and compliance. Teams updates automatically, but admins should ensure this feature is properly configured. Starting November 12th, 2024, outdated clients will receive notifications, and by December 4th, 2024 (on hold), a blocking page will appear for versions older than 90 days. Admins need to prepare by updating Teams and verifying configurations. |
| 2024-12-04 | MC Last Updated | 11/12/2024 01:06:29 | 2024-12-03T20:10:00Z |
| 2024-12-04 | MC Messages | In today's security climate, our work across the company and greater industry to keep this critical ecosystem secure is more important than ever. And while we also ship bug fixes and other new features via continuous innovation, in the end security is job one.
Keeping Microsoft Teams up to date is critical to ensure your devices are secure and compliant. By default, and as designed, Teams updates automatically which successfully updates most clients in the world without additional overhead for customers. Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the Teams desktop client be kept up to date. This is not a new policy, for instance in MC298823 (November 2021), a version that is far out of date will become incompatible with the service until it's updated. As documented, when a client falls out of date, the user will see: Recurring in-app alerts, if the app is between 30d-90d out of date. A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web. As an example, if the Teams app is hypothetically on a version released on January 1 and the next update is fully available on January 15, an in-app alert would be shown on February 14th (30 days after the January 15th update). For reference, link to the Teams app's version's release dates. Also, The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization. Classic Teams is not in scope for this post; see MC783985 for Classic Teams Timelines regarding end of support and end of availability. [When this will happen:] The existing policy enforcement will be visible beginning November 12th, 2024. | Updated December 3, 2024: We're delaying further rollouts of warning banners and blocking pages in December and intend to resume in mid-January. We'll have a more detailed update later.
In today's security climate, our work across the company and greater industry to keep this critical ecosystem secure is more important than ever. And while we also ship bug fixes and other new features via continuous innovation, in the end security is job one. Keeping Microsoft Teams up to date is critical to ensure your devices are secure and compliant. By default, and as designed, Teams updates automatically which successfully updates most clients in the world without additional overhead for customers. Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the Teams desktop client be kept up to date. This is not a new policy, for instance in MC298823 (November 2021), a version that is far out of date will become incompatible with the service until it's updated. As documented, when a client falls out of date, the user will see: Recurring in-app alerts, if the app is between 30d-90d out of date. A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web. As an example, if the Teams app is hypothetically on a version released on January 1 and the next update is fully available on January 15, an in-app alert would be shown on February 14th (30 days after the January 15th update). For reference, link to the Teams app's version's release dates. Also, The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization. Classic Teams is not in scope for this post; see MC783985 for Classic Teams Timelines regarding end of support and end of availability. [When this will happen:] The existing policy enforcement will be visible beginning November 12th, 2024. |
| 2024-12-04 | MC Title | Ensuring Security and Compliance: Keep your Microsoft Teams desktop clients up to date | (Updated) Ensuring Security and Compliance: Keep your Microsoft Teams desktop clients up to date |
| 2024-12-04 | MC How Affect | New Teams - Windows & Mac Versions desktop clients (not running in a VDI environment)
Beginning November 12th, 2024 , Teams desktop clients >30d out of date, will present a banner or notification to users that they are on an outdated version of Teams. For reference, Windows client versions less than 24231.512.3106.6573 are impacted on November 12. Mac client versions less than 242507.3125.3475 are impacted on Nov 12. Beginning December 4th, 2024, Teams desktop clients older than 90d out of date, will present a blocking page. They will be shown an option to update to the latest version of Teams from this page or use Teams on the web. For reference, Windows client versions less than 24193.1805.3040.8975 are impacted on December 4th. Mac client versions less than 24215.1002.3039.5089 are impacted on December 4th. New Teams app running in a VDI environment - Windows desktop clients will follow the same policies as non-VDI environments, with enforcement starting on dates below Beginning January 13th 2025, for clients more than 30d out of date will get a banner or notification to users that they are on an outdated version of Teams. Beginning February 3rd 2025, for clients older than 90d out of date, the Teams desktop client will present a blocking page. Note: The enforcement policies on preview rings may start mid-November. The 30d out of date in app messaging and 90d out of date blocking dates still apply (for versions released to that ring) | New Teams - Windows & Mac Versions desktop clients (not running in a VDI environment)
Beginning November 12th, 2024, Teams desktop clients >30d out of date, will present a banner or notification to users that they are on an outdated version of Teams. For reference, Windows client versions less than 24231.512.3106.6573 are impacted on November 12. Mac client versions less than 242507.3125.3475 are impacted on Nov 12. (On hold) Beginning December 4th, 2024, Teams desktop clients older than 90d out of date, will present a blocking page. They will be shown an option to update to the latest version of Teams from this page or use Teams on the web. For reference, Windows client versions less than 24193.1805.3040.8975 are impacted on December 4th. Mac client versions less than 24215.1002.3039.5089 are impacted on December 4th. New Teams app running in a VDI environment - Windows desktop clients will follow the same policies as non-VDI environments, with enforcement starting on dates below Beginning January 13th, 2025, for clients more than 30d out of date will get a banner or notification to users that they are on an outdated version of Teams. Beginning February 3rd, 2025, for clients older than 90d out of date, the Teams desktop client will present a blocking page. Note: The enforcement policies on preview rings may start mid-November. The 30d out of date in app messaging and 90d out of date blocking dates still apply (for versions released to that ring) |
Last updated 1 month ago
