Attackers exploited a flaw in Microsoft Entra Connect Health to read administrator and technical contact email addresses, along with configuration data from affected organizations.
A Microsoft customer notice shared on Reddit describes read-only access to those records, not access to inboxes or email messages. Microsoft fixed the flaw in its cloud service on November 19, 2026, and said customers do not need to install a patch.
Microsoft said the vulnerability was introduced on July 23 and detected on November 9. Investigators reviewed service logs for unauthorized requests and concluded on November 20 that attackers had read tenant data.
The flaw could also have allowed changes to monitoring settings, but Microsoft found none. The notice does not say when the unauthorized access began, who was behind it, or how many organizations were affected.
Entra Connect Health Flaw Exposed
Microsoft Entra Connect Health lets IT teams view alerts, performance data, and directory sync errors for identity systems running on their own servers. The flaw was in the cloud monitoring service’s API. Unlike a separate Entra ID flaw involving Global Administrator privileges, this incident involved confirmed reads of tenant records, with no reported takeover of administrator accounts through the flaw.
The records included each affected tenant’s ID, display name, initial domain, country code, regional scope, and Entra license tier. They also showed whether directory sync was enabled, when it last ran, and whether the organization had set up Connect Health.
The API still returned an expired certificate once used to register monitoring agents with an internal Microsoft service shut down in late 2024. Microsoft said the flaw did not expose passwords, password hashes, sign-in tokens, valid cryptographic keys, Azure subscription details, or details about how local Active Directory servers were arranged.
The cloud fix stopped further access through the flaw, but it cannot take back the contact details already exposed. Knowing who administers a tenant and which domain it uses could make a fake support message more convincing.
Previous Microsoft 365 phishing campaigns show why unexpected sign-in requests deserve scrutiny. The notice did not report any phishing linked to this incident.
Microsoft advised organizations to alert their IT and security teams, confirm their technical contact details, and require phishing-resistant multifactor authentication for privileged accounts.
Where available, teams should use Privileged Identity Management to grant admin access only when needed. They should also check Connect Health settings and review Entra audit and sign-in logs and Azure Activity Logs for unexpected changes or unusual administrator activity.
Administrators should open the Azure portal directly and check the security advisory in Azure Service Health to confirm whether it lists their tenant.
The notice also points to Microsoft’s read-only GetTenant PowerShell script, which shows the types of records the API could have returned. It reports current values, so it cannot reconstruct what attackers saw or tell an organization which specific records were read.
What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

