Cloud SecurityIdentity

Entra Connect Health Flaw Leaked Tenant Metadata and Admin Emails for Months. Expect the Phishing Next.

November 22, 2026 · Brian Deitch

Microsoft is notifying customers that attackers used a flaw in the Microsoft Entra Connect Health API to read tenant data. Nobody's passwords leaked. But the data that did leak is exactly what you'd want if your next step was a convincing phishing email to the people who run a company's identity system.

What Happened

Per Microsoft's customer notice, as reported by Cyber Security News, The CyberSec Guru and Windows Forum (which cites BleepingComputer):

  • The flaw was introduced July 23, 2026, detected November 9, fixed server-side November 19, and Microsoft concluded its investigation November 20. That's 109 days from introduction to detection.
  • What was read: tenant ID, display name, initial domain, country and region, license tier, directory sync status, and admin and technical contact email addresses.
  • What Microsoft says was not exposed: passwords, hashes, tokens, valid keys, Azure subscription details and on-premises topology.
  • The root of it, per the notice as reported: the API kept returning an expired certificate tied to an internal Microsoft service that was shut down in late 2024. Microsoft says the certificate "poses no risk."
  • Read-only: Microsoft found no changes to monitoring settings.
  • Scope: Microsoft hasn't said how many tenants were hit or who did it. Only tenants that got a direct Azure Service Health advisory had confirmed read activity.

The fix is in Microsoft's cloud, so there's nothing to install. Credit to Microsoft for telling affected customers directly and spelling out what was and wasn't touched. The 109 days is the uncomfortable part.

Why Metadata Matters

"Just metadata" is how these stories get dismissed. Think like the attacker. You now know who the Entra admins are, what licenses the tenant has, whether it syncs from on-prem AD, and what the official domain looks like. That's a ready-made target list for MFA fatigue, device code phishing, help desk vishing and fake "Microsoft security notice" emails. The irony is that a real Microsoft security notice is going out right now, which makes a fake one easier to believe.

This is also a reminder that SaaS and cloud control planes are part of your attack surface even when you never touch the code. You can't patch Microsoft's API. You can make the stolen information less useful.

What To Do

  • Check Azure Service Health in the portal for the advisory. Don't trust email links claiming to be the notice.
  • Brief your admins and technical contacts today. Assume they'll get targeted phishing that knows the tenant name and license tier.
  • Require phishing-resistant MFA (FIDO2 or passkeys) for every privileged role, and block device code flow where you don't need it.
  • Use PIM so admin rights are just-in-time, not standing.
  • Review Entra sign-in and audit logs for privileged accounts from late July on, and review your Connect Health settings.
  • Tighten help desk identity checks for admin password and MFA resets. That's where the vishing calls will land.

Bottom Line

No passwords leaked, and Microsoft fixed it. But a list of who runs your identity system is the attacker's first page of notes. Lock down those accounts like you expect a call, because you probably should.

Sources: Cyber Security News, The CyberSec Guru, Windows Forum, BleepingComputer

microsoftentra-identra-connect-healthtenant-metadataphishingmfapimsaas-security
All postsDiscuss on LinkedIn