Microsoft Outage History

Started Oct 21, 2026, 01:27 PM UTC· resolved Oct 21, 2026, 02:09 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 19, 2026, 12:00 AM UTC· resolved Oct 21, 2026, 09:28 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 15, 2026, 07:15 AM UTC· resolved Oct 15, 2026, 08:20 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 14, 2026, 08:26 AM UTC· resolved Oct 14, 2026, 10:16 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 13, 2026, 07:40 AM UTC· resolved Oct 13, 2026, 06:43 PM UTC

1. monitoring Oct 13, 2026, 10:34 AM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section may be impacted. Next update by: Tuesday, October 13, 2026, at 11:30 AM UTC

2. monitoring Oct 13, 2026, 11:43 AM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We’ve identified that a section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. We’re applying performance and traffic optimizations to remediate impact and restore connectivity. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 1:30 PM UTC

3. monitoring Oct 13, 2026, 01:39 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're continuing to apply the aforementioned traffic and performance optimizations with early signals showing signs of recovery. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC

4. monitoring Oct 13, 2026, 02:38 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We've deployed the traffic optimizations and although we saw a reduction of errors initially, this did not fully resolve the issue. We're continuing to troubleshoot the issue to develop additional mitigation strategies. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC

5. monitoring Oct 13, 2026, 02:59 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're redirecting traffic from the underperforming infrastructure to improve service health. We're monitoring to confirm this will fully resolve impact. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC

6. monitoring Oct 13, 2026, 03:10 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're redirecting traffic from the underperforming infrastructure to improve service health. We're monitoring to confirm this will fully resolve impact. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC

7. monitoring Oct 13, 2026, 03:24 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We've completed redirecting traffic to healthy infrastructure and are assessing for positive trends towards recovery. We're continuing to investigate additional mitigating actions to expedite remediation. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Next update by: Tuesday, October 13, 2026, at 4:30 PM UTC

8. monitoring Oct 13, 2026, 04:25 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're restarting a portion of impacted infrastructure where we've removed traffic and are seeing positive trends towards recovery. We've confirmed through internal testing that this resolves impact for some users and we're monitoring to validate the full recovery of the service. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Next update by: Tuesday, October 13, 2026, at 5:30 PM UTC

9. monitoring Oct 13, 2026, 05:26 PM UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're continuing our targeted restarts throughout the impacted infrastructure, and our telemetry shows services hosted on the restarted infrastructure are now operating at healthy service levels. We're also receiving confirmation that impact is resolved for some users. Scope of impact: Some users in Germany attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 7:40 AM UTC Next update by: Tuesday, October 13, 2026, at 6:30 PM UTC

10. monitoring Oct 13, 2026, 06:20 PM UTC

    User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs As a workaround, users may disable GSA to access the affected Microsoft 365 services until the resolution of this incident. Current status: We're finishing our restarts throughout the affected infrastructure and expect this will be complete and resolve all impact by Tuesday, October 13, 2026, at 7:00 PM UTC. Our telemetry is showing service recovery, and we'll continue to monitor to ensure full remediation. Scope of impact: Some users in Germany attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 7:40 AM UTC Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC

Read the full incident report →

Started Oct 12, 2026, 09:54 PM UTC· resolved Oct 13, 2026, 10:38 PM UTC

1. monitoring Oct 13, 2026, 06:52 PM UTC

   User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We've received reports from a subset of affected users who have reported that they are unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. We've isolated that a recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. We're rolling back the offending update and monitoring for remediation. We anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 8:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC

2. identified Oct 13, 2026, 07:53 PM UTC

   User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We're continuing to monitor recovery, and we anticipate some users will start to see remediation at this time. To ensure impact is fully remediated, we've extended our monitoring period, and we anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 10:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC

3. monitoring Oct 13, 2026, 07:53 PM UTC

   User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We're continuing to monitor recovery, and we anticipate some users will start to see remediation at this time. To ensure impact is fully remediated, we've extended our monitoring period, and we anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 10:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC

4. identified Oct 13, 2026, 09:02 PM UTC

   User impact: Admins may have been unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Admins' "What's new" tab in the Microsoft Teams admin center may have been blank and displayed an error stating, "We can't load data. Try again." Final status: We've completed our monitoring period and validated that the rollback of the service update containing the misconfiguration successfully remediated impact. Scope of impact: This issue affected some admins attempting to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. Start time: Monday, October 12, 2026, at 9:54 PM UTC End time: Tuesday, October 13, 2026, at 7:35 PM UTC Root cause: A recent service update introduced a misconfiguration which caused the Service Health and Communications API to return authentication errors, resulting in impact. Next steps: - We're analyzing the offending service update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future. This is the final update for the event.

Read the full incident report →

Started Oct 08, 2026, 09:58 AM UTC· resolved Oct 08, 2026, 11:28 AM UTC

1. monitoring Oct 08, 2026, 09:58 AM UTC

   Azure Data Factory issues in UK SouthWe are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact.Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected.Further updates will be provided as more information becomes available.

2. monitoring Oct 08, 2026, 10:03 AM UTC

   We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact . Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected. Further updates will be provided as more information becomes available.

3. monitoring Oct 08, 2026, 10:11 AM UTC

   We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts with pipeline and activity runs, integration runtime management, or authoring operations. Our engineers are actively working to determine the cause and impact.As a workaround, customers are advised to cancel and retry affected runs that fail, time out, or remain in progress longer than expected

4. monitoring Oct 08, 2026, 10:12 AM UTC

   We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts with pipeline and activity runs, integration runtime management, or authoring operations. Our engineers are actively working to determine the cause and impact. As a workaround, customers are advised to cancel and retry affected runs that fail, time out, or remain in progress longer than expected.

Read the full incident report →

Started Oct 05, 2026, 10:28 PM UTC· resolved Oct 06, 2026, 03:19 AM UTC

1. monitoring Oct 05, 2026, 11:21 PM UTC

   Current status: We're investigating a potential issue impacting admin access to the Microsoft 365 admin portal in certain regions and we're checking for impact to your organization. We'll provide an update within 30 minutes.

2. monitoring Oct 05, 2026, 11:39 PM UTC

   User impact: Admins intermittently may be unable to access the Microsoft 365 admin center. Current status: We’re investigating an unusually large increase in requests to the Microsoft 365 admin center and expect that this increase is resulting in requests queuing and timing-out. We’re reviewing options for mitigating this issue and determining if other factors are contributing to the problem. Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. Next update by: Wednesday, October 6, at 12:30 AM UTC

3. monitoring Oct 06, 2026, 12:09 AM UTC

   User impact: Admins intermittently may be unable to access the Microsoft 365 admin center. Current status: We're continuing to analyze the unusually large increase in requests to the Microsoft 365 admin center along with recent service updates to isolate potential sources of impact that contributed to the traffic increase. We’ve implemented performance optimizations to assist with processing affected traffic and we've validated that service availability has recovered to pre-impact levels. We're continuing our investigation in order to isolate and remediate the underlying root cause to ensure the similar scenario does not occur again in the future. Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as the investigation progresses. Start time: Monday, October 5, 2026, at 10:28 PM UTC Next update by: Tuesday, October 6, 2026, at 1:30 AM UTC

4. monitoring Oct 06, 2026, 01:26 AM UTC

   User impact: Admins intermittently may have been unable to access the Microsoft 365 admin center. Final status: We've validated that an unexpected influx in requests caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center. We've implemented additional performance optimizations to assist with processing affected traffic. After completing an internal monitoring period, we've validated that impact is remediated. Scope of impact: Admins attempting to access the Microsoft 365 admin center may have been intermittently affected. Start time: Monday, October 5, 2026, at 10:28 PM UTC End time: Monday, October 5, 2026, at 11:37 PM UTC Root cause: An unexpected influx in requests and caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center. Next steps: - We're evaluating what additional performance optimizations or safeguards we can implement to further the resiliency of our service. This is the final update for the event.

Read the full incident report →

Started Sep 30, 2026, 08:30 PM UTC· resolved Oct 01, 2026, 02:15 AM UTC

1. monitoring Sep 30, 2026, 08:30 PM UTC

   We are investigating an alert for Azure ExpressRoute Gateway in multiple Azure regions. We will provide more information as it becomes available.

