Microsoft has restored Outlook, Microsoft Teams, Copilot and other Microsoft 365 services after a major global outage disrupted businesses and government organisations for more than 24 hours.
The company confirmed the recovery on Saturday, November 14, 2026. The disruption affected users in more than 70 countries and caused problems with email, workplace communication, file access and other cloud-based services.
Microsoft said it had resolved the underlying technical issue and restored services to the remaining affected customers and regions. The company also apologised for the disruption.
The incident was linked to a problem during an earlier network-capacity upgrade. Microsoft said it had no indication that the outage was caused by a cyberattack or artificial intelligence.
The recovery ends one of the most disruptive Microsoft 365 incidents in recent years. However, it has raised fresh questions about the reliability of cloud infrastructure and the risks of depending on a single technology provider.
Microsoft Confirms Full Restoration of Services
Microsoft announced on Saturday that its engineers had completed the work needed to address the underlying issue.
In an update shared on X, the company said it had restored service to the remaining affected customers and regions.
The restoration covered major Microsoft products, including:
- Outlook: Email access and delivery services.
- Microsoft Teams: Workplace messaging, meetings and collaboration features.
- Microsoft Copilot: Microsoft’s AI assistant and connected workplace experiences.
- Exchange Online: Microsoft’s cloud-based email infrastructure.
- SharePoint Online: Document management and collaboration.
- OneDrive: Cloud storage and file synchronisation.
- Microsoft 365: Connected productivity and enterprise services.
The company had been restoring services gradually as engineers addressed infrastructure and server problems.
Although some services began recovering earlier, customers continued to experience intermittent issues and delayed email delivery while Microsoft worked through the remaining problems. <Cite refs={[“turn382028search0″,”turn340462view0″,”turn382028search14”]}/>
What Caused the Microsoft Global Outage?
Microsoft attributed the incident to a technical problem connected to an earlier network-capacity upgrade.
According to the company’s explanation, the issue surfaced following a recent network change.
During the incident, some servers became unexpectedly unavailable. This affected Microsoft’s ability to process requests and maintain normal service availability.
The problem also affected Exchange Online, which supports Outlook and several connected Microsoft 365 features.
As a result, services that depended on Exchange Online experienced problems even when some of their other functions remained operational.
Microsoft’s recovery work involved addressing server availability, adjusting infrastructure and restoring affected services.
The company said the incident was not related to a cyberattack or AI agents. However, a more detailed technical explanation is expected through its post-incident investigation. <Cite refs={[“turn340462view0″,”turn382028search4″,”turn382028search15”]}/>
How Long Did the Microsoft Outage Last?
The disruption began on Thursday, November 12, 2026, with problems appearing around midday in the United States.
Reports increased across multiple countries as users struggled to access Microsoft’s cloud services.
The outage continued into Friday and affected organisations across different time zones. Microsoft worked through several recovery attempts before confirming full restoration on Saturday, November 14.
The incident therefore disrupted services for more than 24 hours.
Downdetector received outage reports from users in more than 70 countries and territories. The actual number of affected users was not confirmed. <Cite refs={[“turn340462view0″,”turn340462view1”]}/>
Which Countries and Organisations Were Affected?
The outage reached far beyond individual Microsoft 365 customers. Government agencies, businesses, financial institutions and public services reported disruption.
Australia
Australian government organisations, including the Australian Security Intelligence Organisation (ASIO) and Australian Federal Police (AFP), confirmed that they were affected.
The incident raised concerns about the dependence of essential public services on external cloud infrastructure.
Singapore
Government departments in Singapore reported problems with Microsoft services.
The disruption affected workplace communication and other digital operations. Services were restored as Microsoft’s recovery progressed.
Japan
Japanese government organisations also reported operational disruption.
The incident demonstrated how a single infrastructure problem could affect public-sector services across different countries.
United Kingdom
The outage created problems for police services, courts and healthcare-related operations.
In Manchester, a court trial was halted after technology-related delays. British police also reported difficulties receiving some online crime reports.
The National Pharmacy Association warned of possible prescription delays because some doctors could not reliably email prescriptions to pharmacies.
United States and Other Markets
Businesses and public organisations in the United States and other markets also reported disruption.
Some financial institutions in Hong Kong experienced problems. Companies also faced difficulties communicating with customers and accessing workplace applications.
The outage showed how deeply Microsoft services are embedded in everyday business operations. <Cite refs={[“turn340462view0″,”turn340462view1”]}/>
Why Outlook and Teams Were Particularly Affected
Outlook and Teams are among Microsoft’s most widely used workplace applications.
Outlook supports business email, calendars and scheduling. Teams provides messaging, meetings and collaboration.
Both services depend on interconnected cloud infrastructure.
Exchange Online plays an important role in email and calendar functions. It also supports certain features in other Microsoft applications.
During the outage, users experienced problems such as:
- Inability to open Outlook inboxes.
- Delayed or failed email delivery.
- Problems sending and receiving messages.
- Calendar and meeting scheduling issues.
- Difficulties accessing certain Teams features.
- Problems with Copilot accessing work-related information.
Not every feature stopped working for every customer. For example, some Teams messaging and meeting functions remained available where they did not depend on the affected Exchange Online components.
This distinction matters because a cloud outage can affect connected features without completely shutting down every application. <Cite refs={[“turn382028search2″,”turn382028search14”]}/>
Microsoft Apologises to Customers
Microsoft acknowledged the disruption and apologised to customers and partners who rely on its services.
The company said it understood the importance of its products to daily business operations and took its responsibility seriously.
The recovery required engineers to address the underlying infrastructure issue and gradually restore affected services.
However, restoring access is only the first step. Microsoft will also need to explain what went wrong and how it plans to prevent similar incidents.
A detailed post-incident report should provide more information about the technical failure, the recovery process and the changes planned to improve reliability.
How Does This Outage Compare With the 2024 CrowdStrike Incident?
The Microsoft outage has drawn comparisons with the global CrowdStrike incident of July 2024.
In that incident, a faulty security software update caused millions of Windows computers to crash. Airlines, hospitals, businesses and government organisations experienced widespread disruption.
However, the two incidents had different technical causes.
The 2024 CrowdStrike incident involved a faulty software update affecting Windows systems. The November 2026 Microsoft incident involved a network-capacity upgrade issue and problems with Microsoft’s cloud infrastructure.
Both events highlight a common risk: modern organisations depend on technology platforms that serve millions of users simultaneously.
When a critical component fails, the consequences can spread quickly across industries and countries.
What This Means for Cloud Computing
The incident is another reminder that cloud computing does not guarantee uninterrupted availability.
Businesses use Microsoft 365 for email, document storage, communication, security and collaboration. These services help organisations operate without managing all their own infrastructure.
However, centralising essential operations with one provider can create a significant dependency.
If that provider experiences a major outage, multiple business functions may become unavailable at the same time.
Organisations should consider several measures:
- Maintain alternative communication channels: Keep emergency communication methods available outside the primary cloud platform.
- Create independent backups: Protect important files and business data through separate backup arrangements.
- Test disaster recovery plans: Make sure employees know how to continue essential work during an outage.
- Review cloud dependencies: Identify which business operations rely on Exchange Online and other connected services.
- Evaluate provider diversity: Consider alternative platforms for critical operations where practical.
The goal is not necessarily to abandon Microsoft 365. Instead, organisations should avoid assuming that any single technology provider will always remain available.
What Happens Next?
With services restored, Microsoft’s next responsibility is to investigate the incident and improve infrastructure resilience.
Customers will want more detail about the network-capacity upgrade, the server failures and the recovery process.
Important questions remain:
- What exact network change triggered the problem?
- Why did the issue affect so many connected services?
- What caused some servers to become unexpectedly unavailable?
- How will Microsoft prevent similar infrastructure failures?
- What additional safeguards will protect enterprise customers?
- Will organisations reconsider their dependence on a single cloud provider?
Microsoft’s post-incident findings will be important for customers evaluating the reliability of its cloud services.
Conclusion
Microsoft has restored Outlook, Teams, Copilot and other affected services after a global outage lasting more than 24 hours.
The incident disrupted communication and business operations across more than 70 countries. It also affected government agencies, courts, healthcare services, airlines and financial organisations.
Microsoft linked the problem to a technical issue during an earlier network-capacity upgrade and said there was no indication of a cyberattack.
Although services are now restored, the incident has highlighted a bigger challenge for the technology industry.
Cloud platforms have become essential to modern businesses, but even the largest providers can experience major failures.
For organisations, the lesson is clear: reliable cloud services are important, but independent backups and disaster recovery plans are equally necessary.
Frequently Asked Questions
1. Has Microsoft fixed the global outage?
Yes. Microsoft confirmed on November 14, 2026, that it had restored services to the remaining affected customers and regions.
2. Which Microsoft services were affected?
The disruption affected Outlook, Exchange Online, Teams, Copilot and other Microsoft 365 services, including certain SharePoint and OneDrive features.
3. How long did the Microsoft outage last?
The global disruption began on November 12 and continued until November 14, lasting more than 24 hours.
4. What caused the Microsoft outage?
Microsoft linked the incident to a technical problem during an earlier network-capacity upgrade that surfaced following a network change.
5. Was the outage caused by a cyberattack?
Microsoft said it had no indication that the incident was related to malicious activity or a cyberattack.
6. How many countries were affected?
Downdetector received outage reports from users in more than 70 countries and territories.
7. Is Microsoft Copilot working again?
Microsoft confirmed that services had been restored across Copilot and its other affected products.
8. Could another Microsoft outage happen?
No cloud provider can guarantee zero downtime. Microsoft can introduce additional safeguards, but organisations should also maintain independent backups and recovery plans.
By
