Just a day after the massive worldwide Cloudflare outage, Microsoft has confirmed that some of the Microsoft 365 services are currently down again. The company confirmed this via its official Microsoft 365 Status X handle as it notes that the Office.com portal and some of its related services are inaccessible at the moment. The tech giant has informed that you can get status updates regarding the progress of the bug on the Microsoft 365 Admin Center portal with issue ID "CP1188020" so details regarding the outage will be shared there.
We"re investigating an issue where users may be unable to perform any action on files within Microsoft Copilot (Microsoft 365). Additional information will be provided in the admin center under CP1188020.
— Microsoft 365 Status (@MSFT365Status) November 19, 2025
The official Microsoft 365 Service Health Status website currently lists that there is no issue with "everything up and running". However, the page will likely be updated soon to reflect the situation.
We will update the post once more details are available.
Update, November 20 2025, 13.30 GMT: After nearly 14 hours from the initial alert, Microsoft managed to fix the issue. In the meantime it continued providing status updates regarding the issue.
We’ve found an issue with an internal service that checks file permissions, causing user requests to fail. We’re investigating recent changes to this service. Additional information will be provided in the admin centre under CP1188020.
— Microsoft 365 Status (@MSFT365Status) November 19, 2025
We"ve identified that an internal service is not routing requests correctly, resulting in impact. We"re currently reviewing system telemetry to identify why this is occurring. Additional information will be provided in the admin center under CP1188020.
— Microsoft 365 Status (@MSFT365Status) November 19, 2025
We"ve determined a network access policy implementation issue is disallowing the service from accessing the dependent VMs. We"re restoring this policy to a previously known healthy state. More detail can be found under CP1188020 in the admin center.
— Microsoft 365 Status (@MSFT365Status) November 19, 2025
We"ve successfully resolved the issue following our actions to restart the dependent VMs. Full details regarding this incident can be found under CP1188020 or MO1188100 in the Microsoft 365 Admin center.
— Microsoft 365 Status (@MSFT365Status) November 20, 2025