r/sysadmin 1d ago

General Discussion Rough Summer for Microsoft

Today's Exchange/O365 (EX1464935/MO1465074) outage seems to be a result of the instability we've been seeing the last 3 or 4 months due to the rapid change occurring regularly in the Microsoft ecosystem. This one is more visible to end users than other problems we've faced this summer. I'm curious if the stability of government tenants has been better. Are commercial tenants the beta testers for government tenant changes?

174 Upvotes

76 comments sorted by

View all comments

2

u/amreagan 1d ago

If they don't have this fixed by the time US east coast work day starts tomorrow, tomorrow's graph won't look like this.

Aug 31, 2026, 4:55 PM CDT
We're continuing our targeted review of affected infrastructure and recent changes made to the service to definitively confirm the cause of impact. We're additionally continuing to test and implement various mitigation strategies to apply the necessary authentication component, which have so far yielded positive results. We're monitoring these tests and mitigative actions closely and will provide an estimated time to resolution as soon as one is available.

 

Aug 31, 2026, 3:36 PM CDT

We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including potentially reverting an update the affected infrastructure recently received. We're performing additional tests to evaluate the best course of action moving forward.

 

Aug 31, 2026, 2:43 PM CDT

We're continuing to perform comprehensive tests to ensure our mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, we're exploring alternative remediation avenues to minimize impact in the interim.

 

Aug 31, 2026, 1:41 PM CDT

We're continuing to fine-tune our remediation strategy as our internal tests progress. We'll aim to provide an estimated time for remediation as soon as it's available.

 

Aug 31, 2026, 1:18 PM CDT

We're continuing to test our remediation strategy and in parallel we're working to confirm whether other services are impacted so we can expand our communications accordingly. This quick update is designed to give the latest information on this issue.

 

Aug 31, 2026, 12:23 PM CDT

We've identified a potential corrective action for the affected infrastructure and are evaluating deployment options. We're monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.

 

Aug 31, 2026, 11:33 AM CDT

We’ve isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. We're analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, we’re continuing to assess the scope of impact and monitor for additional affected scenarios.

 

Aug 31, 2026, 11:16 AM CDT

We're reviewing service telemetry and diagnostic data to isolate the source of the issue after receiving an increase in user-reported issues affecting Exchange Online. We'll keep refining the 'more info' section as additional impacts are identified.

 

Aug 31, 2026, 10:55 AM CDT

We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings. This communication serves as a preliminary notification about a potential issue affecting your service.

 

More info

We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074. We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service. Users may experience a variety of symptoms related to this event, including but not limited to: - Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes. - Delays or failures when sending or receiving email messages. - Authentication-related errors when accessing Exchange Online services. - Difficulties accessing or performing actions within Exchange administration experiences. - Intermittent failures affecting mailbox operations and message delivery workflows.

 

Scope of impact

This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.

 

Preliminary root cause

An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.

u/cavegriswold 22h ago

How many times do you think they re-fed that same "we are continuing..." line back into Copilot to spit out the next time they were about to miss a deadline?

u/Dal90 8h ago

tomorrow's graph won't look like this.

Pretty sure today's market would reward them for finding ways to squeeze even more margin out of Microsoft's already obscene margin by reducing QA. It won't impact the stock price downwards any more than then number of pigeons flying around Wall Street on any given day would.

What's the alternative? Exchange on-prem? Win!

Any one of the list of "no viable candidates to enterprises, despite what a bunch of redditors are about to claim (since they're only thinking technical and not corporate political)"? You mean the same publicly traded companies that folks who own large parts of Microsoft also own large parts of their competitors? Tails the investors win, heads the same investors win, so that's just a wash. So the investors instead want everyone they own to focus on increasing margins.

Remember folks, we all rightfully vilify Broadcom for absolutely trashing VMware's viability for most companies. Also since they bought VMware their stock has nearly quadrupled on a split-adjusted basis. Developers, developers, developers Margins, margins, margins!

u/Curtis_Low 9h ago

And the issues remain....