2. monitoring Sep 30, 2026, 08:30 PM UTC

   Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and/or Azure VPN Gateway may experience degraded or interrupted connectivity. We are also seeing impact to components responsible for managing network gateways, which may affect some management operations. Our investigation has identified a correlation between the onset of impact and infrastructure ‘operating system’ servicing activity. During this activity, some network gateway instances became unhealthy or temporarily unavailable. We have observed different recovery behavior across the affected services. Many impacted ExpressRoute gateways are recovering as the servicing operation completes. However, some supporting management components have not recovered automatically, and we are actively working to restore those components. Our current working hypothesis is that infrastructure operating system servicing is triggering an unexpected condition in some network service instances. We have not yet confirmed the underlying failure mechanism and are continuing to investigate why affected instances became unhealthy and why recovery behavior differs between services. We have paused further operating system servicing associated with this activity to prevent new instances from entering the affected servicing workflow. In parallel, our engineering teams are restoring network management components that have not recovered automatically as well as evaluating additional recovery actions for resources that remain unhealthy. We are continuing to monitor recovery across the affected services and will provide additional information within the next 30 minutes or as events warrant.

3. monitoring Sep 30, 2026, 08:30 PM UTC

   Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and/or VPN Gateway may experience degraded or interrupted network connectivity. Customers may also experience failures or delays when performing some network management operations. Current status: We have paused the infrastructure servicing activity associated with the onset of this event, preventing additional resources from entering the affected servicing workflow. We are seeing continued recovery across impacted ExpressRoute gateways and are monitoring this recovery to confirm that it remains durable. For VPN Gateway, some affected gateways have experienced reduced redundancy rather than a complete loss of connectivity. Recovery continues to be monitored. Some supporting network management components have not recovered automatically and are contributing to management operation failures in a subset of affected regions. Engineering teams are actively restoring these components using alternate healthy instances where available. Our investigation continues to show a correlation between this event and infrastructure operating system servicing activity. However, the underlying failure mechanism has not yet been confirmed. We are investigating why some network service instances became unhealthy and why recovery behavior has differed between services. We will provide additional information within the next 30 minutes, or sooner if events warrant.

4. postmortem Oct 01, 2026, 02:15 AM UTC

   Join either of our upcoming 'Azure Incident Retrospective' livestreams discussing this incident (to hear from our engineering leaders, and to get any questions answered by our experts) or watch a recording of the livestream (available the following week, on YouTube): • Option #1 - 18:30 to 19:00 UTC on 22 October 2026 - https://aka.ms/air/7Q30-010/1 • Option #2 - 06:30 to 07:00 UTC on 23 October 2026 - https://aka.ms/air/7Q30-010/2 What happened? Between 20:30 UTC on 30 September 2026 and 02:15 UTC on 1 October 2026, customers using several Azure networking services – including Azure ExpressRoute Gateway, Azure Application Gateway, Azure Firewall, Azure Bastion, Azure Virtual WAN, and Azure VPN Gateway – experienced intermittent failures when performing service management operations. In addition, a subset of upgraded Azure ExpressRoute gateways could not retrieve their required configuration from the control plane service, resulting in temporary connectivity loss. Customers using Azure VMware Solution may also have temporarily lost network connectivity to their software-defined datacenter environments. The issue affected multiple regions including Australia Central 2, Australia Southeast, Austria East, Belgium Central, Canada East, Central US, Chile Central, Denmark East, East Asia, France Central, Germany North, Germany West Central, India South Central, Indonesia Central, Japan West, Jio India Central, Korea Central, Malaysia West, North Europe, Norway West, South Africa North, South Central US, South India, Southeast Asia, Sweden South, Switzerland North, Taiwan North, UAE North, UK South, West Europe, West US, West US 2, and West US 3. The issue began when a platform-triggered gateway update resumed across multiple regions, increasing request volume to the regional gateway control plane service, thereby affecting its ability to process management operations reliably. Impact times varied region by region, as the issue was triggered by a rolling update moving through the regions. We paused this update while applying a configuration change in phases to restore the control plane service. The last wave of customer impact was mitigated at 02:15 UTC on 1 October 2026. What went wrong and why? Azure regularly applies operating system and security updates to networking gateway services. These updates are designed to roll out gradually across deployment stages and redundant gateway instances, allowing service health to be evaluated before updates proceed. Before this incident, a temporary deployment restriction had paused operating system updates for a group of networking gateways. When this restriction expired, a large number of gateway updates resumed within a short period, generating a surge in gateway restarts and configuration-retrieval requests. At the same time, a previously deployed change had increased the processing time required for configuration operations handled by a shared regional networking control plane service. The combination of increased request volume and longer processing times overwhelmed the control plane, affecting its ability to process requests reliably. As a result, management operations for several Azure networking services failed intermittently. Existing request-throttling and load-protection mechanisms did not sufficiently protect critical processing under these conditions. For Azure ExpressRoute Gateway, an additional issue prolonged connectivity impact. Gateway instances restarting during the update process were marked healthy before their configuration and routing state had been fully restored. This allowed updates to proceed to another redundant instance before the first instance was ready. Consequently, some gateways temporarily lost connectivity to connected on-premises networks because neither instance could retrieve the required routing configuration. After approximately 30 minutes of unsuccessful configuration-retrieval attempts, the affected gateways automatically applied their locally stored last known good (LKG) configurations and restored connectivity. Automated monitoring detected ExpressRoute connectivity degradation at 20:43 UTC on 30 September 2026, followed by broader control plane degradation at 20:58 UTC. We pursued several recovery approaches in parallel, including pausing further gateway updates at 21:45 UTC, shifting control plane traffic, and attempting to add resources. Although these actions provided temporary relief, they did not fully resolve the issue. Further investigation identified the combination of elevated request volume and increased processing time per operation as the primary contributing factors. Once this was understood, we began rolling back the change that had increased control plane processing time, starting at 01:15 UTC on 1 October 2026. The rollback was applied across the affected regions, and customer impact ended at 02:15 UTC. How did we respond? • 20:30 UTC on 30 September 2026 – Customer impact began, with intermittent failures affecting management operations across multiple Azure networking services. • 20:43 UTC on 30 September 2026 – ExpressRoute monitoring detected connectivity degradation. • 20:58 UTC on 30 September 2026 – Control plane monitoring detected health failures across additional regions. • 21:12 UTC on 30 September 2026 – Multiple teams were engaged to investigate the issue and coordinate response efforts. • 21:45 UTC on 30 September 2026 – Further gateway operating system updates were paused to prevent additional update activity. • 22:09 UTC on 30 September 2026 – Traffic shifting actions provided temporary relief, but elevated resource utilization returned. Further traffic shifts were stopped. • 22:15 UTC on 30 September 2026 – Attempts to add control plane resources were investigated, and constraints involving dependent platform services were addressed. • 22:36 UTC on 30 September 2026 – Affected ExpressRoute gateways automatically restored connectivity using their last known good configurations. • 23:55 UTC on 30 September 2026 – We identified increased processing time for gateway configuration operations were associated with a previously deployed performance change, so we determined that a rollback would be a relevant mitigation. • 01:15 UTC on 1 October 2026 – The rollback began in an initial region, where the results were validated before proceeding. • 02:15 UTC on 1 October 2026 – The rollback was completed across the affected regions, and customer impact ended. How are we making incidents like this less likely or less impactful? • We have rolled back the change that introduced the performance regression, to de-risk this failure mode immediately. (Completed) • We are improving how paused operating system updates resume, to ensure they follow staged rollout practices rather than resuming across large numbers of gateways at once. (Estimated completion: October 2026) • We are strengthening ExpressRoute gateway health checks, to ensure that redundant instances are updated only after the initial instances have fully restored its configuration and routing state. (Estimated completion: March 2027) • We are addressing platform issues that prevented the control plane service from scaling out successfully during the incident. (Estimated completion: March 2027) • In the longer term, we are improving throttling and load-shedding mechanisms in the control plane service to help protect critical request processing during unexpected increases in demand. (Estimated completion: June 2027) How can customers make Incidents like this less impactful? • There was nothing that customers could have done to avoid or minimize impact from this specific service incident. • More generally, consider evaluating the reliability of your applications using guidance from the Azure Well-Architected Framework and its interactive Well-Architected Review: https://aka.ms/AzPIR/WAF • The impact times above represent the overall incident duration and are not specific to any individual customer. Actual impact varied by service, region, customer, and resource. For guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring • Finally, consider ensuring that the right people in your organization are notified about any future service issues by configuring Azure Service Health alerts. These can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/AzPIR/Alerts How can we make our incident communications more useful? You can rate this PIR and provide any feedback using our quick 3-question survey: https://aka.ms/AzPIR/7Q30-010

