# Microsoft 365 outage November 2026 - What happened on 12–13 November > What happened during the Microsoft 365 disruption on 12–13 November, what Microsoft confirmed and how UK businesses can respond and prepare. Language: British English (en-GB). Canonical page: https://kbyte.co.uk/microsoft-365-outage-november-2026/ Last updated: 2026-11-14 By [KByte IT Services](https://kbyte.co.uk/about-us/) Published: 2026-11-14 The **Microsoft 365 outage November 2026** disrupted business email and connected workplace tools on 12–13 November. Outlook users struggled to reach mailboxes, while some Teams and other Microsoft 365 features were affected. Microsoft later linked the incident to a networking issue. Recovery was progressing, but a final resolution time had not been confirmed when we checked. **Status checked on 14 November 2026 at 00:23 GMT.** This is a dated incident report, not a live availability monitor. Use [Microsoft’s service health page](https://status.cloud.microsoft/) for subsequent updates and your organisation’s admin centre for its specific impact. ## Microsoft 365 outage November 2026 timeline The disruption began on Thursday 12 November and continued into Friday 13 November. Different reports refer to different stages: the initial Exchange Online investigation, the broader Microsoft 365 incident and later recovery updates. They should not be treated as one exact start time for every customer. [BleepingComputer’s incident report](https://www.bleepingcomputer.com/news/microsoft/massive-microsoft-365-outage-disrupts-outlook-teams-copilot-worldwide/) identifies the broader incident start as 13:26 Eastern Time on 12 November, equivalent to **18:26 GMT**. Exchange mailbox problems were already being investigated. The reported references were **EX1550543** initially and **MO1550821** for the wider incident. - **12 November, before 18:26 GMT** — Microsoft investigated Exchange mailbox access problems in the Americas. - **12 November, 18:26 GMT** — Reported start of the broader Microsoft 365 incident. Its scope later included users in any region. - **12 November evening into 13 November** — Engineers restored capacity in stages; early recovery did not immediately resolve every connection or delivery problem. - **13 November, 22:00 GMT update** — Microsoft reported sustained recovery while continuing monitoring and checking the email backlog. - **14 November, 00:23 GMT check** — The public business-service status still showed degradation. No confirmed final end time was available. A separate, earlier Teams incident on 12 November had already been resolved. Its recovery announcement should not be mistaken for closure of the broader outage. ## Which services were affected? The [Microsoft business-service update](https://status.cloud.microsoft/api/posts/mac) distinguishes affected features from services that remained usable: - **Outlook and Exchange Online** — Mailbox access and email delivery problems across several connection methods. - **Microsoft Teams** — Calendar and other Exchange-dependent features; most core calls, meetings and chats were not affected in the updated assessment. - **SharePoint Online** — Some external sharing and dependent features, rather than a blanket loss of direct file access. - **Microsoft 365 Copilot** — Chat and access to connected work information could fail. - **Microsoft 365 administration and apps** — Some administrative pages and recently used file views were affected. ### Was Microsoft Teams down for everyone? “Microsoft Teams down” was a reasonable search when a calendar or invitation failed, but it did not describe every Teams function. An application can open normally while a connected service fails. Record the exact task that does not work, rather than reporting only the application name. ### What about OneDrive? OneDrive appeared in user outage reports covered by BleepingComputer. That is not evidence that every OneDrive account or file operation was unavailable. Avoid assuming that a delayed email invitation means the underlying document has disappeared. Check the particular file, permission and sharing operation with your administrator. ## What caused the Microsoft 365 global outage? Microsoft’s 13 November statement said a problem introduced during an earlier network capacity upgrade emerged after a subsequent network change. The [official Microsoft statement](https://x.com/Microsoft/status/2121282013600907325) was also reproduced in [Windows Central’s coverage](https://www.windowscentral.com/microsoft/we-are-deeply-sorry-microsoft-apologizes-for-major-outage-that-knocked-outlook-teams-and-microsoft-365-offline-for-24-hours-insists-it-wasnt-ai-that-caused-it). In everyday terms, the systems connecting and directing requests between services were involved. Earlier updates described servers becoming unavailable and leaving the remaining infrastructure under pressure. That differs from saying customers simply generated too much traffic. This was an initial explanation, not a complete engineering post-incident report. It did not justify attributing the failure to a particular employee, software tool or customer configuration. A fuller review would be needed to establish why safeguards did not contain the disruption. ### Was Microsoft hacked? Microsoft described the outage as a technical issue unrelated to cyber activity or AI agents. There was no basis in that statement to label this incident a confirmed cyberattack. Equally, an availability update is not a security assessment of your own organisation. Investigate suspicious sign-ins or unexpected payment requests separately. ## How did the outage affect UK businesses? [Reuters’ 13 November report](https://www.streetinsider.com/Reuters/Microsoft%2Boutage%2Bhits%2BOutlook%2C%2BTeams%2Band%2BCopilot%2Bworldwide/27334788.html) described disruption across businesses and governments internationally. It reported email problems for Euronext’s listing teams and backup arrangements for earnings calls at British insurer Aviva. Reports covered the Americas, Europe and Asia-Pacific; there was no reliable basis for treating every organisation in those regions as equally affected. For a smaller UK company, the practical consequences could include delayed quotations, missed customer replies, disrupted meeting arrangements and uncertainty about whether invoices had arrived. These are operational risks, not measured losses for KByte customers. We have not estimated a UK-wide financial cost or a definitive number of affected businesses. Shared inboxes are especially important when several staff handle customer work. Our [shared mailbox and distribution list guide](https://kbyte.co.uk/shared-mailbox-vs-distribution-list/) explains the different workflows. Neither arrangement, by itself, provides an independent route around an Exchange service outage. ## How did Microsoft restore services? Reported recovery steps included pausing deployments, restarting affected servers, returning capacity gradually and diverting traffic. Microsoft also investigated configuration reversals. The process was uneven: a successful connection did not necessarily mean email queues had cleared. BleepingComputer reported an extended 48-hour email timeout window intended to help preserve delayed messages. That extension was a mitigation, not a promise that every message would arrive. Businesses still needed to check important correspondence and delivery failures when access returned. ## Is Microsoft 365 working again? At our check, Microsoft’s update described recovery and ongoing monitoring, not final closure. Its public business-service entry remained degraded. Check your tenant and test important tasks before declaring your own business recovered. Ask two separate questions: can staff access the service, and has outstanding work caught up? A recovered inbox does not prove that all incoming messages, calendar changes or connected workflows have completed. ## Outlook email not working - what should you do? ### Check the scope before changing anything Ask whether colleagues have the same symptoms and whether other websites work. Note the error message, time and connection method. If several users are affected, an administrator should check the incident record before anyone reinstalls applications or changes shared settings. Microsoft’s [service health guidance](https://learn.microsoft.com/en-us/microsoft-365/enterprise/view-service-health?view=o365-worldwide) explains how authorised administrators can view incidents and advisories affecting their tenant. Use the public status page if the admin centre is inaccessible. A social-media complaint can be an early clue, but does not replace that check. ### Keep essential work moving safely - **Choose one incident coordinator.** Give staff a short update, an approved alternative contact method and the time of the next update. - **Use an independent channel for urgent matters.** Telephone key contacts when appropriate. Do not move confidential files into personal accounts or unapproved messaging apps. - **Avoid repeated resends.** Record urgent messages and confirm receipt with the recipient when service returns, reducing duplicate orders or conflicting instructions. - **Protect unfinished work.** Keep permitted local copies and notes of pending tasks. Do not delete profiles, clear application data or reset credentials merely because a provider incident exists. - **Keep security controls enabled.** Treat unexpected “outage repair” links cautiously. Follow your established verification process for requests involving passwords or payments. Our [phishing email checklist](https://kbyte.co.uk/how-to-spot-a-phishing-email/) covers warning signs worth checking. If only one person remains affected after wider recovery, report that individual fault with the evidence collected rather than assuming the global incident explains it indefinitely. ## How to prepare for the next outage Build a continuity plan around essential business activities. List who must be contacted, which work can wait and which alternative channels are already approved. Keep the contact list accessible when your normal email or cloud sign-in is unavailable, with appropriate protection for personal information. Then rehearse a realistic scenario. Can your team reach the support provider without Outlook? Can managers tell customers about a delay without relying on Teams? Agree who can approve a workaround and how staff return to the normal process afterwards. A short exercise often reveals missing access or unclear responsibilities. Review monitoring and escalation arrangements with your IT provider, including how alerts reach someone during a Microsoft outage. Record the incident reference, observed impact, decisions and recovery checks. Afterwards, review failed workflows and delayed transactions rather than treating restored connectivity as the end of the work. Backups address a different problem from continuous availability. They can support recovery of information, but do not automatically restore an unavailable hosted mailbox service. Use our [backup restore-testing checklist](https://kbyte.co.uk/business-backup-recovery-checks/) to establish what can actually be recovered, by whom and within what practical constraints. ## Frequently asked questions ### When did the Microsoft Outlook outage end? No final end time had been confirmed at our stated check. Recovery and backlog processing were continuing. Consult Microsoft’s current incident record rather than treating this article as a live all-clear. ### Should I change my Microsoft 365 password? A service outage alone is not a reason to change it. Follow your organisation’s security process if there is evidence of account compromise, and do not approve unexpected authentication prompts. ### Does an outage mean my emails have been deleted? Not necessarily. Inaccessibility and delivery delays do not establish deletion. Check important messages, failed-delivery notices and any missing correspondence with your administrator after recovery. ### Can another internet connection fix it? It may help distinguish a local connection fault from a provider incident. It cannot guarantee access when the affected service itself is unavailable. ## Make your next response easier KByte can help review your support and continuity arrangements through our [managed IT services](https://kbyte.co.uk/it-services/) and [business IT helpdesk](https://kbyte.co.uk/it-support-helpdesk-services/). Remote support is available across the UK, with onsite support in Peterborough. Start with the activities your business needs to keep running. ## Support with this topic - [IT helpdesk support for business users](https://kbyte.co.uk/it-support-helpdesk-services/)