A widespread Microsoft service outage disrupted email, collaboration and artificial-intelligence tools used by businesses and public institutions, leaving organizations to activate backup communication plans while the company worked to stabilize its systems.
The incident affected services including Outlook, Teams and Copilot. Reports collected by outage monitor Downdetector came from more than 70 countries after problems began on Thursday. Microsoft said it was seeing early signs that conditions were stabilizing, but acknowledged that services had not yet returned to normal. The company also said the incident was not caused by a cybersecurity breach.
The disruption was especially visible in the United Kingdom, where schools, Parliament, police forces and parts of the health system reported difficulties. Some schools asked parents to contact them by telephone rather than email. Parliament put alternative communication arrangements in place, while several police forces similarly directed the public toward phone contact when Microsoft-based channels were unavailable.
Health services experienced uneven effects because local organizations use different technical systems. Access to NHS email was impaired, complicating communication among pharmacies, general practices and some patients. The National Pharmacy Association warned that prescription waits could be longer. Some hospitals limited referrals or reverted to paper-based contingency procedures, while the NHS said clinical and operational systems were functioning. Emergency dispatch and life-threatening 999 calls continued to operate, according to accounts gathered by the BBC.
The outage’s full reach was difficult to quantify. Microsoft 365 has hundreds of millions of users, but a report of difficulty on one product does not establish that every customer or service was unavailable. What was clear was that dependence on a shared suite allowed one technical incident to affect many unrelated workplaces at the same time.
Microsoft’s public updates described traffic and capacity problems and mitigation work, but users were still waiting for a plain-language technical explanation while recovery continued. The absence of evidence of malicious activity pointed instead toward an internal service failure, though a detailed post-incident account had not yet been published in the supplied reporting.
The interruption also tested business-continuity plans. Organizations with telephone trees, independent messaging tools or paper procedures could route around some failures, while those relying heavily on Microsoft-hosted email and calendars had fewer immediate options. Cybersecurity and resilience specialists cited by the BBC urged companies to maintain alternative channels and additional capacity for critical operations.
Until Microsoft confirms full recovery, the practical measure of progress will be whether affected customers regain stable access across regions and products. Early stabilization suggests mitigation was taking effect, but it is not the same as a completed restoration, and institutions were continuing to use workarounds.