5. postmortem Oct 01, 2026, 02:15 AM UTC

   Incorrect Region: correction: Impacted region(s) within a previous communication has been corrected. What happened? Between 20:30 UTC on 30 September 2026 and 02:15 UTC on 01 October 2026, a subset of customers using gateway services in multiple regions experienced degraded or interrupted network connectivity. Impacted customers may have observed gateways failing to load in the Azure Portal, along with failures or delays in network management operations across the following impacted services. • Azure ExpressRoute Gateway • Azure Firewall • Azure Application Gateway and Web Application Firewall • Azure VPN Gateway • Azure VMware Solution What do we know so far? Our investigation identified that a recent change to a regional gateway management service triggered a higher-than-expected load when an unrelated operating system servicing maintenance proceeded gradually through multiple regions. Normally, this gateway management service would auto scale as needed. Demand on dependent services increased due to the increased workload, preventing these regional services from scaling as expected. The operating system servicing maintenance was paused as a precaution. We reverted the contributing regional gateway manager change, which reduced gateway manager load and allowed affected services to recover. We are continuing to investigate the scaling behavior and the safeguards needed to help prevent recurrence. How did we respond? • 20:30 UTC on 30 September 2026 – Customer impact began. • 21:29 UTC on 30 September 2026 – We began investigating connectivity issues affecting Azure ExpressRoute Gateway in UK South. • 22:27 UTC on 30 September 2026 – We identified that the issue was affecting multiple Azure regions and expanded our investigation. • 23:05 UTC on 30 September 2026 – We identified a correlation with operating system servicing activity and paused further servicing while we worked to restore affected services. • 01:36 UTC on 01 October 2026 – Recovery progressed across most affected regions, while configuration changes were applied to remaining impacted regions, including France Central, North Europe, Southeast Asia, UK South, and UK West. • 02:15 UTC on 01 October 2026 – We confirmed that the issue was mitigated. What happens next? • Our team will be completing an internal retrospective to understand the incident in more detail. Once that is completed, generally within 14 days, we will publish a Post Incident Review (PIR) to all impacted customers. • To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts. • For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs. • The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring • Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness.

Read the full incident report →

Started Sep 29, 2026, 10:00 AM UTC· resolved Sep 29, 2026, 03:58 PM UTC

1. monitoring Sep 29, 2026, 10:00 AM UTC

   We are investigating an issue affecting Azure OpenAI and Foundry agent services in the Sweden Central region. Impacted customers may experience intermittent errors when making service requests. We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation. We will provide additional information as it becomes available.

2. monitoring Sep 29, 2026, 10:00 AM UTC

   We are investigating an issue affecting Azure OpenAI Service, Azure AI Foundry Agent Service, Azure AI Foundry Models, and Azure AI Cognitive Services in the Sweden Central region. Impacted customers may experience intermittent request failures, increased latency and HTTP 5XX error codes when making service requests. We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation. We will provide additional information as it becomes available.

3. monitoring Sep 29, 2026, 10:00 AM UTC

   Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Initial findings indicate that a backend service which is relied on to retrieve metadata information when managing requests for this region, was experiencing timeouts when reading from dependent database and caching layers. As a result, requests that depend on these processes were delayed or failed intermittently. Queued requests are being processed. We are continuing to investigate the health of supporting platform infrastructure or system processes that may impact these requests. The next update will be provided within 60 minutes, or as events warrant.

4. postmortem Sep 29, 2026, 03:58 PM UTC

   Join either of our upcoming 'Azure Incident Retrospective' livestreams discussing this incident (to hear from our engineering leaders, and to get any questions answered by our experts) or watch a recording of the livestream (available the following week, on YouTube): • Option #1 - 17:30 to 18:00 UTC on 22 October 2026 - https://aka.ms/air/7QL5-Z50/1 • Option #2 - 05:30 to 06:00 UTC on 23 October 2026 - https://aka.ms/air/7QL5-Z50/2 What happened? Between 10:03 UTC and 15:58 UTC on 29 September 2026, a platform issue resulted in impact to Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services in the Sweden Central region. Impacted customers experienced intermittent request failures, increased latency, and/or HTTP 500 and 503 errors when submitting requests to affected models and data plane APIs hosted in this region. Note that the Azure OpenAI Service processes customer requests through model engines deployed across multiple Azure regions and supported by traffic routing systems. Depending on the selected deployment model (Global, Data Zone, or Regional), note that requests may be routed across multiple Azure regions within defined geographic boundaries to support availability and resilience, while customer data remains stored at rest in the selected Azure region. Learn more at: https://azure.microsoft.com/blog/enterprise-trust-in-azure-openai-service-strengthened-with-data-zones/ What went wrong and why? When requests are made to Azure OpenAI Service and related Azure AI services in a region, the service relies on a regional backend service to retrieve resource metadata and configuration information for the account making the request. This backend service reads from a caching layer and a database layer. Other internal services that call this backend service maintain their own caches of this information, to reduce load on the backend service. At approximately 09:38 UTC on 29 September 2026, a planned deployment of one of these internal services began in Sweden Central. As part of this deployment, the internal service's caches were cleared and - because the deployment coincided with peak traffic hours in the region - this produced a large number of cache misses, where requests were made for information no longer stored in the cache. Two other defects in how that service read from its caches amplified this effect, causing most lookups to bypass the cache and fall back to calling the backend service directly. By approximately 10:00 UTC, traffic to the backend service had increased to approximately 20 times its normal level. This surge drove a sharp increase in requests from the backend service to its caching layer, which reached full utilization, thereby increasing latency. This higher latency caused connections to be held open longer, while client retries added further requests. As a result, the network connection capacity on the infrastructure node instances was exhausted, so new outbound connections to both the caching layer and the database layer could not be established. While this traffic surge was a trigger, the extended duration of the incident was primarily caused by how the backend service determined whether its instances were healthy. Automated health checks for each instance depended on successfully connecting to the database layer. When instances could not establish new outbound connections, they failed this health check and were automatically restarted by design. As more instances entered this restart loop, fewer healthy instances remained to serve requests, and retries from dependent services further increased the load on the remaining instances. Multiple factors also extended the duration of the incident. Existing network metrics and diagnostic metrics did not effectively indicate the connection exhaustion issue in this scenario. It took an extended amount of time to correlate the failures with what was causing this specific connection exhaustion scenario. As a result, different mitigation attempts - including scaling the number of service instances, and increasing compute and memory resources - could not resolve the incident, until the health check issue was identified and mitigated. How did we respond? • 09:38 UTC on 29 September 2026 – A deployment of an internal service in Sweden Central began, which cleared its caches. • 10:00 UTC on 29 September 2026 – Traffic to the backend service began increasing sharply. • 10:03 UTC on 29 September 2026 – Customer impact began because of service instance instability. • 10:17 UTC on 29 September 2026 – Service monitoring detected elevated failure rates for Azure OpenAI Service requests in the region, and alerted our engineering teams. • 10:28 UTC on 29 September 2026 – Engineers were engaged and investigating the issue. • 11:21 UTC on 29 September 2026 – Additional engineering teams were engaged, ongoing deployments were reviewed for the Azure OpenAI Service in Sweden Central to determine whether any recent change correlated with the issue. • 11:30 UTC on 29 September 2026 – We identified that infrastructure node service instances were experiencing timeouts when attempting to connect to the backend service's caching and database layers. • 13:55 UTC on 29 September 2026 – We confirmed that the database layer was healthy. We made attempts to mitigate through different scaling adjustments of service instances to lower the number of outbound connections, which did not result in significant improvements. • 15:00 UTC on 29 September 2026 – We further increased compute resources for the backend service and increased its resource limits. In parallel, we investigated infrastructure health for affected service instances and restarted service instances. • 15:40 UTC on 29 September 2026 – We reconfigured the automated health check to no longer depend on remote connectivity, which stopped the restart loop. Service availability began to recover. • 15:58 UTC on 29 September 2026 – Service availability had recovered, and customer impact was mitigated. • 16:30 UTC on 29 September 2026 – We identified the source of the increased traffic and correlated it with the internal service deployment, while monitoring confirmed that services were stable. How are we making incidents like this less likely or less impactful? • We have reconfigured the automated health check for the backend service so that it no longer depends on connectivity to its database layer, preventing instances from being restarted unnecessarily during dependency issues. (Completed) • We have added monitoring and alerting on the load and latency of the caching layer used by the backend service. (Completed) • We have updated our troubleshooting and procedural guidance for such connection exhaustion scenarios, to assist on-call engineers in mitigating similar scenarios. (Completed) • We are adding additional throttling and rate limiting for the backend service, to protect it from sudden increases in traffic. (Estimated completion: October 2026) • We are increasing the resource capacity of the caching layer used by the backend service across regions. (Estimated completion: October 2026) • We are improving diagnostic metrics and automated detection, to help identify such issues more quickly. (Estimated completion: October 2026) • In the longer term, we are partitioning the caching layer used by the backend service to increase its throughput. (Estimated completion: December 2026) How can customers make incidents like this less impactful? • Consider reviewing our guidance and best practices related to Business Continuity and Disaster Recovery (BCDR) scenarios for Microsoft Foundry: https://learn.microsoft.com/azure/foundry/how-to/high-availability-resiliency • Consider reviewing and implementing our best practices surrounding retry patterns, especially with exponential backoff, to improve workload resiliency during intermittent issues: https://learn.microsoft.com/azure/architecture/patterns/retry • More generally, consider evaluating the reliability of your applications using guidance from the Azure Well-Architected Framework and its interactive Well-Architected Review: https://aka.ms/AzPIR/WAF • The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability varied between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring • Finally, consider ensuring that the right people in your organization will be notified about any future service issues – by configuring Azure Service Health alerts. These can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/AzPIR/Alerts How can we make our incident communications more useful? You can rate this PIR and provide any feedback using our quick 3-question survey: https://aka.ms/AzPIR/7QL5-Z50

