"We've identified that a recent Edge release introduced a regression that's resulting in failures for some users when attempting to join meetings in Microsoft Teams," Microsoft said.
Incident TM1288497: Microsoft acknowledges an Edge-induced regression
Microsoft has confirmed that a recent update to its Edge browser introduced a bug that prevents some Windows users from joining Microsoft Teams meetings. The company logged the problem as incident TM1288497 and described it as a regression tied to a recent Edge release. Microsoft said it is analyzing diagnostic data and monitoring recent service changes as it works toward a fix, and that it will provide a timeline for next steps when one becomes available.
Who is affected: scheduled meetings and meetings joined via links
According to Microsoft's incident report, the issue affects only users who attempt to join scheduled meetings or meetings by following links. The company framed the problem narrowly: it did not attribute the symptom to ad-hoc meetings or other join paths, instead specifying the failure mode is limited to scheduled or link-based joins. Microsoft did not disclose how many users are affected or which geographic regions are impacted.
Immediate mitigation: restart the Microsoft Teams client
As an interim workaround, Microsoft advised affected users to restart the Microsoft Teams client. The company said restarting the client "might help them work around" the failure to join meetings while engineers investigate the regression in the most recent Edge release. Beyond that suggestion, Microsoft did not publish alternate mitigations or configuration changes in its advisory.
Context: a string of recent Edge and Teams service disruptions
This incident follows a series of related service problems Microsoft has acknowledged in recent days. Last week the company warned that a recent Edge update introduced a separate bug that broke right-click paste in chats in the Microsoft Teams desktop client; in that case, Microsoft tracked the issue as TM1279908 and said a fix would roll out to affected customers through the next scheduled platform update.
On Monday Microsoft reverted a recent service update that had blocked some customers from launching the Microsoft Teams desktop client, an error that left affected users stuck on the loading screen with the message, "We're having trouble loading your message. Try refreshing." Separately, Microsoft is working to address ongoing Universal Print sharing problems caused by a Microsoft Graph API code change that prevents users from creating printer shares.
How technologists, enterprises, and end users are responding
- Technologists and security teams: Operations teams will be parsing diagnostic data and monitoring Microsoft’s service-change messages, mirroring the approach Microsoft described. They are likely to prioritize verifying whether scheduled meeting joins or link joins are impacted in their environments and to deploy the simple client-restart workaround where appropriate.
- Affected enterprises and procurement leaders: Organizations that rely on scheduled, link-based meeting workflows may need to notify users about the restart workaround and track Microsoft’s announced timeline for a patch or platform update. Procurement and platform teams will watch for the formal fix and any follow-up advisories that change the advisory’s scope.
- End users and the general public: For individuals encountering join failures, Microsoft’s immediate guidance is to restart the Teams client. Users experiencing persistent problems should await Microsoft’s timeline for remediation and monitor Microsoft’s service advisories for updates.
Microsoft categorized the problem as an advisory — a classification it typically uses for service issues with limited scope or impact — but provided no quantitative measures of reach. Until Microsoft publishes the timeline it promised, the company’s diagnostic analysis and monitoring of recent service changes are the primary indicators of when a definitive remedy will be available. For now, the practical step for affected Windows users is simple: restart the Teams client and monitor Microsoft’s incident report TM1288497 for updates.
