Microsoft Teams Bug Blocks Some Windows Users From Joining Meetings After Edge Update

Microsoft is investigating a Teams issue that prevents some Windows users from joining meetings after a recent Microsoft Edge update introduced a regression. The incident is tracked as TM1288497 and affects scheduled Teams meetings and meetings joined through links.

The issue does not appear to affect every Teams user. Microsoft’s incident notice says the impact applies to some users on Windows devices, and affected users may be unable to join Microsoft Teams meetings until they restart the Teams client.

Microsoft has already deployed an updated version of Edge to replace the problematic release. The company said it is monitoring service health telemetry and expects the impact to ease as the updated browser version reaches affected environments.

The problem affects scheduled meetings and meeting links

The most important detail for users is that the failure appears when joining scheduled meetings or joining through shared meeting links. Those are two of the most common ways employees join business calls, school sessions, healthcare consultations, and internal briefings.

Microsoft identified the root cause as a regression in a recent Edge release. Teams relies on Microsoft Edge components on Windows, so a browser-level change can affect desktop meeting workflows even when users are joining through the Teams client.

NHSmail also listed the incident under reference INC46806917, confirming impact for organizations using its Microsoft 365 environment. Its latest service alert says the issue remains ongoing while Microsoft monitors recovery after deploying the updated Edge version.

What Microsoft says happened

Item	Details
Microsoft incident ID	TM1288497
NHSmail reference	INC46806917
Affected service	Microsoft Teams
Affected platform	Windows devices
Main failure point	Scheduled meetings and meeting links
Root cause	Regression in a recent Microsoft Edge release
Workaround	Restart the Microsoft Teams client
Current status	Updated Edge version deployed, telemetry under monitoring

Microsoft’s incident timeline says the issue started on April 16, 2026, at 7:00 AM UTC. The company later confirmed that a recent Edge release introduced a regression that caused failures when some users attempted to join Teams meetings.

Early updates said Microsoft was reviewing logs from affected users and trying to reproduce the issue internally. Later updates said the company had moved from investigation to remediation by deploying an updated Edge version to replace the offending build.

The latest NHSmail update, posted on April 24, says Microsoft deployed the updated Edge version and is watching telemetry to confirm that the impact eases as expected.

Restarting Teams is the fastest workaround

Microsoft’s recommended workaround is simple: restart the Microsoft Teams client. That step can restore meeting access for affected users while the Edge fix rolls out across managed devices and enterprise environments.

Users should fully close Teams before reopening it. On Windows, that may mean quitting Teams from the system tray, not just closing the main app window. IT teams can also advise users to check for pending Edge updates if their organization allows manual browser updates.

Organizations should avoid assuming this is a meeting policy issue, account permission problem, or organizer-side setting without first checking the TM1288497 advisory. Microsoft’s own incident text ties the problem to the Edge regression, not to Teams meeting configuration.

Why an Edge bug can affect Teams

Microsoft Teams on Windows uses web platform components, and Edge updates can affect those shared components. That means a browser regression can create problems inside Teams even when the user is not actively opening a meeting in the Edge browser.

This is not the only recent Teams problem linked to Edge. Microsoft also tracked a separate issue, TM1279908, where users could have trouble using paste in Teams desktop client chats after another Edge-related regression.

The two incidents are separate, but they show the same broader risk. When collaboration apps depend on shared web components, a browser update can affect daily work features such as meeting joins, chat input, or link handling.

What users should do now

Users who cannot join a Teams meeting on Windows should first restart the Teams desktop client. If the meeting still fails, they should try again after confirming that Edge has received the latest available update from their organization’s update channel.

If the problem continues, users should contact their IT helpdesk and mention Microsoft incident TM1288497. NHSmail users can also reference INC46806917 when reporting the problem internally.

Meeting organizers should also prepare a backup option for critical calls. That could include sharing dial-in details, rescheduling if many users are blocked, or asking affected participants to restart Teams before the meeting begins.

Recommended actions for IT admins

• Monitor Microsoft 365 admin center updates for TM1288497.
• Review NHSmail service alerts if your organization uses NHSmail.
• Tell affected users to restart the Teams desktop client.
• Confirm that Edge has updated to the replacement version.
• Track helpdesk reports involving scheduled meetings and meeting links.
• Avoid broad Teams policy changes unless Microsoft identifies a separate cause.
• Prepare fallback access steps for critical meetings.

IT teams should also watch for users who report the same symptoms after the updated Edge release has reached their devices. Those reports may help confirm whether the fix has fully propagated or whether some endpoints remain on the problematic version.

Current status

Microsoft has deployed an updated version of Edge to replace the release that introduced the regression. The company is now monitoring service health data to confirm that Teams meeting access recovers for affected Windows users.

The incident remained listed as ongoing in the latest NHSmail service alert. Microsoft’s next detailed admin-center update was scheduled for April 27, 2026, at 10:00 PM UTC, according to a mirrored Microsoft 365 incident feed.

For now, the key message is practical: restart Teams if meeting joins fail, make sure Edge receives the replacement update, and keep checking official service health alerts until Microsoft marks the incident resolved.

FAQ