Microsoft Entra Connect Health flaw exposed tenant metadata, not credentials
Affected organisations face a higher risk of targeted phishing aimed at the administrator contacts exposed by the flaw.
Microsoft has disclosed that attackers abused a flaw in the Entra Connect Health API, a cloud service that monitors on-premises identity infrastructure, to read tenant-level metadata. The flaw was found on November 9, 2026, and the investigation concluded on November 20 with confirmed read-only access and no detected configuration changes. Exposed data includes administrator and technical contact emails, tenant IDs, domains, license tiers and sync status, but not passwords, hashes, tokens or keys. Microsoft fixed the issue server-side on November 19 and notified affected customers through Azure Service Health, and it has not said how many tenants were hit or who was responsible. Administrators need no patching, but Microsoft advises watching for targeted phishing aimed at the exposed contacts, enforcing phishing-resistant MFA on privileged accounts, and reviewing audit and sign-in logs.
Why it matters
The incident shows that metadata alone can make an organisation a target. Administrator and technical contact addresses and tenant configuration details are now known to an unknown party, so attackers have a ready list of people to approach with convincing messages. Since Microsoft has not said how many tenants were hit or when the activity began, administrators cannot yet tell whether they were among them. The fix is already in place server-side, so the remaining exposure is the risk of follow-on social engineering rather than an open vulnerability.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.