Microsoft 365 services toppled over in North America last night due to an infrastructure misconfiguration.

[1]According to affected users, the outage started at 1810 UTC on October 9 and affected all Microsoft 365 services including Teams. The outage was brief, and just over an hour later, Microsoft confirmed that everything was back to normal.

The blackout came shortly after [2]another in which Microsoft blamed a Kubernetes crash for taking down a substantial chunk of Azure Front Door instances. Microsoft said it had "ruled out any deployments that could have triggered this event."

[3]

Of the latest wobble, Microsoft said: "We identified that a portion of network infrastructure in North America was misconfigured, resulting in impact."

[4]

[5]

Several users [6]attributed the problems to the AT&T network, although neither Microsoft nor the telco have confirmed this. Other users [7]reported that switching to a backup circuit restored services.

[8]Kubernetes kicks down Azure Front Door

[9]Subpoena tracking platform blames outage on AWS social engineering attack

[10]Texas man accidentally shoots cable, brings internet down

[11]Starlink outage knocks tens of thousands offline worldwide

The Register contacted both companies and will update the article should we receive a response.

The downtime highlights the potential brittleness of cloud infrastructure and the risks introduced by configuration changes. Microsoft did not detail the misconfiguration, but administrators left with suddenly disconnected users might question whether putting all their eggs in a cloudy basket was wise – especially when a single error can knock out services and rerouting takes time to restore them.

Regarding the debacle in North America, Microsoft [12]stated that it had "rerouted the impacted traffic to healthy infrastructure" before eventually confirming the issue as resolved.

[13]

The company's Admin Center said: "We're analyzing configuration policies and traffic management processes on the affected network infrastructure to identify necessary refinements and increase resilience in the event of future incidents."

It did not call out any particular network provider in its updates. ®

Get our [14]Tech Resources



[1] https://x.com/gustnadoex/status/1976363268655677592

[2] https://www.theregister.com/2025/10/09/kubernetes_azure_outage/

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aOktl4U0R8e6rdRD7ZqbeAAAARA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aOktl4U0R8e6rdRD7ZqbeAAAARA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aOktl4U0R8e6rdRD7ZqbeAAAARA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://x.com/polevaulthamstr/status/1976359343529562450

[7] https://www.reddit.com/r/msp/comments/1o2ej54/comment/ninguqz/

[8] https://www.theregister.com/2025/10/09/kubernetes_azure_outage/

[9] https://www.theregister.com/2025/10/02/subpoena_tracking_platform_outage_blamed/

[10] https://www.theregister.com/2025/10/01/texas_internet_outage_gunshot/

[11] https://www.theregister.com/2025/09/15/starlink_outage/

[12] https://x.com/MSFT365Status/status/1976364914106118279

[13] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/paasiaas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aOktl4U0R8e6rdRD7ZqbeAAAARA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[14] https://whitepapers.theregister.com/