Read the full incident report →

Started Sep 16, 2026, 01:22 PM UTC· resolved Sep 16, 2026, 06:21 PM UTC

1. monitoring Sep 16, 2026, 02:29 PM UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. Current status: We're reviewing service monitoring telemetry and associated reports to isolate the root cause, in order to develop a remediation plan. Scope of impact: Impact is specific to users in the United States and United Kingdom attempting to access Microsoft 365 services. This information may be updated as our investigation continues. Next update by: Wednesday, September 16, 2026, at 3:30 PM UTC

2. monitoring Sep 16, 2026, 02:35 PM UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. Current status: We're reviewing service telemetry while investigating reports of users encountering 502 and 503 errors when accessing Microsoft 365 services. Recent user reports indicate the impact may be decreasing and we're continuing to analyze service health data to determine whether service conditions are improving and to isolate the source of impact. Scope of impact: Impact is specific to users attempting to access Microsoft 365 services and users whose service requests are routed through the United States and United Kingdom regions. This information may be updated as our investigation continues. Next update by: Wednesday, September 16, 2026, at 3:30 PM UTC

3. monitoring Sep 16, 2026, 03:15 PM UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services. Current status: Our investigation remains focused on the cause of the Single Sign-On (SSO) failures and associated 5xx errors. In parallel, we're reviewing upstream dependencies to determine whether they are contributing to the impact. While some affected customers have reported improvement in service availability, our investigation continues as we work towards a full resolution. Start time: Wednesday, September 16, 2026, at 1:22 PM UTC Next update by: Wednesday, September 16, 2026, at 4:30 PM UTC

4. monitoring Sep 16, 2026, 04:47 PM UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services. Current status: Impact reports continue to decrease. Our investigation has not identified any issues with core Microsoft 365 components. As part of our ongoing root cause analysis, we're focusing on the request paths and dependency conditions associated with the reported Single Sign-On (SSO) failures and 5xx errors, while continuing to monitor and confirm sustained recovery. Start time: Wednesday, September 16, 2026, at 1:22 PM UTC Next update by: Wednesday, September 16, 2026, at 5:30 PM UTC

5. monitoring Sep 16, 2026, 05:59 PM UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services. Current status: Impact reports have largely subsided, and service telemetry continues to indicate stable service conditions. Our investigation hasn’t identified a corresponding issue within the Microsoft 365 service environment, and we’re assessing whether conditions outside the core service path contributed to the reported impact. We’re continuing to monitor service health and validate sustained recovery. Start time: Wednesday, September 16, 2026, at 1:22 PM UTC Next update by: Wednesday, September 16, 2026, at 6:30 PM UTC

Read the full incident report →

Started Sep 03, 2026, 10:03 AM UTC· resolved Sep 03, 2026, 10:36 AM UTC

1. monitoring Sep 03, 2026, 10:03 AM UTC

   We are investigating an issue affecting a subset of infrastructure within the East US region. Customers may experience service degradation for dependent Azure services. Our teams are actively investigating the cause and working to restore normal operations. More information will be provided as it becomes available.

Read the full incident report →

Started Aug 31, 2026, 03:08 PM UTC· resolved Sep 03, 2026, 08:08 PM UTC

1. monitoring Aug 31, 2026, 07:38 PM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. Microsoft Purview: Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: Users may experience intermittent authorization failures across solutions in Defender. Current status: We're continuing to perform comprehensive tests to ensure our mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, we're exploring alternative remediation avenues to minimize impact in the interim. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Monday, August 31, 2026, at 8:30 PM UTC

2. monitoring Aug 31, 2026, 08:39 PM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues with the administration of Exchange Online functionality, such as updating user aliases. Current status: We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including reverting an update the affected infrastructure recently received. We're performing additional tests to determine whether this will provide relief. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start Time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Monday, August 31, 2026, at 10:00 PM UTC

3. monitoring Aug 31, 2026, 10:03 PM UTC

   Start Time: Monday, August 31, 2026, at 3:08 PM UTC Next update by: Monday, August 31, 2026, at 11:00 PM UTC Current status: We're continuing our targeted review of affected infrastructure and recent changes made to the service to definitively confirm the cause of impact. We're additionally continuing to test and implement various mitigation strategies to apply the necessary authentication component, which have so far yielded positive results. We're monitoring these tests and mitigative actions closely and will provide an estimated time to resolution as soon as one is available. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. Microsoft Purview: Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: Admins may experience issues authenticating into the admin center. Universal Print: Users may be unable to create, upload, or retrieve print jobs.

4. monitoring Aug 31, 2026, 10:21 PM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues with the administration of Exchange Online functionality, such as updating user aliases. Current status: We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including reverting an update the affected infrastructure recently received. We're performing additional tests to determine whether this will provide relief. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start Time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Monday, August 31, 2026, at 10:00 PM UTC

5. monitoring Aug 31, 2026, 11:00 PM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're continuing to implement a targeted mitigation to re-apply core authentication components, and we're expanding this action more widely across the affected environments as we closely track the recovery of affected downstream scenarios. Users may notice gradual recovery to the scenarios identified in the "More info" section as our mitigation action takes effect in their corresponding sections of infrastructure, and we're continuing to review whether any additional actions may be required to achieve withstanding recovery across all affected scenarios. We'll provide an estimated time to resolution as soon as one is available. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC

6. monitoring Sep 01, 2026, 12:01 AM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're progressively restarting targeted sections of affected infrastructure to ensure the re-applied authentication components are effectively implemented across affected services. We expect this will aid the recovery of affected scenarios. Users should expect delayed delivery of backlogged messages and residual impact across downstream scenarios as these actions are continuing. We'll provide an expected recovery time as soon as one becomes available to us. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 1:00 AM UTC

7. monitoring Sep 01, 2026, 01:00 AM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We’re seeing improvement across the affected environments as we observe the successful albeit gradual implementation of our mitigation actions. Users should expect to see varying degrees of recovery and residual delays until these actions have completed. We're closely monitoring the health of the service environment and will continue to aggressively pursue any available options to expedite our ongoing recovery work, and we'll provide an estimated recovery timeline as soon as one becomes available. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 2:00 AM UTC

