Microsoft 365 Outage and GDPR What it Means for Compliance

Microsoft 365 Outage and GDPR: What it Means for Compliance

Summary

The Microsoft 365 outage that began on 12 November 2026 cut access to email and other services for many organisations. Under the GDPR, a loss of access to personal data is a personal data breach, and it must be recorded. Whether to notify the regulator depends on the risk to individuals, and that assessment belongs to each customer as controller.

This guide covers what Microsoft has said about the outage, when an outage becomes a reportable breach, how responsibility splits between you and Microsoft, the risks created by staff workarounds, and the checks to run now.

Key Takeaways

• A temporary loss of access to personal data can be a personal data breach. Every breach must be recorded under Article 33(5), and the regulator is notified only where the breach is likely to result in a risk to individuals.

• Microsoft is the processor. It reports availability problems through the Service Health Dashboard and leaves the risk assessment to the customer.

• The workarounds staff used during the outage, such as personal email and messaging apps, may create a larger data protection problem than the outage itself.

What Microsoft Has Said About the Outage

The disruption started on 12 November 2026. Microsoft first reported that users in the Americas could not connect to Exchange Online mailboxes, then identified possible impact on Teams, SharePoint Online, Microsoft 365 Copilot, Defender XDR and other services, according to SecurityWeek. 

The Exchange Online incident was marked resolved on 13 November. Microsoft said it had no evidence of malicious activity, described the event as a technical issue unrelated to a cyberattack or to AI, and said it would publish a full post-incident report, as SecurityWeek reported.

Charles Lamanna, Microsoft’s Executive Vice President for Copilot, Agents and Platform, summarised the cause on X, as reported by ITPro. He described three factors:

• a latent defect in a fix prepared in July 2026 for Microsoft 365 networking gateway servers;

• a failover of Teams traffic onto the gateway that supports Exchange Online about 15 hours before the outage;

• nearly 14% of gateway server capacity being out of service because of an unrelated issue the day before.

According to Lamanna, the failure spread from server to server, and at its lowest point, more than 80% of servers were unresponsive. Microsoft has directed customers to the Microsoft 365 admin centre for full details on the root cause.

In the UK, BCS, The Chartered Institute for IT, reported that schools, the NHS and local authorities were among those affected.

A Cloud Outage Can Be a Personal Data Breach

Article 4(12) GDPR defines a personal data breach as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. The ICO’s guide to personal data breaches lists “loss of availability of personal data” as an example.

The ICO adds a qualifier. It describes a breach as including cases where data is made unavailable, and this unavailability has a significant negative effect on individuals.

The GDPR then sets three levels of response:

• Record it. Article 33(5) requires the controller to document every personal data breach, including the facts, its effects and the remedial action taken, whether or not it is notified.

• Notify the regulator if there is a risk. Under Article 33(1), the controller notifies the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to individuals.

• Tell individuals if the risk is high. Article 34 applies where the breach is likely to result in a high risk to their rights and freedoms.

When an Outage Becomes Reportable

For most organisations, a day without email is an operational problem with limited effect on the people whose data sits in the mailboxes. The ICO notes that some breaches lead to no more than inconvenience for those who need the data to do their job.

The assessment changes where the outage affected people directly. Situations to examine include:

• patients, clients or vulnerable people who could not receive care, services or time-sensitive decisions;

• safeguarding, fraud or legal deadlines that were missed;

• messages lost, corrupted or delivered to the wrong recipient once services recovered;

• personal data moved into personal or unapproved tools while services were down.

The last point turns an availability problem into a possible confidentiality breach, which is assessed separately.

If your breach log has no entry for 12 and 13 November 2026, add one. Record what happened, which processing was affected and why you did or did not notify. Our guide to personal data breaches explains the assessment in more detail.

Microsoft Is the Processor, and the Assessment Is Yours

When you use Microsoft 365 for personal data, your organisation is the controller, and Microsoft acts as your processor. Microsoft’s own GDPR breach notification page states that, as a processor, it does not determine the risk of a data breach. Controllers decide on severity, regulator notification and whether to inform individuals.

Two points from that page matter for this outage:

• Microsoft commits to notify customers of a personal data breach within 72 hours of the breach being declared, through the Message Centre in the Microsoft 365 admin centre.

• Microsoft says it also reports issues that affect data availability, but this usually happens through the Service Health Dashboard.

You may therefore receive no breach notice for an outage at all. The duty to assess it stays with you.

Article 32(1) GDPR also requires controllers and processors to take measures that include ensuring the ongoing availability and resilience of processing systems, and restoring access to personal data promptly after an incident. A continuity plan that assumes Microsoft 365 is always available is hard to defend under that wording.

Export the service health records for EX1550543 and MO1550821 from your admin centre now. They are your evidence of timing and of what Microsoft told you.

Staff Workarounds Are the Larger Risk

Deadlines did not stop when Outlook and Teams did. BCS warned during the outage that staff were likely to fall back on personal WhatsApp and home email. Adam Leon Smith FBCS said these alternatives are often less secure than corporate tools, both contractually and technically. BCS added that personal data moved onto personal devices can no longer be tracked, audited or deleted by the organisation.

Each workaround can engage several GDPR duties:

• Client or patient data sent to personal email or messaging apps: the security principle in Article 5(1)(f), security of processing under Article 32, and a possible confidentiality breach.

• A new, unapproved file-sharing or chat tool: no processor contract under Article 28 and no entry in your record of processing activities.

• A tool hosted outside the EU or UK: the international transfer rules in Chapter V.

