![Ensuring Security and Compliance: Keep your Microsoft Teams desktop clients up to date [MC931401]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-frank-cone-140140-3573555-1024x683.webp)
Message ID: MC931401
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.
[How this will affect your organization:]
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)
[What you can do to 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.
Source: Microsoft
![New Microsoft Outlook for Windows: Read-only support for .pst files [MC931404]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-tirachard-kumtanom-112571-347139-150x150.webp)
![Microsoft Copilot: New user control for web searches [MC931407]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-freestockpro-1227513-150x150.webp)
The recent update regarding Microsoft Teams is set to significantly impact both admins and users, and it’s essential to unpack these changes with a balanced perspective—perhaps even with a sprinkle of humor.
For admins, the mandate to keep Teams clients up to date means more responsibility, but it also simplifies their workload in the long run. With automatic updates, the need for manual oversight is reduced, allowing IT teams to focus on more strategic initiatives. However, the reality is that some admins might find themselves in a bit of a pickle if their users are slow to adopt these updates. The alerts and eventual blocking pages for outdated versions can lead to a flurry of support tickets, and let’s face it, no one enjoys a sudden influx of “Why can’t I log in?” emails!
On the user side, the changes are a double-edged sword. While automatic updates ensure that everyone has access to the latest features and security enhancements, the looming threat of being locked out after 90 days without an update can cause a bit of anxiety. Imagine the horror of being in the middle of a crucial meeting and suddenly facing a blocking page! It’s a good reminder for users to keep an eye on their app notifications—after all, no one wants to be that person who shows up with outdated software, like wearing last season’s fashion!
Overall, the impact of these updates is quite profound. They not only enhance the security and compliance landscape but also encourage a culture of regular updates and proactive IT management. Let’s embrace this change, share our experiences, and support each other in navigating the new norms of Teams usage.
I encourage everyone to chime in with their thoughts and experiences in the comments below! Have you encountered any hiccups with updates in your organization? How do you keep your Teams clients current? Let’s get the conversation rolling! For more insights, check out other posts at mwpro.co.uk.