Users may have been unable to join Microsoft Teams meetings and saw sign-in errors.
- Status
- Service restored
- Feature
- Meetings
- Region
- Not specified (all regions)
- Started
- Oct 7, 2026, 03:00 CEST
- Resolved
- Oct 16, 2026, 05:30 CEST
- Duration
- 9 days 2 h
More info
Affected users saw a sign-in prompt when they attempted to join a meeting but clicking "sign-in" on the prompt had no effect.
Users can sign-out and sign back in as a temporary mitigation.
Scope of impact
Some users who attempted to join Microsoft Teams meetings may have been affected by this issue.
Root cause
A recent change to the authentication flow utilized in the event contained a regression, which resulted in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to the Microsoft Teams meetings and sign-in authentication path prior to deployment to prevent similar impact in the future, and to improve our pre-deployment update testing processes.
This is the final update for the event.
Final status
We've completed the deployment of our code fix to all affected environments and confirmed through telemetry, along with a subset of impacted users, that the issue is resolved.
Timeline
Every update Microsoft posted for this issue, newest first.
- Oct 16, 2026, 06:33 CEST
We've completed the deployment of our code fix to all affected environments and confirmed through telemetry, along with a subset of impacted users, that the issue is resolved.
- Oct 16, 2026, 02:35 CEST
Our code fix has nearly completed propagation throughout most of the affected environments and we're continuing to monitor it as it progresses. We anticipate it'll have fully propagated by our next scheduled communications update.
- Oct 14, 2026, 23:49 CEST
We've halted the code change causing this problem to ensure that no additional users encounter Microsoft Teams meeting join and sign-in errors. We're deploying a code fix to remediate the issue for users who received the code change prior to us halting it. Users will experience progressive relief from the issue as this deployment reaches them and we expect the code fix to propagate fully around the time of our next update.
- Oct 14, 2026, 04:06 CEST
We’re monitoring the rollback of the offending change and expect that a remediation timeline will be provided by our next scheduled communications update.
- Oct 14, 2026, 01:51 CEST
We've initiated our rollback of the responsible change and will monitor this rollback to provide a mitigation timeline as it becomes available.
- Oct 14, 2026, 00:00 CEST
We've confirmed a recent change to the authentication flow utilized in the event contained a regression, resulting in this impact. We're preparing to rollback this change in the affected environments and will provide a remediation timeline as soon as one becomes available.
- Oct 13, 2026, 20:56 CEST
We're continuing to review the logs provided by a subset of affected users alongside service side data in order to develop the most effective remediation steps.
- Oct 13, 2026, 19:18 CEST
We're reviewing the logs provided by a subset of affected users and have requested an additional set of fresh logs from those users to assist in pinpointing the underlying root cause of this event, so we may develop the most effective remediation steps.
- Oct 13, 2026, 18:57 CEST
We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
Subscribe to incidents in LEXOJ