Status Page

O365 - General

2025-07-10	Status	Description
10:29 AM		Status Service Degradation Impacted services Microsoft 365 suite Title: Some users may experience a loss of freshness for some data sources such as Organization Data in Microsoft 365 User impact: Users may experience a loss of freshness for some data sources such as Organization Data in Microsoft 365. More info: Specifically, impacted users may see that changes aren't reflecting, such as editing and adding new items, which aren't showing up, and the action of deleting items isn't actually deleting them as expected. Current status: We've identified a recent change to the portion of code facilitating the processing of user requests which contains a code issue that's preventing changes made to the impacted data sources from reflecting properly. We've halted the deployment of this change to ensure saturation doesn't continue, and we're reverting the deployment in our internal testing environment to validate that it remediates impact. Once our validation efforts are complete, we'll revert the offending deployment on a broader scale, and we'll aim to provide a resolution timeline once one becomes available. Scope of impact: Some users who are editing, adding, or deleting data sources such as Organization Data in Microsoft 365 may be impacted. Start time: Friday, June 27, 2025, at 5:30 PM UTC Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to the impacted data sources from reflecting properly. Next update by: Thursday, July 10, 2025, at 7:00 PM UTC
09:54 AM		Status Service Restored Impacted services Microsoft 365 suite Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services User impact: Users may have experienced latency or intermittent failures fetching user contacts in multiple Microsoft 365 services. More info: Affected services and scenarios included: - Microsoft Teams users were unable to fetch user's regional and language settings using the Profile API. - Exchange Online users experienced latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online. - Users may have been unable to see free/busy information for other users within their organization. Final status: We've reviewed the service health and confirmed it's stabilized and impact has been successfully remediated. Scope of impact: Users may have experienced latency or intermittent failures for user contact fetching across multiple Microsoft 365 services. Start time: Friday, July 4, 2025, at 12:00 AM UTC End time: Tuesday, July 8, 2025, at 2:00 PM UTC Root cause: A configuration change caused services to only route to a subset of available infrastructure due to an inventory cache probe being incorrectly quarantined, which led to impact across multiple services. Next steps: - We're further reviewing the service infrastructure and our testing of configuration changes to help prevent similar impact in the future. This is the final update for the event.

2025-07-08	Status	Description
09:30 AM		Status Service Degradation Impacted services Microsoft 365 suite Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services User impact: Users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services. More info: Affected services and scenarios include: - Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API - Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online. Current status: We've validated that a change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing. We've implemented an Enhanced Configuration Service (ECS) change to spread the service load and reduce latency for affected users. We're testing this ECS change with a subset of affected users, and we aim to provide a timeline to mitigation as one becomes available. Scope of impact: Users may experience latency or intermittent failures for user contact fetching across multiple Microsoft 365 services. Root cause: A change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing. Next update by: Monday, July 7, 2025, at 8:30 PM UTC