O365 - General
| 2026-06-01 | Status | Description |
|---|---|---|
| 03:06 PM |
|
Resolved: - Copilot: Users may have been unable to access the Copilot desktop or web app. |
| 02:07 PM |
|
Copilot: - Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app. |
| 01:08 PM |
|
Unable to open files in Office for the web or Microsoft Teams User impact: Users may have been unable to open files in Office for the web or Microsoft Teams. More info: Impacted Office Apps included, but were not limited to: - Excel - PowerPoint When users opened documents, impacted users were shown the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon." Final status: We've confirmed through customer reports and service telemetry that the impact has been resolved, and the service has remained stable for an extended period of time. As the issue recovered without any specific engineering actions being implemented, engineer teams continue to investigate the underlying root cause so actions can be taken to prevent the issue from reoccurring. |
| 11:40 AM |
|
Unable to open files in Office for the web. ID: MO1329446Issue type: Incident Status Service Degradation Impacted services O365 suite, SharePoint Online, OneDrive,Teams DetailsTitle: Unable to open files in Office for the web. User impact: Users may be unable to open files in Office for the web. More info: Impacted Office Apps include, but are not limited to: - Excel When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon." Current status: We're investigating service telemetry to isolate the source of the issue. Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Teams. Next update by: Monday, June 1, 2026, at 2:30 PM UTC |
| 09:53 AM |
|
Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows. More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations. Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact. |
| 09:25 AM |
|
Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website User impact: Users may have been unable to setup MFA or access the mysignins.microsoft.com website. More info: Users may have encountered 504 Gateway Timeout errors when trying to access mysignins.microsoft.com Current status: We've identified a recent cache configuration change required a failover. During the failover, the service experienced high CPU and memory utilization as EU traffic peaked, which prevented the MySignIn service from processing the volume of requests. Mitigation actions have since been rolled back, and traffic has been restored to the original infrastructure. |
| 09:24 AM |
|
Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website. Current status: We've received reports indicating an issue with setting up MFA or accessing the mysignins.microsoft.com page. We're reviewing service health telemetry to help isolate the root cause and determine our next troubleshooting steps. |
| 09:12 AM |
|
Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents User impact: Users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents. More info: Impacted users may have seen empty message bubbles when interacting with custom engine agents, including admin agents. Final status: We’ve confirmed that impact is fully remediated following the reversion, with custom engine agents returning responses as expected. Users who continue to see impact may need to start a new Copilot session for the fix to take effect. |
| 08:52 AM |
|
Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows User impact: Users were intermittently unable to create, save, manage, or run Microsoft 365 workflows. More info: Affected users experienced intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encountered failures when creating, saving, updating, or running workflows and automations. Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem. |
| 08:49 AM |
|
Users may be unable to use Microsoft 365 Copilot User impact: Users may have been unable to use Microsoft 365 Copilot. More info: Users received errors when attempting to interact with Microsoft 365 Copilot. This issue affected Copilot experiences across all Microsoft 365 productivity apps and services. Final status: After a period of extended monitoring, we've validated that service has been restored. |
No Issue
Outage
