Skip to main content
Emerging ThreatsData Breaches

Microsoft Flaw Exploited to Breach Tenant Data

Secure data center with server racks and a laptop in foreground displaying a blurred screen.

"On 20 November 2026, we concluded our investigation and determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred. We did not identify any unauthorized configuration changes," Microsoft said in a notification to customers.

Microsoft's timeline and remediation

Microsoft says the vulnerability was introduced into the Entra Connect Health API on July 23, 2026, and was discovered by the company on November 9, 2026. The company deployed a server-side fix on November 19 and completed its investigation on November 20, after which it began notifying affected organizations through Azure Service Health, according to the notification and comments Microsoft provided to BleepingComputer.

What data was exposed by the Entra Connect Health flaw

Microsoft identified unauthorized read-only access to tenant-level metadata and service-monitoring metadata. The company listed the exposed items as including:

  • Email addresses belonging to tenant technical contacts and administrator accounts.
  • Tenant IDs, display names, initial domain names, country codes, and regional information.
  • Microsoft Entra license tiers and directory synchronization status, including whether synchronization was enabled and the last synchronization timestamp.
  • Connect Health onboarding status.
  • An expired certificate previously used to register Connect Health agents with a Microsoft internal service that Microsoft decommissioned in late 2024; Microsoft says the certificate was no longer in use but remained in Connect Health storage and was still returned by the API.

Microsoft explicitly stated the flaw did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, or Azure subscription information.

Impact on administrators and managed service providers

Microsoft has not disclosed how many organizations were affected. More than a dozen administrators reported receiving the notification in a Reddit post, and several managed service providers (MSPs) reported notifications for multiple customer tenants. One administrator told researchers the emails arrived hours apart for different tenants.

Although Microsoft said it did not identify unauthorized configuration changes, the exposure of administrator email addresses and tenant metadata raises immediate operational concerns for administrators and MSPs, who must now assume that contact information and tenant identifiers are known to unknown parties.

Guidance Microsoft published and available tools

Microsoft told customers that no software updates or other customer remediation were required to address the vulnerability. Still, it issued recommendations for organizations to:

  • Alert security teams to the heightened risk of targeted phishing and social-engineering attacks leveraging exposed administrator email addresses and tenant metadata.
  • Ensure privileged accounts use phishing-resistant multifactor authentication.
  • Review Connect Health configurations.
  • Examine Microsoft Entra audit and sign-in logs for suspicious activity.

Microsoft also published a PowerShell script to let administrators view the types of tenant metadata that could have been exposed; the company made the script available at https://aka.ms/ConnectHealth/scripts. Microsoft cautioned that the script displays current configuration values rather than the exact information that may have been accessed during the incident.

Attribution and scope: what Microsoft has not disclosed

The company has not named who exploited the vulnerability, how many tenants were impacted, or when the attacks first began. When contacted by BleepingComputer, Microsoft reiterated that it "identified and addressed a security issue affecting Microsoft Entra Connect Health that could have resulted in unauthorized access to tenant-level contact and configuration metadata," adding that it had deployed a fix on November 19 and notified impacted customers through Azure Service Health, but declined to provide further details about the breach.

The facts Microsoft has released establish a narrow, focused exposure: contact information and tenant metadata rather than credentials or keys. That distinction limits the technical damage recorded so far, but it leaves clear follow-on risks — targeted phishing and social-engineering campaigns that can weaponize the exposed contact lists and tenant context. Administrators and MSPs who received notifications will need to treat those data points as compromised and act on Microsoft's operational guidance while awaiting any further details Microsoft might publish about the number of affected tenants or the identity of the actor.

Read the original BleepingComputer report: https://www.bleepingcomputer.com/news/security/microsoft-entra-connect-health-flaw-exploited-to-steal-tenant-data/