8. monitoring Sep 01, 2026, 01:55 AM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're closely monitoring the health of the service environment amidst our ongoing recovery work, and we're observing some sections of affected infrastructure which aren't accepting the re-applied authentication components as readily as expected. Users can expect to see continued recovery to email delivery, while users may see residual impact to downstream and dependent scenarios, including search, across affected services. We're working to identify whether any additional actions are required to expedite full recovery. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 3:00 AM UTC

9. monitoring Sep 01, 2026, 02:55 AM UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. Current status: We're observing residual impact to some downstream scenarios, including search. We're incrementally restarting corresponding instances of infrastructure to ensure our previously applied authentication components are fully saturated, and we're working to identify whether any additional actions are required to achieve resolution. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 4:00 AM UTC

10. monitoring Sep 01, 2026, 03:51 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're observing widespread recovery to Exchange Online mail connectivity, though the draining of backlogged mail queues may take longer for some organizations due to the volume of previously queued messages. Our recovery efforts are now focused on re-applying our targeted authentication component fix and restarting certain instances of infrastructure correlated with search functionality to ensure the full restoration of the associated scenarios. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 5:00 AM UTC

11. monitoring Sep 01, 2026, 05:02 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're persistently reviewing what additional actions may be required to re-apply our targeted authentication component fix and facilitate the recovery of remaining sections of infrastructure correlated with search functionality to ensure the full remediation. Meantime, we've validated persistent recovery for mail flow across the environment and are focusing our work on recovering search functionality. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC

12. monitoring Sep 01, 2026, 05:55 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're continuing our work to restart affected infrastructure and re-apply the targeted authentication component fix to recover search functionality across the affected environments. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 7:00 AM UTC

13. monitoring Sep 01, 2026, 06:39 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: Our efforts to restart affected sections infrastructure and re-apply the targeted authentication component fix has yielded progress, and we're observing incremental improvement reflected in the service health telemetry associated with search functionality across a sample of the affected environment. We're continuing this action for additional sections of infrastructure as we monitor closely to ensure widespread remediation. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC

14. monitoring Sep 01, 2026, 08:03 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: Reapplying the targeted authentication component fix and restarting affected infrastructure segments has led to measurable progress. We're observing gradual improvements within telemetry data related to search functionality across the remaining affected infrastructure, and we're continuing this remediation effort across additional infrastructure segments while closely monitoring service health telemetry to ensure we're progressing towards a broader recovery. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 9:00 AM UTC

15. monitoring Sep 01, 2026, 08:57 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: -Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. -Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. -Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: -Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: -Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. -Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: -Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: -Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: -Admins may experience issues authenticating into the admin center. Universal Print: -Users may be unable to create, upload, or retrieve print jobs. Current status: We're continuing to reapply the targeted authentication component fix to the remaining affected infrastructure where necessary. While our remediation effort is underway, indications from service telemetry remain positive. We're observing an overall increase in service availability, and we're monitoring this closely to ensure we're progressing towards a broad mitigation. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 10:00 AM UTC

16. monitoring Sep 01, 2026, 10:04 AM UTC

    More info: More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Microsoft Teams: - Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: - Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: - Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Current status: We're continuing to apply the targeted authentication component fix across the remaining affected infrastructure where necessary. Service telemetry continues to indicate recovery, with availability increasing across previously impacted scenarios as remediation progresses. We're validating that authentication, connectivity and search operations are returning to expected service levels while monitoring for any residual impact and confirming that the remediation is delivering broad mitigation across affected Exchange Online scenarios. As recovery signals continue to trend positively, we're maintaining extended monitoring across affected service workflows to ensure improvements are sustained. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC

17. monitoring Sep 01, 2026, 01:54 PM UTC

    More info: More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft Teams: - Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: - Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: - Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Current status: We're continuing to apply the targeted authentication component fix across the remaining affected infrastructure where necessary. Service telemetry continues to indicate recovery, with availability increasing across previously impacted scenarios as remediation progresses. We're validating that authentication, connectivity and search operations are returning to expected service levels while monitoring for any residual impact and confirming that the remediation is delivering broad mitigation across affected Exchange Online scenarios. As recovery signals continue to trend positively, we're maintaining extended monitoring across affected service workflows to ensure improvements are sustained. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC

18. monitoring Sep 01, 2026, 02:19 PM UTC

    More info: More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft Teams: - Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: - Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: - Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Current status: We're continuing to apply the targeted remediation across the remaining affected infrastructure where needed. Service telemetry continues to show positive recovery trends, with availability improving across previously impacted scenarios. We're actively validating that authentication, connectivity, and search experiences are returning to expected service levels, while maintaining enhanced monitoring to ensure improvements are sustained and any residual impact is addressed. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC

19. monitoring Sep 01, 2026, 03:59 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft Teams: - Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft Purview: - Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal. Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed. Microsoft Defender XDR: - Users may experience intermittent authorization failures across solutions in Defender. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Current status: Service telemetry continues to indicate recovery across previously impacted scenarios as remediation progresses through the remaining affected infrastructure. Core Exchange Online experiences, including mail flow and search functionality, have recovered. Our focus has shifted toward validating recovery across remaining Microsoft 365 services. We're actively monitoring service health, assessing any residual pockets of impact, and confirming end-to-end functionality across affected workloads. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 5:00 PM UTC

20. monitoring Sep 01, 2026, 04:59 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft Teams: - Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Current status: We've observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Our focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. We're maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC

21. monitoring Sep 01, 2026, 06:26 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft Teams: - Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Current status: We are carefully implementing corrective actions while maintaining enhanced monitoring to ensure services remain stable as recovery progresses. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 7:00 PM UTC

22. monitoring Sep 01, 2026, 07:02 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft Teams: - Users may experience issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail. - Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Current status: We’re continuing to advance multiple workstreams to restore service and prevent additional impact. We’re prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, we’re investigating remaining reports of impact and evaluating additional actions to support full service recovery. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Tuesday, September 1, 2026, at 10:30 PM UTC

23. monitoring Sep 01, 2026, 10:31 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may be unable to connect to Exchange Web Services (EWS) Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC

24. monitoring Sep 02, 2026, 01:32 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may be unable to connect to Exchange Web Services (EWS) Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Current status: We're continuing to closely monitor service health as we carefully expand our reiterative corrective actions across additional regions. This work involves re-deploying our targeted fixes to the dependent authentication components to ensure service resilience, while balancing ongoing traffic patterns to avoid additional residual impact. Most users should see recovery across the majority of impacted scenarios, though some scenarios, including those reliant on Graph API and Representational State Transfer (REST) connection methods, will remain degraded until our mitigation efforts are complete. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 3:30 AM UTC

25. monitoring Sep 02, 2026, 03:32 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may be unable to connect to Exchange Web Services (EWS) Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Current status: Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC

26. monitoring Sep 02, 2026, 04:41 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may be unable to connect to Exchange Web Services (EWS) - Users may be unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Current status: Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC

27. monitoring Sep 02, 2026, 06:45 AM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may be unable to connect to Exchange Web Services (EWS) - Users may be unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may experience issues authenticating into the admin center. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. Resolved Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Current status: Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC

28. monitoring Sep 02, 2026, 01:48 PM UTC

    More info: More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. Microsoft Graph: - Users may experience failures for scenarios that rely on access to Exchange Online data. *RECOVERED* Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail. - Users may experience failures for scenarios that rely on access to Exchange Online data. - Users prompts may fail or they may experience degradation when utilizing Cowork. Current status: We're continuing to observe positive recovery trends across the affected environments, with service availability remaining stable above 99 percent. Based on our telemetry, we expect the vast majority of previously impacted users should no longer be experiencing issues related to this event. Our deployment activities are progressing as expected, and we're continuing to implement the remaining portions of our remediation across affected infrastructure to help ensure recovery is sustained over time. We remain focused on validating end-to-end service health, monitoring for any residual impact, and confirming that recovery is maintained for scenarios that rely on REST and Graph API connection methods. While a small subset of users may still encounter intermittent impact as the deployment continues to progress, current telemetry indicates continued improvement and no signs of broader service degradation. We're maintaining enhanced monitoring and will provide further updates as recovery work continues. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC

