Tech
Microsoft 365 outage: what Luxembourg SMEs should learn
From the evening of 12.11.2026 a Microsoft 365 outage cut many users off from Outlook and Exchange Online for hours, including in Europe, and Microsoft blames failed server health checks, not an attack.
Key takeaways
- The outage started on 12.11.2026 at 18:54 CET with Exchange Online and soon affected users in all regions.
- Microsoft says servers failed automated health checks and that it has no evidence of malicious activity.
- On 13.11.2026 at 15:00 CET Microsoft reported improvements in Europe but had not declared the incident fully resolved.
- Under Luxembourg's NIS2 law, covered entities must plan for business continuity and supplier risks.
On this page
A Microsoft 365 outage that began on the evening of 12.11.2026 cut many users worldwide, including in Europe, off from Outlook and Exchange Online for hours, and as of 13.11.2026 at 15:00 CET Microsoft had not yet declared it fully resolved.
Microsoft says servers failed automated health checks and dropped out of service, overloading the rest of its infrastructure, and that it has no evidence of malicious activity.
Update, 13.11.2026, 19:05: In a post at 19:05 CET Microsoft named the cause: "The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." It added: "This was a technical issue not related to cyber or AI / agents." Microsoft said it would "continue to restore service to remaining customers and regions", and at 19:24 CET restoration was still ongoing, with no newer status post. Microsoft has announced a post-incident report but not yet published it: "We will provide a full post-incident report once our review is complete."
Update, 14.11.2026, 07:15: At 07:09 CET on 14.11.2026 Microsoft wrote: "We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions." Further updates are posted under MO1550821 in the Microsoft 365 admin center. In the same post of 19:05 CET on 13.11.2026 Microsoft had apologised: "We are deeply sorry for the disruption this incident has caused our customers and partners." At 21:05 CET it still wrote "We do not have an ETA for full recovery yet.", and at 22:55 CET it reported sustained recovery while "monitoring the backlog of email messages accrued during this event". The announced post-incident report had not been published by 07:15 CET. According to Reuters, Microsoft's consumer services had fully recovered at 17:10 CET on 13.11.2026. The BBC reported that services were broadly recovering nearly 24 hours after the problems began and that the outage hit more than 70 countries.
What happened during the Microsoft 365 outage?
The first post on the official Microsoft 365 Status account came at 18:54 CET on 12.11.2026: Microsoft was investigating problems reaching Exchange Online mailboxes in the Americas, tracked as EX1550543. Thirteen minutes later it warned that the issue could affect Microsoft 365 connectivity for users in any region. A separate Teams incident in North America earlier that afternoon had already been resolved.
Microsoft's explanation developed over the evening. At first it cited elevated load across multiple regions, then clarified that the load was not caused by more traffic but by a number of servers being unexpectedly unavailable. It then reported that servers were failing automated health checks, possibly because of a specific component that processes server health. An alternative health check method brought some servers back, but at 23:09 CET Microsoft wrote that its actions had not provided the anticipated relief and that a core process on affected servers was becoming overwhelmed.
On the morning of 13.11.2026 Microsoft extended the email timeout to 48 hours to help preserve delayed mail. At 14:32 CET it reported broader improvements in North America, sustained improvements across much of Europe and encouraging recovery signals in Asia Pacific, while warning that some users could still see intermittent access problems or delayed mail.
Which services and regions were affected?
Microsoft tracks the wider impact under MO1550821. According to the reporting of IT-Administrator, which lists Microsoft's notices, Exchange Online was at the centre, with Outlook on the web and other connection methods affected. Teams chats and meetings largely kept working, but functions that rely on Exchange Online, such as calendars and meeting scheduling, could fail. SharePoint Online, Copilot, Planner, To Do and Purview were also named. Microsoft's public status page listed a degradation for Microsoft 365 and no Azure issues.
The outage tracker Downdetector received reports from 74 countries and territories within about an hour, according to DW, with nearly 130.000 US reports about Outlook at the peak. Reuters reported that the outage hit government agencies from Australia to the United States and halted at least one bond repurchase in Europe. AP, The Guardian, CNBC and tagesschau.de also covered it.
Weekly, Thursday morning, Central European Time.
The Thinking briefing
One email a week: what changed in European business software, which prices moved, and which comparison we published. No sales mail.
Was it a cyberattack?
According to Microsoft, no. AP and Reuters quote the company as saying it was not aware of any malicious activity behind the incident. Microsoft has not yet published a root cause. In its status update it announced a post-incident report with the root cause after mitigation, as documented by the University of Bath, which reproduces Microsoft's message. Until then, the health check explanation is Microsoft's interim account, not a final analysis.
What should SMEs in Luxembourg take from it?
Many small firms run mail, calendars, files and chat through one Microsoft 365 tenant. When that tenant is unreachable, several tools fail at once. A short contingency plan helps more than a hasty change of provider:
- Second channel: a current phone list and an agreed messaging channel outside Microsoft 365 for staff and key customers.
- Status source: Microsoft pointed users to status.cloud.microsoft when the admin centre itself was not available.
- Offline basics: contacts, ongoing orders and the next days' appointments should also exist outside the mailbox.
- Clear roles: who informs customers, and who decides whether meetings move to phone or another tool.

