Microsoft Entra Connect Health Flaw Exposed Admin Emails and Organization Data
A vulnerability in Microsoft Entra Connect Health's API allowed attackers to access administrator email addresses and organization data, with Microsoft patching the issue in its cloud service.

Attackers exploited a flaw in Microsoft Entra Connect Health's cloud monitoring service API to gain read-only access to administrator email addresses and sensitive organization data. The vulnerability, which was present from July 23 to November 19, 2026, allowed threat actors to view tenant IDs, display names, and sync status, but crucially, not inboxes or credentials. Microsoft confirmed the fix was deployed to its cloud service on November 19, 2026, and stated that customers do not need to install any patches.
The vulnerability was introduced on July 23 and detected on November 9, 2026. Following an investigation of service logs, Microsoft concluded on November 20 that attackers had indeed accessed tenant data. While the flaw could have potentially allowed modifications to monitoring settings, Microsoft found no evidence of such changes. The exact timeline of the unauthorized access, the identity of the perpetrators, and the total number of affected organizations remain undisclosed.
Microsoft Entra Connect Health is designed to help IT teams monitor alerts, performance data, and directory synchronization errors for identity systems hosted on their own servers. The exploited flaw resided within the cloud monitoring service's API. Unlike a separate incident involving Entra ID and Global Administrator privileges, this breach specifically involved the confirmed reading of tenant records, without any reported account takeovers.
The exposed tenant records included essential information such as each tenant's ID, display name, initial domain, country code, regional scope, and Entra license tier. Additionally, the compromised data revealed whether directory synchronization was enabled, the last time it ran, and if the organization had configured Connect Health. The API's vulnerability stemmed from its continued use of an expired certificate, which was previously used to register monitoring agents with an internal Microsoft service that was decommissioned in late 2024.
Microsoft has emphasized that the vulnerability did not expose passwords, password hashes, sign-in tokens, valid cryptographic keys, Azure subscription details, or specific configurations of local Active Directory servers. The cloud-based fix has successfully halted further unauthorized access through this specific flaw, but it cannot revoke the contact details that have already been exfiltrated. The exposure of administrative contact information could potentially be leveraged by attackers to craft more convincing phishing or social engineering attacks.
While the notice did not report any direct phishing campaigns linked to this incident, Microsoft strongly advises organizations to alert their IT and security teams. Customers should verify their technical contact details and implement phishing-resistant multi-factor authentication (MFA) for all privileged accounts. Where feasible, organizations are encouraged to utilize Privileged Identity Management (PIM) to grant administrative access on a just-in-time basis.
Microsoft also recommends that administrators review their Connect Health settings and examine Entra audit logs, sign-in logs, and Azure Activity Logs for any unusual changes or suspicious administrator activity. Users can check the Azure portal directly and look for the security advisory within Azure Service Health to confirm if their tenant is listed as affected. Microsoft's GetTenant PowerShell script can provide insight into the types of records the API could have exposed, though it cannot reconstruct the exact data read by attackers.