29. monitoring Sep 02, 2026, 04:30 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. Current status: Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 5:30 PM UTC

30. monitoring Sep 02, 2026, 05:25 PM UTC

    More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. OneDrive for Business and SharePoint Online: - Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may be unable to create, upload, or retrieve print jobs. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. Current status: We’re working on additional mitigation measures for the portion of infrastructure which have not yet returned to healthy service levels after deployment of our primary remediation. Service availability remains above 99 percent and our monitoring shows impact is resolved for the majority of users. We remain engaged and committed to fully resolving this issue for all users. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC

31. monitoring Sep 02, 2026, 06:31 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We've confirmed that impact related to OneDrive for Business, SharePoint Online, and Universal Print are now resolved. We recognize that while the majority of services are restored for most users, the remaining issues are disruptive for those still impacted. We're continuing to address residual impact with the highest priority so we can ensure resolution for all users. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC

32. monitoring Sep 02, 2026, 08:04 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: The majority of services are restored for most users, and we continue to observe broad service recovery. We recognize that some users may still experience residual impact, and addressing these remaining scenarios continues to be our highest priority. We’re actively progressing our mitigation efforts and closely monitoring service health as we work to ensure full recovery for all users. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC

33. monitoring Sep 02, 2026, 10:01 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We continue to see sustained recovery across the affected services, with most users no longer experiencing impact. We’re continuing to focus on the remaining areas of impact and are progressing our mitigation efforts to address these residual scenarios. We’re closely monitoring service health throughout this work to maintain stability. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 12:30 AM UTC

34. monitoring Sep 03, 2026, 08:29 AM UTC

    More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From Purview Communications compliance perspective, this issue is mitigated. Customers should be able to use the portal. We are running backfill for any missed policy hits and those should appear in the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 10:30 AM UTC

35. monitoring Sep 03, 2026, 09:27 AM UTC

    More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 10:30 AM UTC

36. monitoring Sep 03, 2026, 10:25 AM UTC

    More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 12:30 PM UTC

37. monitoring Sep 03, 2026, 12:28 PM UTC

    More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We're continuing to implement further mitigation actions where required to resolve any outstanding impact associated with this incident. Customer feedback and reports from our telemetry remain positive, and service health is stable. While this work is underway, we're actively monitoring the service closely to ensure stability is consistent. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 2:30 PM UTC

38. monitoring Sep 03, 2026, 02:27 PM UTC

    More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: While monitoring service telemetry closely, we identified a small volume of errors affecting mail flow functionality. We're conducting targeted restarts to reduce the number of errors and alleviate impact. In parallel, we're continuing to analyze service health telemetry to determine if any additional mitigation actions are required to restore normal functionality. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 4:30 PM UTC

39. monitoring Sep 03, 2026, 04:25 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact is currently limited to Outlook on the web, Outlook mobile apps, and Outlook for Mac. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves. Exchange Online: - Users can't download email message attachments through any Exchange Online connection method. - Users may be unable to sign in to Outlook on the web. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: We discovered an issue in less than one percent of our infrastructure, where our additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. We remain committed to restoring all services to all users and will continue to carefully monitor our telemetry to ensure recovery. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Thursday, September 3, 2026, at 6:30 PM UTC

40. monitoring Sep 03, 2026, 06:41 PM UTC

    User impact: Users may experience issues when utilizing multiple Microsoft 365 services. More info: Impact is now fully resolved. Previously identified impact included the services and scenarios listed below. RECOVERED Microsoft Graph: - Users may have experienced failures for scenarios that rely on access to Exchange Online data. Exchange Online: - Service telemetry indicates recovery of core mail flow and search functionality. - Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios. - Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected. - Users may have been unable to connect to Exchange Web Services (EWS) - Users may have been unable to use room finder in Outlook calendars. - Users couldn’t download email message attachments through any Exchange Online connection method. - Users may have been unable to sign in to Outlook on the web. Outlook for iOS and Android: - Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center: - Admins may have experienced issues authenticating into the admin center. Microsoft Purview: - Users can now access the Microsoft Purview portal. - Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues. - From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR: - Users may have experienced intermittent authorization failures across solutions in Defender. Microsoft Teams: - Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed. - Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center. - Users may have experienced issues creating, deleting, and editing Teams channels. - Users may have experienced issues with calendar functionality. Microsoft 365 Copilot: - Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed. - Users may have experienced failures for scenarios that rely on access to Exchange Online data. - Users prompts may have failed or they may have experienced degradation when utilizing Cowork. OneDrive for Business and SharePoint Online: - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news. - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback. - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print: - Users may have been unable to create, upload, or retrieve print jobs. Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update. Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event. Start time: Monday, August 31, 2026, at 3:08 PM UTC Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Friday, September 4, 2026, at 6:30 PM UTC

Read the full incident report →

Started Aug 28, 2026, 06:19 AM UTC· resolved Aug 28, 2026, 07:01 AM UTC

1. monitoring Aug 28, 2026, 06:19 AM UTC

   We are investigating an issue impacting multiple Azure services in the West US regions. Engineering teams are actively assessing the scope and working to mitigate customer impact. Further updates will be shared as they become available

Read the full incident report →

Started Aug 25, 2026, 04:36 AM UTC· resolved Aug 25, 2026, 06:11 AM UTC

1. monitoring Aug 25, 2026, 04:03 AM UTC

   We are investigating an issue affecting a subset of infrastructure within the Southeast Asia region. Customers may experience connectivity issues or service degradation for dependent Azure services. Engineers are actively investigating the cause and working to restore normal operations. More information will be provided as it becomes available.

2. monitoring Aug 25, 2026, 04:36 AM UTC

   We have observed recovery for a portion of the infrastructure affected by this issue within the Southeast Asia region. While many impacted services and resources have recovered, a subset of customers may continue to experience connectivity issues or service degradation for dependent Azure services. Engineers are actively working to restore the remaining impacted infrastructure and validate full service recovery.More information will be provided as it becomes available.

3. resolved Aug 25, 2026, 06:09 AM UTC

   We have mitigated a power-related infrastructure issue that affected a subset of Azure services in Southeast Asia. Most services have recovered and are operating normally. A remaining issue affecting a single storage stamp is being tracked separately, and impacted customers are being communicated with through a dedicated tracking process.

Read the full incident report →

Started Aug 14, 2026, 05:28 AM UTC· resolved Aug 14, 2026, 06:22 AM UTC

1. monitoring Aug 14, 2026, 05:28 AM UTC

   We are aware of an issue affecting access to the Azure portal in the Australia regions. Our engineers are actively investigating the cause and impact. Further updates will be provided as more information becomes available.

Read the full incident report →

Started Jul 27, 2026, 05:40 PM UTC· resolved Jul 28, 2026, 01:00 AM UTC

1. monitoring Jul 28, 2026, 05:15 PM UTC

   User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: We're reviewing scenario telemetry logs to determine why users may be unable to send messages after a recipient of a new chat request accepts in Microsoft Teams Free. Next update by: Tuesday, July 28, 2026, at 6:30 PM UTC

2. monitoring Jul 28, 2026, 06:26 PM UTC

   User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: We've identified that the process which should occur when a user accepts a new chat isn't trigger as expected. We're continuing to review the scenario telemetry logs to identify why this process isn't completing to determine the root cause and a strategy that remediates impact. Next update by: Tuesday, July 28, 2026, at 8:30 PM UTC

3. monitoring Jul 28, 2026, 08:29 PM UTC

   User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: Our review of the scenario telemetry logs is taking longer than anticipated, but we're continuing to make progress in understanding the root cause and developing a strategy that remediates impact. Next update by: Wednesday, July 29, 2026, at 1:00 AM UTC

4. monitoring Jul 29, 2026, 12:01 AM UTC

   User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: Current status: We’ve made changes to improve background processing and confirmed through internal monitoring that the impacted scenario is recovering. We’re continuing to monitor the recovery progress to confirm the issue is fully resolved. Next update by: Wednesday, July 29, 2026, at 10:00 AM UTC