If you are reassessing your tools, our comparisons of Slack and Microsoft Teams and of Microsoft 365 Copilot and Gemini for Google Workspace show how the suites differ. Note that a second provider only helps if it does not depend on the same mailbox.
What does NIS2 say about this?
Luxembourg transposed the NIS2 directive with the law of 05.05.2026, in force since 10.05.2026 according to the ILR. It mainly covers medium and large companies in the listed sectors, so many small firms are outside its scope. Entities that are covered must, under Article 12, take measures that include business continuity with backup management, recovery and crisis management, supply chain security covering their direct service providers, and secure emergency communication systems where needed.
The ILR stresses that the notion of an incident is broad and also includes technical failures, not only attacks, and that significant incidents require a preliminary notification within 24 hours. Whether a cloud outage is significant for a given company depends on its effect on that company's services. This describes the legal framework and is not legal advice.
Questions and answers
Was the Microsoft 365 outage a cyberattack?
Do I have to report a cloud outage under NIS2 in Luxembourg?
Sources
- [1] Microsoft 365 Status on X: investigating Exchange Online mailbox access issues (EX1550543) accessed 2026-11-13
- [2] Microsoft 365 Status on X: issue may affect users in any region accessed 2026-11-13
- [3] Microsoft 365 Status on X: load caused by servers unexpectedly unavailable accessed 2026-11-13
- [4] Microsoft 365 Status on X: servers failing automated health checks accessed 2026-11-13
- [5] Microsoft 365 Status on X: actions have not provided the anticipated relief accessed 2026-11-13
- [6] Microsoft 365 Status on X: email timeout extended to 48 hours accessed 2026-11-13
- [7] Microsoft 365 Status on X: recovery progress in North America, Europe and Asia Pacific accessed 2026-11-13
- [8] Microsoft service health status accessed 2026-11-13
- [9] Microsoft 365 - Global Outage (University of Bath status page) accessed 2026-11-13
- [10] Microsoft 365: Störung legt zahlreiche Dienste lahm (IT-Administrator) accessed 2026-11-13
- [11] Microsoft rules out 'malicious activity' in global outage (DW) accessed 2026-11-13
- [12] Hours-long Microsoft outage disrupts businesses, governments globally (Reuters via StreetInsider) accessed 2026-11-13
- [13] Microsoft reports progress as it works to recover email and other services in a global outage (AP) accessed 2026-11-13
- [14] Microsoft scrambles to fix global outage affecting Teams and Outlook (The Guardian) accessed 2026-11-13
- [15] Microsoft outage continues, Outlook and other 365 services down (CNBC) accessed 2026-11-13
- [16] Auch Outlook betroffen: Weltweite Störungen bei Microsoft-Diensten (tagesschau.de) accessed 2026-11-13
- [17] Loi du 5 mai 2026 concernant des mesures destinées à assurer un niveau élevé de cybersécurité (Mémorial A 225) accessed 2026-11-13
- [18] NIS 2 (ILR) accessed 2026-11-13
- [19] Cybersécurité : l'ILR présente la nouvelle loi NIS 2 (ILR) accessed 2026-11-13
- [20] Microsoft 365 Status on X, post of 13.11.2026 19:05 CET accessed 2026-11-13
- [21] Microsoft 365 Status on X, post of 13.11.2026 21:05 CET accessed 2026-11-14
- [22] Microsoft 365 Status on X, post of 13.11.2026 22:55 CET accessed 2026-11-14
- [23] Microsoft 365 Status on X, post of 14.11.2026 07:09 CET accessed 2026-11-14
- [24] Reuters via Khaleej Times, Microsoft says consumer products services recovered; still monitoring enterprise services accessed 2026-11-14
- [25] BBC News, Microsoft 'deeply sorry' for global outage as it reports broad recovery accessed 2026-11-14