• Data left on personal devices afterwards: storage limitation under Article 5(1)(e), and gaps in your answers to access and erasure requests.

• Health or HR data shared informally: the conditions for special category data in Article 9, and a higher risk in any breach assessment.

The UK has a precedent. In 2023, the ICO reprimanded NHS Lanarkshire after 26 staff used a WhatsApp group to enter patient data more than 500 times between April 2020 and April 2022. A non-staff member was added by mistake. The ICO found that the board had no appropriate policies, guidance or processes, and no assessment of the risks of sharing patient data that way.

Attackers Used the Outage for Phishing

Microsoft Threat Intelligence reported a phishing campaign that exploited the disruption, according to SecurityWeek. The emails posed as Microsoft 365 service health notices, referred to the real incident number EX1550543, and in some cases told recipients that emails held during the outage would be deleted within 24 hours unless they clicked a link.

Microsoft said the activity was consistent with credential phishing and advised organisations to verify service incidents directly in the Microsoft 365 admin centre. A mailbox taken over through a link like this would be a confidentiality breach, assessed on its own terms.

Other Reporting Regimes Run in Parallel

Organisations in regulated sectors may have incident reporting duties outside the GDPR, with their own thresholds and deadlines. These include NIS2 for in-scope essential and important entities, DORA for EU financial entities, and UK sector rules. Check each regime that applies to you, separately from the GDPR assessment.

Microsoft’s regulatory position is also relevant for financial services customers. Microsoft Ireland Operations Limited is on the European Supervisory Authorities’ November 2025 list of designated critical ICT third-party providers under DORA. The designation says nothing about fault in this outage. It does mean regulators expect financial entities to manage their dependency on Microsoft as a third-party risk.

What to Check

• Define the incident window for your tenant using service health history, and export the records for EX1550543 and MO1550821.

• Open a breach log entry under Article 33(5), with your risk assessment and the reason for your notification decision.

• Decide on notification now if the outage affected time-critical or special category processing, or if data went into unapproved channels. The 72-hour period runs from when you became aware.

• Ask staff which tools they used during the outage. A no-blame message gets more honest answers than a warning.

• Bring data back from unapproved channels, then delete it from personal email, messaging apps, consumer cloud storage and personal devices. Record what was done.

• Review mail flow and access changes made during the outage, including new forwarding rules and temporary exceptions to access policies, and remove those that are no longer needed.

• Warn staff about outage-themed phishing and ask them to report any credentials entered on unfamiliar pages.

• Request Microsoft’s post-incident report and keep it with your breach log.

Planning for the Future

Article 32 expects resilience to be planned before an incident. Four measures make the most difference:

• An approved fallback. Agree in advance which alternative tools staff may use if Microsoft 365 is down, with a processor contract in place and an entry in your records.

• Clear limits on data. Name the data that must never leave approved systems, such as health records, HR files and financial identifiers. Keep the list short enough to remember.

• An outage section in your continuity plan. Cover who invokes the fallback, how staff are told when email is down, and how you reach regulators, courts and clients.

• An updated DPIA. Add availability, dependence on a single provider and the risk of staff workarounds to the data protection impact assessment for Microsoft 365.

Conclusion

The November outage was a technical failure at Microsoft, and most customers will record it without notifying a regulator. The decision still has to be made and documented by each controller, and the workarounds staff used while systems were down need to be found and cleaned up.

We are publishing this because outages like this one show whether an organisation’s breach process, continuity plan and staff guidance work under pressure. If you want help assessing the incident or updating your plans, our GDPR consultants and data protection officer service can support you.

Frequently Asked Questions

Is the Microsoft 365 Outage a Personal Data Breach?

It can be. A loss of access to personal data falls within the GDPR definition of a personal data breach, and the ICO treats unavailability as a breach where it has a significant negative effect on individuals. Every breach must be recorded, and notification depends on the risk to individuals.

Will Microsoft Notify the Regulator for Us?

No. Microsoft acts as a processor and says it does not determine the risk of a breach for its customers. Each controller assesses the outage and decides whether to notify its supervisory authority and individuals.

Is Using WhatsApp or Personal Email During an Outage a Breach?

It can be. Moving personal data into unapproved personal accounts can breach the security principle and Article 32, and it becomes a confidentiality breach if the data reaches the wrong person or an account is compromised. The ICO’s reprimand of NHS Lanarkshire concerned this kind of informal sharing.

Disclaimer: This blog post is intended solely for informational purposes. It does not offer legal advice or opinions. This article is not a guide for resolving legal issues or managing litigation on your own. It should not be considered a replacement for professional legal counsel and does not provide legal advice for any specific situation or employer.

About the Author

Zlatko Delev

Head of Commercial & Country Manager

Zlatko Delev is Head of Commercial and Country Manager at GDPRLocal, where he leads the company’s commercial strategy and market presence. He brings international experience across sales, marketing, and customer success, along with a legal background from his studies at Iustinianus Primus Law School in Skopje, Macedonia.

Zlatko sits at the front line of GDPRLocal’s client relationships, guiding organisations through the first stages of their compliance journey and helping them understand where they stand and where they need to go on GDPR, information security, and the emerging landscape of AI regulation. His role bridges commercial strategy with practical data protection knowledge, ensuring clients get clear, actionable direction from their very first conversation with GDPRLocal.

Alongside his commercial focus, Zlatko has trained extensively in project management and organisational leadership, including risk management, stakeholder communication, agile methodology, and digital marketing, a broad skill set that supports his structured, delivery-focused approach to growing GDPRLocal’s business internationally.