Steve Miller's Blog

When the Zero Trust Proxy Goes Down, Some Microsoft 365 Users Go Down With It: Planning for Your SSE Provider’s Bad Day

Three IT colleagues gather around a desk with a notepad and closed laptop to plan a contingency in a bright open office

On October 13, some Microsoft 365 users could not reach their mail, files and meetings, and the cause was not Outlook or Teams themselves. Microsoft’s own incident notes point to its Global Secure Access service, the cloud network layer many organizations use to route traffic to Microsoft 365. Search for “Microsoft Global Secure Access outage Microsoft 365” and you will find coverage of exactly this event. That shorthand is useful as long as you keep the narrow scope in mind. This post lays out what Microsoft’s notices actually say, then what I would change in a plan that depends on a security service edge (SSE) provider.

What Microsoft’s Notices Say

Microsoft tracked the event as incident MO1505952. The notice text, as republished by 365Fanatic from a West Europe tenant and in the University of Pennsylvania’s mirror of Microsoft’s incident reports, reads like this:

The cause Microsoft names is in Global Secure Access itself. Nothing in these notices attributes the problem to Microsoft Entra ID or Exchange Online, and I am not claiming either way beyond what Microsoft says. I am also not going further on root cause. Microsoft has published a post-incident report, according to the status entries, but I could not read its contents.

Microsoft Global Secure Access Outage, Microsoft 365 Impact: Narrower Than the Headlines

This matters for anyone deciding how worried to be. The impact was scoped to users “using GSA,” not to everyone on Microsoft 365. IncidentHub, which recorded Microsoft’s updates, writes that its updates “do not say Microsoft 365 was unavailable for users who were not using GSA.”

The geography changed during the incident. Early updates said “Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.” Microsoft’s final notice narrows that to “Some users in Germany.” IncidentHub’s timeline says the scope was narrowed to Germany only in the 17:26 UTC update. So “UK and Germany” is accurate for most of the incident, and “Germany” is what Microsoft’s final notice states.

The start time also moved. IncidentHub notes that updates before 17:26 UTC stated an 08:00 UTC start, which Microsoft later revised to 07:40 UTC. Aggregators therefore disagree on duration. I use Microsoft’s final start and end times.

One more useful detail. Microsoft’s updates show it first tried “performance and traffic optimizations,” then “redirecting traffic from the underperforming infrastructure,” then “targeted restarts.” A status entry also says “As a workaround, users may disable GSA to access the affected Microsoft 365 services until the resolution of this incident.” IncidentHub says that workaround first appeared at 18:20 UTC, about 11 minutes before the stated end. Other trackers time that entry slightly earlier, so treat the exact minute as approximate. Either way, it appeared late in a window of almost 11 hours.

Planning for Your SSE Provider’s Bad Day

Everything from here down is my own opinion and recommendation. Microsoft and the sources above do not say any of it.

Here is my view of the lesson. Moving to zero trust and a cloud security edge removes some old single points of failure, such as one VPN concentrator. It can also add a new dependency. If your users reach Microsoft 365 through a cloud service edge, then that service’s health is part of your Microsoft 365 availability. This incident does not show that every organization has that exposure. It shows that organizations that do route through GSA were exposed to it.

Picture this hypothetical. Your help desk gets a wave of “can’t open Outlook or Teams” tickets from one region. Your tenant dashboard shows no Exchange or Teams problem, and half the team spends the first hour troubleshooting endpoints. Nobody thinks to check whether the security edge is the common factor.

What I would put in place:

  1. Know which traffic depends on the edge. Document which user groups, regions and Microsoft 365 workloads are forwarded through your SSE service, and which are not.
  2. Write the bypass decision down before you need it. Microsoft’s own workaround in this incident was to disable GSA. Decide who may approve that, what security controls you give up while it is off, and how you turn it back on.
  3. Keep a break-glass path. Have a tested way to reach critical services if the edge is degraded, such as a small group of pre-approved devices or a documented exception policy, with logging and a time limit.
  4. Test fallback policies in pilot rings. Try switching a small group off the edge during a planned test, so the first time you do it is not mid-incident.
  5. Monitor from the user’s side. Synthetic checks that sign in and open mail or files from the regions you care about will catch a path problem that the provider’s dashboard may not describe yet.
  6. Add the SSE service to your incident triage. When several Microsoft 365 apps fail at once for one region, check service health for the edge service early.
  7. Ask for the post-incident report. Read it, and ask your account team what changes are planned.

The Bottom Line

This was a real incident of nearly eleven hours, with a named cause in Microsoft’s Global Secure Access infrastructure, and a scope that narrowed from Germany and the UK to Germany. It was not a global Microsoft 365 failure. The planning lesson, in my view, is still worth taking: if a security service sits in front of your productivity suite, write the runbook for its bad day before it has one.

Exit mobile version