Microsoft Teams Cannot Join Meetings for Some Users After a Recent Edge Update

Microsoft Teams Cannot Join Meetings for Some Users After a Recent Edge Update

Microsoft confirmed on April 23, 2026 that some Windows users are unable to join scheduled Teams meetings or link-based meetings after a recent Edge browser update. The issue is tracked as incident TM1288497. The root cause is a regression introduced in a recent Edge release that breaks the meeting-join flow for a subset of users. The only confirmed workaround at time of writing is to restart the Teams client.

What Is Broken

Affected users attempting to join scheduled Teams meetings via calendar links or direct meeting URLs are hitting failures. The issue appears to affect meeting join specifically — existing meetings in progress and direct calls are not reported as affected. Microsoft's service health dashboard confirmed the incident, attributing it to "a recent Edge release introduced a regression that's resulting in failures for some users."

Why an Edge Update Breaks Teams

Microsoft Teams on Windows uses Edge's WebView2 runtime component for rendering certain UI elements and handling browser-based authentication flows, including meeting join links. A regression in Edge's WebView2 can therefore break Teams functionality even for users who do not use Edge as their primary browser. This is a known architectural dependency that has caused similar incidents before — a browser update in one product silently breaking a completely separate product that shares an underlying runtime component.

The Workaround

Restarting the Teams desktop client resolves the issue for some affected users. For organizations where the restart workaround is not sufficient, rolling back the Edge update or switching to the Teams web app (teams.microsoft.com) as a temporary measure are options. Microsoft has not provided a resolution timeline.

My Take

The Teams/Edge WebView2 dependency is an ongoing liability. Microsoft has shipped multiple incidents where an Edge update has broken Teams behavior, and the root cause — shared runtime components across distinct products — has not been architecturally resolved. For enterprises running large Teams deployments, an uncoordinated Edge update that breaks meeting join during a busy period is a real operational problem. Microsoft should decouple Teams' critical path functionality from Edge's release cadence, or at minimum gate Edge updates through Teams compatibility testing before deployment.

Related Articles

Sources