Microsoft said Monday a software defect introduced in July helped trigger last week’s global Microsoft 365 outage, exposing how enterprises maintain security monitoring and incident response when their communications provider fails.
In its preliminary findings, Microsoft’s Charles Lamanna identified three contributing factors: a latent defect tied to lock contention, increased traffic after Teams switched networking gateways and an unrelated issue that had taken nearly 14% of gateway server capacity offline. Together, they caused requests to accumulate until servers stopped responding.
At the worst point, more than 80% of the affected gateway’s servers were unresponsive. Traffic redirected to surviving servers spread the failure, while safeguards intended to contain problems between infrastructure partitions failed.
Recovery required engineers to restore a previously working code path, take groups of servers offline, apply the fix and restart them before reintroducing traffic. Microsoft said its automated recovery processes were not designed for such widespread unresponsiveness. A final post-incident review is expected later this week.
The outage itself wasn’t a security breach, but it has prompted security leaders to scrutinize whether their own monitoring, access controls and incident response held up when the platform they depend on went dark — and what should change before the next disruption.
Check what security systems missed
For enterprise security teams, recovery requires determining whether alerts, endpoint reporting and access controls continued to function throughout the disruption.
“The first thing I’d check is what your detection stack didn’t see,” said Hayden Covington, associate director of security operations at Black Hills Information Security.
He explained that if an organization’s endpoint or email security tooling was degraded, there may be a window during which telemetry and alerting are thin or absent.
“That window should be reviewed after the fact,” Covington said.
Microsoft’s notices described disruptions affecting features that depend on Exchange Online, including functions within Defender and Purview.
Darin Fredde, senior director and offensive security evangelist at Ridge Security, said responders should verify that an endpoint can generate an alert, reach the response team and be isolated.
“For access controls, review emergency accounts, temporary administrator privileges, MFA exceptions, and changes to device compliance requirements,” he said. “A quiet dashboard means little if the systems feeding it were offline.”
Prepare for impersonation and improvised workarounds
Disrupted communications also give attackers an opportunity to impersonate support staff offering help with account recovery.
“Social engineering is a particular concern here, especially vishing and impersonation of Microsoft or internal IT support teams,” said Matt Hull, vice president of cyber intelligence and response at NCC Group.
Hull warned that attackers could use phone calls and text messages to request password resets, approvals for multifactor authentication or remote access. Employees should verify unexpected contact through established channels.
Security teams also need to determine where employees moved company information while normal tools were unavailable.
“I’d want to know two things: what did people do to keep working, and what was missed while monitoring was degraded,” Covington said. “Workarounds often mean personal email, personal file sharing, or relaxed policies.”
Test whether response tools remain reachable
A separate communications or security product provides limited protection against an outage if employees still need the unavailable platform to access it.
Fredde said organizations should test responder communications, recovery instructions, credentials, log access and containment capabilities during an exercise that makes selected Microsoft services unavailable. Emergency Microsoft accounts can address some lockouts but still depend on Microsoft’s identity service, he noted.
After restoration, delayed alerts should be reviewed, unnecessary permissions removed, and any remaining monitoring gaps assigned an accountable owner and a deadline.
“Organizations need a minimum response capability that remains usable when the Microsoft services they depend on are unavailable,” Fredde said.