Microsoft 365 Outage Disrupted Defender and Purview Along With Outlook and Teams

Microsoft outage https://pixabay.com/illustrations/ai-generated-face-modern-touch-8497925/

A widespread Microsoft 365 outage on Nov. 12–13 disrupted Outlook, Teams, Copilot, and other cloud services, leaving users unable to access email, schedule meetings, or use workplace applications. The outage also affected Microsoft Defender and Purview, disrupting security and compliance functions that organizations rely on to protect their systems and data.

According to Microsoft's service advisories, some Defender for Office 365 Safe Links functions were unable to verify URLs, while users experienced problems accessing portions of the Defender XDR portal. Purview capabilities, including data loss prevention and information protection, also experienced disruptions.

The incident affected services dependent on Exchange Online and related infrastructure, demonstrating how failures in shared cloud systems can disrupt both business operations and cybersecurity protections.

How a Software Bug Caused the Outage

Microsoft traced the outage to three contributing factors: a previously undetected software defect, increased traffic following a Microsoft Teams failover, and reduced server capacity.

According to a preliminary post-incident report released Nov. 16, the defect originated in an update deployed to Microsoft's networking gateway servers beginning in July. It went undetected for months because the problem emerged only under certain traffic and hardware conditions. Microsoft said its testing failed to identify the issue partly because its test environments used less powerful servers than those where the defect was most pronounced.

About 15 hours before the outage, an automated failover shifted Teams traffic onto gateway infrastructure also used by Exchange Online. At the same time, nearly 14% of gateway server capacity was unavailable because of an unrelated issue.

During peak U.S. business hours, the increased traffic triggered the defect, exhausting server resources. Microsoft's automated systems redirected requests from unresponsive servers to those still operating, overwhelming the remaining infrastructure. Within two hours, more than 80% of the affected gateway servers were unresponsive.

Safeguards designed to prevent disruptions from spreading between infrastructure regions were also ineffective. Microsoft attributed that problem to a separate issue but did not explain its cause in the preliminary report.

Recovery was complicated because restarted servers became overwhelmed again as traffic returned. Microsoft ultimately developed an update restoring the affected software to a previously working state and gradually returned servers to service.

Security Tools Caught in the Outage

According to Microsoft's service advisories, Defender for Office 365 experienced problems with Safe Links, which checks URLs for malicious destinations, and Safe Attachments, which identifies potentially dangerous email attachments. Administrators also encountered difficulties accessing protection policies, quarantined messages, Threat Explorer, and email remediation features.

Microsoft Defender XDR experienced problems loading security portal pages and solution tabs, potentially complicating security teams' ability to investigate alerts and manage incidents.

Microsoft Purview, the company's data security and compliance platform, also experienced disruptions affecting data loss prevention (DLP), automatic sensitivity labeling, information protection, and other compliance functions. Microsoft warned that some policies intended to protect sensitive information could experience delays or failures in evaluation and enforcement.

The problems raised concerns about the operational risks of security tools relying on the same infrastructure as the applications they protect.

“The lesson for organizations is to know what depends on what,” said Waseem Ahmed, Head of Engineering at Secure.com. “Ask which tools, including security tools, stop when your email provider does.”

The disruptions affected specific security capabilities rather than Microsoft's entire security infrastructure. Microsoft said it did not find evidence of malicious activity causing the outage and has not identified a resulting security breach.

Phishing Campaign Exploits the Disruption

As Microsoft worked to restore its services, attackers exploited the outage in a phishing campaign targeting organizations across multiple industries.

Microsoft Threat Intelligence reported detecting the campaign on Nov. 13. The fraudulent emails impersonated Microsoft 365 service-health notifications, claiming messages had been delayed during the outage and would be permanently deleted unless recipients took immediate action.

Some messages included a "RESTORE MESSAGES" button directing users to non-Microsoft websites. The attackers referenced the Exchange Online disruption and Microsoft services to make the notifications appear legitimate.

Microsoft assessed that the campaign was likely intended to steal account credentials but did not establish that attackers successfully obtained passwords or compromised accounts.

The company advised organizations to verify service disruptions through the Microsoft 365 admin center rather than links in unsolicited emails. Users should avoid suspicious account-restoration notices and never enter credentials on unfamiliar websites. Security teams should investigate employees who clicked the links and reset credentials if passwords may have been exposed.

Lessons for Enterprise Security and Business Continuity

The outage highlighted the risks of relying on a single cloud provider for business applications and cybersecurity services. While consolidating services can simplify management, shared infrastructure can create single points of failure affecting multiple operations.

IT and security teams should map dependencies between critical applications and security controls to identify what could become unavailable during a provider outage. That assessment should determine whether security teams could still investigate threats and enforce protection policies.

“Resilient organizations know which systems and data they can’t operate without and have a plan for how people communicate and work when a primary platform is unavailable,” said Adam Laub, Chief Growth Officer at Superna.

Organizations should maintain communication channels independent of their primary cloud provider and regularly test business continuity procedures to ensure critical operations can continue during an outage.

Those plans should also address what happens after service is restored. An outage can interrupt access without causing permanent data loss, but restoring service does not guarantee that every interrupted process has been completed.

IT teams should therefore verify that delayed emails were delivered and critical files remain accessible. They should also confirm that security policies and permissions are functioning correctly.

Although cloud outages cannot be eliminated, identifying dependencies and testing recovery procedures can help organizations maintain essential operations when critical services fail.

Author
  • Michael Ansaldo
    Contributing Writer, Security Buzz
    Michael Ansaldo is a veteran technology and business journalist with experience covering cybersecurity and a range of IT topics. His work has appeared in numerous publications including Wired, Enterprise.nxt, PCWorld, Computerworld, TechHive, GreenBiz, Mac|Life, and Executive Travel.