Some users may have seen incorrect presence status information in Microsoft Teams
Operational Resolved
- Started
- Ended
- Affects
- Microsoft Teams
Timeline (UK time)
- Operational
A post-incident report has been published.
- Operational
A post-incident report has been published.
- Operational
A post-incident report has been published.
- Operational
A post-incident report has been published.
- Operational
A post-incident report has been published.
- Operational
Title: Some users may have seen incorrect presence status information in Microsoft Teams User impact: Some users may have seen incorrect presence status information in Microsoft Teams. Final status: We have confirmed through our telemetry and from some of the previously affected customers that the issue is now resolved. Scope of impact: This issue primarily affected users in EMEA, and users in other regions may have experienced impact when interacting with the affected users. Start time: Wednesday, June 17, 2026, at 8:30 AM UTC End time: Wednesday, June 17, 2026, at 9:35 AM UTC Root cause: The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live. A code bug in the configuration and subsequent miss in the review process resulted in the bad rollout file that was published to ATM. This resulted in inadvertently overwriting/replacing the existing full EMEA configuration that included all the existing data centers which were handling traffic, rather than being extended on top of the existing configuration. This meant that the service removed all the existing data centers from the ATM set-up for Presence and just left the newly added region, which was not in an operational state yet. As such, there were no reachable endpoints for Presence-related requests. Since Azure Front Door (AFD) has caching for last known good DNS endpoints, we had some protection for client-side presence scenarios and only when a user’s caches expired would they have seen impact. Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document. We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The second update was provided on August 31, 2026. The next update will be provided by September 30. 2026.
- Operational
Since we deployed the fix, we're observing a steady improvement in service recovery. We'll continue to monitor service telemetry for complete recovery. Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC This quick update is designed to give the latest information on this issue.
- Operational
We’ve identified that a recent Teams traffic routing change introduced a misconfiguration, which unexpectedly resulted in impact. We’ve deployed a fix and are closely monitoring service telemetry to ensure full recovery. Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC This quick update is designed to give the latest information on this issue.
- Operational
Title: Some users may see incorrect presence status information in Microsoft Teams User impact: Some users may see incorrect presence status information in Microsoft Teams. Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix. Scope of impact: This issue is primarily affecting users in EMEA, and users in other regions may experience impact when interacting with the affected users. Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
- Operational
Title: Possible delays or problems when accessing Microsoft Teams User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams. Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
Wording above is from Microsoft 365 service health. Original notice.