Microsoft Entra Connect Health Leaked Tenant Metadata for Four Months. No Patch to Install, but Your Admin Emails Are Now Phishing Targets.

If your organization uses Microsoft Entra Connect Health, open the Azure portal, go to Service Health, and look under Security advisories for a notice about Connect Health. SecurityOnline reports that only tenants that got that direct notice had confirmed unauthorized reads; we could not read Microsoft's own wording on that point. Either way, there is nothing to patch: Microsoft fixed the flaw on its own servers on Thursday, November 19. What is left for you is the fallout: someone may now hold your administrators' email addresses, your tenant ID and your license tier, which is exactly the starting kit for a targeted phishing run against your admins.
Am I affected?
Run these checks in order. They take about fifteen minutes.
- Did you get the notice? Azure portal, Service Health, Security advisories, and the inbox of your tenant's technical contact. Microsoft notified affected organizations starting Friday, November 20. Managed service providers have reported notices for several customer tenants at once, so check every tenant you administer, not just your own.
- See what the API returned for your tenant. Microsoft published read-only PowerShell scripts at aka.ms/ConnectHealth/scripts (it redirects to the AzureAD/EntraIDGovernance repository on GitHub, folder ConnectHealth, first uploaded November 18). Sign in with Connect-AzAccount to the tenant, then run GetTenant.ps1. It makes one HTTP GET to the Azure Resource Manager endpoint for the Microsoft.ADHybridHealthService provider and prints the tenant configuration as JSON. GetTenantPksCertificateDetails.ps1 decodes the expired certificate metadata in memory. The scripts need the Az.Accounts module, version 2.17.0 or later, and read access to Connect Health. Microsoft's caveat matters: the scripts show today's values, not what was read during the incident.
- List the people whose addresses were exposed. Microsoft names the email addresses of tenant technical contacts and administrator accounts. In the Entra admin center, read the technical contact under tenant Properties, then list who holds Global Administrator and the other privileged roles. Those are the people to warn.
- Confirm phishing-resistant MFA on every one of them. Microsoft's own guidance. Passkeys, FIDO2 keys or Windows Hello for Business, not SMS or push approval. An attacker who knows exactly which addresses are admins will try MFA fatigue and fake "Microsoft security notice" emails first.
- Review Entra sign-in and audit logs. Microsoft's guidance, without specifics. Our suggestion for what to look for: sign-ins for your privileged accounts from new countries or hosting providers since July 23, new MFA methods registered on admin accounts, new app credentials or consent grants, and new role assignments. Microsoft says it found no configuration changes, but a phishing follow-up would show up in these logs, not in Connect Health.
- Review your Connect Health setup. Also Microsoft's guidance. In the Connect Health blade, check which servers are registered and who has been granted access to Connect Health itself. Remove registrations for servers you retired.
There is no agent version to check. The flaw was in Microsoft's cloud API, not in the Connect Health agent on your servers, and Microsoft says no software update is needed.
What is confirmed
All of this comes from one source: Microsoft, through its notification to affected tenants (shared by administrators on Reddit's r/sysadmin; Reddit blocked our fetcher, so we read the text as quoted by BleepingComputer and SecurityOnline) and a Microsoft spokesperson's statement to BleepingComputer.
- Dates. Microsoft says the flaw was introduced into the Connect Health API on Thursday, July 23, 2026. Microsoft says, "On 9 November 2026, we detected a vulnerability in the Microsoft Entra Connect Health API." The spokesperson: "We deployed a fix on November 19, 2026." Microsoft finished its investigation and began notifying organizations on November 20. That is a window of almost four months.
- What was read. Microsoft's notice says "unauthorized read-only access to tenant-level metadata associated with your organization had occurred." The exposed data: email addresses of tenant technical contacts and administrator accounts; tenant IDs, display names, initial domain names, country codes and regional information; Entra license tiers; directory sync status, including whether sync was on and the last sync time; Connect Health onboarding status; and an expired certificate once used to register Connect Health agents with a Microsoft internal service decommissioned in late 2024. Microsoft says the expired certificate "remained in Connect Health storage and was still returned by the API" and that it poses no risk.
- What was not. Microsoft says the flaw "did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys," and reports no exposure of on-premises server or Active Directory topology or Azure subscription information.
- No changes. "We did not identify any unauthorized configuration changes."
What is not known
- Who did it. Microsoft has not named the actor, and has not said when the reads began within the July 23 to November 19 window.
- How many tenants. Not disclosed. BleepingComputer counted more than a dozen administrators reporting the notice.
- How it worked. No root cause beyond "a vulnerability in the API." SecurityOnline reports the bug could in theory have allowed configuration edits, while logs showed only reads; we could not trace that to a Microsoft statement.
- A CVE. None. We queried Microsoft's Security Update Guide on November 21: no CVE carries Connect Health or Hybrid Health in its title, and the newest Entra entries (CVE-2026-109460, Private Network Connector, and CVE-2026-109469, Device Registration) are different issues. CVE-2026-65673 (Entra Connect elevation of privilege, August 11) is also a separate bug.
- CISA KEV. Not listed. We read the KEV JSON, catalog version 2026.11.20 released November 20: no Entra or Connect Health entry. A server-side cloud fix with no CVE would not normally appear there.
- Indicators. None published in the sources we read. No IPs, domains, hashes or app IDs.
What our data shows
- Coverage. We had no post on Connect Health before this one.
- Feed. We added nothing, because no indicators were published. Our IOC corpus holds no record for Connect Health or Entra Connect. One unrelated record names the service: a malicious npm package called adhybridhealthservice-resource-manager, in our corpus since August 28, 2025 from the OSV malicious-packages feed. That is someone squatting the service name on npm, a third-party listing, not connected to this incident.
- Edge. We scanned our edge for any request path containing hybridhealth or connecthealth since July 1: 0 matches in 775,197 edge blocks, 201,875 canary hits and 7,661 origin honeypot captures. That zero says little. This attack hit Microsoft's API, not websites like ours, so our sensors could never have seen it. No first-party sighting, and none was possible.
Why this one matters more than "read-only" suggests
Tenant metadata is reconnaissance done for the attacker. A list that pairs a tenant ID and initial domain with the exact addresses of its administrators, the license tier (which tells you whether the victim has Entra ID P2 risk-based Conditional Access), and whether directory sync is on (which tells you there is an on-premises AD to aim for) saves a phishing crew weeks. Treat the next "Microsoft security notice" email your admins receive with suspicion, including ones about this incident. Verify it by opening Service Health in the portal yourself, never through a link in the email.
Sources
- BleepingComputer, Lawrence Abrams, "Microsoft Entra Connect Health flaw exploited to steal tenant data," November 21, 2026 (Microsoft spokesperson statement and quoted notification text): https://www.bleepingcomputer.com/news/security/microsoft-entra-connect-health-flaw-exploited-to-steal-tenant-data/
- SecurityOnline, "Microsoft Entra Connect Health Exposure Leaked Tenant Metadata": https://securityonline.info/microsoft-entra-connect-health-exposure/
- Microsoft, Connect Health reference scripts (aka.ms/ConnectHealth/scripts): https://github.com/AzureAD/EntraIDGovernance/tree/main/ConnectHealth
- r/sysadmin thread with the Microsoft notification (blocked to our fetcher): https://www.reddit.com/r/sysadmin/comments/1y1of2u/important_security_notification_regarding/
- CISA Known Exploited Vulnerabilities catalog, version 2026.11.20: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Read next: ConnectWise Cloud Backup Lost One App Secret. We Ran the Checklist on Our Own Microsoft 365 Tenant, the sign-in and audit log checklist for a Microsoft 365 tenant, run on our own.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.