5. resolved Jul 29, 2026, 05:14 AM UTC

   User impact: Users may have been unable to send new messages in Microsoft Teams Free. Final status: We’ve confirmed after monitoring that this issue is fully resolved. Start time: Monday, July 27, 2026, at 5:40 PM UTC End time: Tuesday, July 28, 2026, at 1:00 AM UTC This is the final update for the event.

Read the full incident report →

Started Jul 23, 2026, 04:29 PM UTC· resolved Jul 23, 2026, 08:24 PM UTC

1. monitoring Jul 23, 2026, 04:29 PM UTC

   We are investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may experience intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact. We are exploring mitigation options on affected network devices. Early indications suggest the issue is related to network traffic flow through the impacted infrastructure; however our analysis remains ongoing. We are closely monitoring traffic while continuing our investigation. We will provide additional information as it becomes available.

Read the full incident report →

Started Jul 23, 2026, 02:44 PM UTC· resolved Jul 23, 2026, 04:34 PM UTC

1. monitoring Jul 23, 2026, 03:50 PM UTC

   We are investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services.We will provide more information as it becomes available.

2. postmortem Jul 23, 2026, 07:41 PM UTC

   Watch our 'Azure Incident Retrospective' video about this incident: https://aka.ms/air/ZJV6-SGG What happened? Between 14:44 and 19:41 UTC on 23 July 2026, a subset of customers experienced connectivity failures, increased latency, and/or difficulty accessing Azure services hosted within the West US region. Impact was limited to network traffic entering or exiting the region, traffic that remained entirely within the region was not affected. Impacted services included: App Service, Application Insights, Azure AD B2C, Azure AI Bot Service, Azure AI Search, Azure API Management, Azure Application Gateway, Azure Bastion, Azure Cosmos DB, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure ExpressRoute, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitor, Azure Speech in Foundry Tools, Azure Virtual Desktop, Azure Virtual WAN, Azure VMware Solution, Azure VPN Gateway, as well as Microsoft Sentinel and Power BI Embedded. Downstream impact to Microsoft 365 services has been communicated via MO1437424. What went wrong and why? Azure datacenters connect through redundant network paths, ensuring that traffic can continue flowing even when one path is unavailable for maintenance or repair. When unplanned maintenance – including ‘break-fix’ hardware repair – is needed on an optical device along one of these paths, the repair process starts by creating system-readable instructions, verifying that the redundant path remains healthy, and performing safety checks to confirm that the work will not affect customer traffic. Because break-fix activities on a single device are generally expected to be impactless, these requests are processed automatically without human engagement or triage. On 23 July 2026, a break-fix repair was initiated on an optical device to address a network reliability risk. A defect in our blast radius analysis system incorrectly expanded the scope of the repair event to include all optical devices egressing a specific datacenter. The safety validation step, which is designed to confirm that at least one of the two redundant datacenter paths remains available, ran but incorrectly concluded the operation was safe. The checks validated each device individually rather than evaluating the aggregate effect of isolating all devices at once, a scenario that was not accounted for because the system was never designed to process a full datacenter's worth of devices in a single request. As a result, routes were withdrawn from multiple devices simultaneously, disrupting connectivity between the datacenter and the WAN – therefore impacting traffic entering or leaving the West US region. Once the route withdrawals took effect at 14:44 UTC, physical links and routing adjacencies continued to appear healthy, which initially masked the correlation between the break-fix activity and the connectivity disruption. The impact presented as a WAN routing anomaly, as third-party networks could not reach Azure in the region, rather than as a datacenter connectivity failure. Although all physical work in the region was stopped, our engineers could not correlate to this recent change because the preparation activities in advance of the break-fix did not succeed, so the physical layer and traffic appeared healthy. Meanwhile, strong signals indicating WAN impact drew much of the investigative focus. Two parallel investigation streams developed: one focused on the WAN routing anomaly, and another examining network device health from within the datacenter. It took additional time to work past these misleading signals and eventually identify the break-fix activity as the source. It was not until 17:19 UTC that our engineers were able to correlate the routing anomaly with the break-fix activity, at which point we had identified the trigger event and began planning a rollback. Our automated recovery and rollback system detected the device failures, and attempted multiple retries to restore the affected devices. However, because that system depended on the same datacenter connectivity that had been disrupted, its automated rollback attempts were unsuccessful. After our engineers correlated the routing anomaly with the break-fix activity, we identified that the incomplete preparation activities established the trigger conditions. We initiated a manual rollback at 17:45 UTC, then datacenter-to-WAN connectivity was restored when the rollback completed at 18:26 UTC, and all impacted services fully recovered by 19:41 UTC. How did we respond? • 14:44 UTC on 23 July 2026 – Device break-fix began. Earliest potential customer impact time. • 14:45 UTC on 23 July 2026 – Service alerts fired and multiple Azure service teams started investigating the traffic anomalies. • 14:54 UTC on 23 July 2026 – Automated recovery system started performing multiple retries to recover the devices that were affected by the over scoping that happened during the break-fix issue. • 15:26 UTC on 23 July 2026 – Routing anomaly alert incorrectly triaged to WAN issue and was sent to engineers to investigate further. • 16:58 UTC on 23 July 2026 – After multiple retries, automated recovery system raised an alert to engineers to investigate. Engineers tried to recover the devices manually. • 17:19 UTC on 23 July 2026 – Engineers correlated the routing anomaly with the initial break-fix trigger event and began attempting auto-rollback. • 17:45 UTC on 23 July 2026 – Engineers initiated manual rollback of the break-fix. • 18:26 UTC on 23 July 2026 – Rollback was successful on all affected devices, engineers continued monitoring recovery of affected services. • 19:41 UTC on 23 July 2026 – Customer impact confirmed as mitigated, after all services returned to expected operating levels. How are we making incidents like this less likely or less impactful? • We have fixed the defect in the blast radius analysis system that incorrectly expanded the scope of this ‘break-fix’ unplanned maintenance to include additional devices. Input validation now ensures that both diverse paths for a datacenter cannot undergo break-fix requests at the same time. (Completed) • We have scanned all existing break-fix requests in the system to identify similar conditions that could have allowed the same defect to produce similar impact elsewhere. (Completed) • We have enhanced safety checks to block any break-fix or maintenance activity that would affect all diverse paths for a datacenter, to de-risk this failure mode. (Completed) • We are improving change visibility, break-fix requests will be recorded in the standard Azure change ledger, to reduce the time required to correlate maintenance activity with network issues during future investigations. (Estimated completion: August 2026) • We are enhancing our datacenter traffic monitoring to detect abnormalities in inbound and outbound traffic more quickly, and surface these directly to engineers for evaluation – enabling faster customer notification, and mitigation efforts. (Estimated completion: September 2026) • We are improving change tooling guardrails so that multiple devices cannot be isolated simultaneously during maintenance. (Estimated completion: September 2026) • In the longer term, we are improving our automated recovery system to fail more quickly and escalate to engineers more promptly when retries are unsuccessful, rather than continuing to retry against disrupted connectivity. (Estimated completion: October 2026) • Finally, we are improving our automated rollback so it can recover more robustly, even when the underlying connectivity on which it depends is degraded. (Estimated completion: October 2026) How can customers make incidents like this less impactful? • For mission-critical workloads, customers should consider a multi-region deployment strategy to maintain availability during events that affect a single region: https://learn.microsoft.com/azure/architecture/patterns/geodes and https://learn.microsoft.com/azure/well-architected/design-guides/regions-availability-zones • More generally, consider evaluating the reliability of your applications using guidance from the Azure Well-Architected Framework and its interactive Well-Architected Review: https://aka.ms/AzPIR/WAF • The impact times represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability varied between customers and resources. For guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring • Finally, consider ensuring that the right people in your organization will be notified about any future service issues by configuring Azure Service Health alerts. These can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts How can we make our incident communications more useful? You can rate this PIR and provide any feedback using our quick 3-question survey: https://aka.ms/AzPIR/ZJV6-SGG

Read the full incident report →

Started Jul 23, 2026, 02:44 PM UTC· resolved Jul 23, 2026, 08:17 PM UTC

1. monitoring Jul 23, 2026, 03:50 PM UTC

   User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region. Current status: We are continuing our investigation and are reviewing recent changes for potential correlation while we analyze service telemetry and available diagnostic data. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Start time: Thursday, July 23, 2026, at 2:44 PM UTC Next update by: Thursday, July 23, 2026, at 5:00 PM UTC

