Microsoft’s service health page on Friday, 13 November listed Microsoft Defender XDR, Defender for Office 365 and Microsoft Purview among the services hit by a Microsoft 365 incident it titled “Users may be unable to connect to multiple Microsoft 365 services.” Microsoft wrote that it is “seeing broad recovery and stability across our services” and that “This was a technical issue not related to cyber or AI / agents.”

What the notice lists for security teams

According to the notice, users “may be unable to load Microsoft Defender portal pages or solution tabs.” Defender for Office 365 experiences that rely on Purview DLP and Information Protection signals may see delays or failures in policy evaluation and governance action enforcement. In Purview, Microsoft listed Data Loss Prevention across Microsoft 365, Communication Compliance, auto-labeling, role-based access control, audit searches and eDiscovery search and export as affected.

On cause, Microsoft said the incident “was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change,” and said a full post-incident report will follow once its review is complete.

Why it matters

The affected list covers three layers a SOC leans on at once: the Defender console, label-based DLP enforcement on mail and files, and the audit and eDiscovery trail used to reconstruct what happened. Microsoft describes failures in policy evaluation, so some DLP and labeling actions during the window may not have run as configured.

Once Microsoft marks the incident resolved, review DLP and Communication Compliance alerts for the outage window, rerun any audit searches and eDiscovery exports started during it, and file the post-incident report with your Microsoft risk records. Teams tightening Microsoft tenant controls this month can also read our coverage of Entra’s new hard deletion protection preview and Microsoft’s Q3 count of 7.3 billion phishing threats.

Source: Microsoft 365 Service health