2. monitoring Jul 23, 2026, 03:58 PM UTC

   Title: Issues accessing or using Microsoft 365 services in the North America region. User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region. More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to: - SharePoint Online - Microsoft Teams - Microsoft365 Admin Center Current status: We’ve identified specific network paths as a focus area and are using diagnostic data from affected infrastructure to determine the source of impact and plan mitigation actions. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Start time: Thursday, July 23, 2026, at 2:44 PM UTC Next update by: Thursday, July 23, 2026, at 5:00 PM UTC

3. monitoring Jul 23, 2026, 04:10 PM UTC

   Title: Issues accessing or using Microsoft 365 services in the North America region. User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region. More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to: - OneDrive for Business - SharePoint Online - Microsoft Teams - Microsoft365 Admin Center - Power Automate Current status: We’ve identified specific network paths as a focus area and are using diagnostic data from affected infrastructure to determine the source of impact and plan mitigation actions. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Start time: Thursday, July 23, 2026, at 2:44 PM UTC Next update by: Thursday, July 23, 2026, at 5:00 PM UTC

4. monitoring Jul 23, 2026, 04:49 PM UTC

   Title: Issues accessing or using Microsoft 365 services in the North America region. User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region. More info: We've confirmed that multiple Microsoft 365 services are degraded, including but not limited to: -Microsoft OneDrive - Access to OneDrive is intermittent. -SharePoint Online - Error message, “Something went wrong” -Microsoft Teams - Degraded chat functionality, including images not loading. -Microsoft 365 Admin Center - Admin Center is loading slowly or not at all. -Power Automate - Automate flows not loading. -Copilot Chat - Intermittent delays or failures in any Copilot Chat action and query. -Microsoft Loop - Unable to open or load Loop pages. Current status: We performed traffic rerouting for some of the affected infrastructure and our initial telemetry indicates that these actions have contributed to partial recovery for some users. We're scaling up our rerouting efforts while continuing to evaluate additional mitigation actions. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Start time: Thursday, July 23, 2026, at 2:44 PM UTC Next update by: Thursday, July 23, 2026, at 6:00 PM UTC

5. monitoring Jul 23, 2026, 06:09 PM UTC

   User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region. More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to: - Microsoft OneDrive: Intermittent connection issues. - SharePoint Online: Intermittent connection issues. Some users are receiving “Something went wrong” errors. - Microsoft Teams: Degraded chat functionality, including images not loading. Additionally, real-time voice apps reporting and historical reporting are not functioning as expected. - Copilot Chat: Intermittent delays using Copilot Chat and failures in query actions. - Microsoft 365 Admin Center: Latency and intermittent inability to access features - Power Automate: Automate flows not loading. - Microsoft Loop: Unable to open or load Loop pages. - Microsoft Purview: Degraded Purview DLP Agent response time. eDiscovery and Data Security Investigations failures when submitting new jobs and delays in processing existing jobs. - Fabric/Power BI: Users in the West US region may encounter issues accessing Publish to Web reports. Some users in Europe and Asia Pacific regions may also be intermittently delayed when accessing Fabric artifacts due to service dependencies in West US. Current status: Our service telemetry indicates that rerouting traffic has provided some relief across affected services. We’re continuing to perform targeted traffic-routing actions while we revert the networking change mentioned in our last update. We're monitoring our telemetry and working directly with some impacted customers to ensure our actions are effectively addressing impact. We expect the configuration change reversion to complete by our next scheduled update, and we’re evaluating other pathways to expedite recovery. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Users from other regions who are served by this infrastructure may also experience impact. Start time: Thursday, July 23, 2026, at 2:44 PM UTC Next update by: Thursday, July 23, 2026, at 7:00 PM UTC

6. monitoring Jul 23, 2026, 07:04 PM UTC

   More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to: - Microsoft OneDrive: Intermittent connection issues. - SharePoint Online: Intermittent connection issues. Some users are receiving “Something went wrong” errors. - Microsoft Teams: Degraded chat functionality, including images not loading. Additionally, real-time voice apps reporting and historical reporting are not functioning as expected. - Copilot Chat: Intermittent delays using Copilot Chat and failures in query actions. - Microsoft 365 Admin Center: Latency and intermittent inability to access features - Power Automate: Automate flows not loading. - Microsoft Loop: Unable to open or load Loop pages. - Microsoft Purview: Degraded Purview DLP Agent response time. eDiscovery and Data Security Investigations failures when submitting new jobs and delays in processing existing jobs. Additionally, admins may be unable to view their policies or navigate in the Purview portal. Retries may succeed. - Fabric/Power BI: Users in the West US region may encounter issues accessing Publish to Web reports. Some users in Europe and Asia Pacific regions may also be intermittently delayed when accessing Fabric artifacts due to service dependencies in West US. -Power Apps: Users may experience some issues accessing the Power Apps Portal and may also experience Canvas Apps not loading and data sources failing to connect. -Copilot Studio: Users may be unable to load the Copilot Studio Portal and data sources may also fail to connect. -Windows 365: Users may be unable to select a non-English (United States) language for their Cloud PC post provisioning. They can try reprovisioning and language selection again and it may succeed on retry. Current status: We’ve completed reverting the networking update, and our telemetry indicates impact is resolved for the vast majority of users. We're reviewing all known impact scenarios and monitoring for a period of time to confirm resolution for all affected environments. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Users from other regions who are served by this infrastructure may also experience impact. Start time: Thursday, July 23, 2026, at 2:44 PM UTC Next update by: Thursday, July 23, 2026, at 8:00 PM UTC

Read the full incident report →

Started Jul 08, 2026, 07:47 PM UTC· resolved Jul 08, 2026, 09:52 PM UTC

1. monitoring Jul 08, 2026, 07:47 PM UTC

   GitHub Enterprise Cloud with Data Residency is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: : https://us.githubstatus.com/posts/details/PBJ0QTY

Read the full incident report →

Started Jul 08, 2026, 06:20 PM UTC· resolved Jul 08, 2026, 06:20 PM UTC

1. resolved Jul 08, 2026, 06:20 PM UTC

   User impact: Users are unable to build or edit agents within Microsoft Copilot. Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication will expire in 24 hours. This is the final update for the event.

Read the full incident report →

Started Jul 08, 2026, 06:09 PM UTC· resolved Jul 09, 2026, 06:32 PM UTC

1. monitoring Jul 08, 2026, 06:09 PM UTC

   User impact: Users are experiencing issues in the service. Current status: We're investigating a potential issue with the Microsoft Copilot for Microsoft 365 and are checking for impact to your organization. We'll provide an update within 30 minutes.

Read the full incident report →

Started Jun 26, 2026, 09:21 PM UTC· resolved Jun 28, 2026, 12:08 AM UTC

1. monitoring Jun 26, 2026, 09:21 PM UTC

   User impact: Users may be unable to access or sign in to Microsoft Teams Free on iOS devices. Current status: We're investigating a potential Microsoft Teams Free issue in which users may be unable to access or sign in to the service on iOS devices and will provide an update in 30 minutes.

Read the full incident report →

Started Jun 25, 2026, 07:00 PM UTC· resolved Jun 27, 2026, 01:16 AM UTC

1. monitoring Jun 26, 2026, 09:49 PM UTC

   User impact: Users may be unable to access or sign in to Microsoft Teams Free on iOS or Android mobile devices. Current status: We've determined that this issue is due to a recent change that included a reference to a deprecated token for mobile devices. We're reverting this offending change to mitigate impact. Start time: Thursday, June 25, 2026, at 7:00 PM UTC Next update by: Saturday, June 27, 2026, at 1:30 AM UTC

2. resolved Jun 27, 2026, 01:16 AM UTC

   User impact: Users may have been unable to access or sign in to Microsoft Teams Free on iOS or Android mobile devices. Final status: We’ve successfully reverted the offending change and confirmed with service telemetry that this issue was resolved by our actions. Start time: Thursday, June 25, 2026, at 7:00 PM UTC End time: Saturday, June 27, 2026, at 1:16 AM UTC This is the final update for the event.

Read the full incident report →