Skip to content
Microsoft Entra Connect Health flaw exposed admin emails and tenant metadata; fixed server-side

Microsoft Entra Connect Health flaw exposed admin emails and tenant metadata; fixed server-side

First seen 21 Nov 2026, 21:46 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 15:44 UTC
  • •Attackers exploited an Entra Connect Health API flaw to read tenant metadata, including admin and technical contact email addresses.
  • •Microsoft says no passwords, hashes, tokens, valid cryptographic keys, or configuration changes were involved.
  • •A server-side fix was deployed November 19, 2026; no customer patch is required.
  • •The number of affected tenants and the identity of the attackers have not been disclosed.
  • •Organizations should expect targeted phishing using exposed contact details and enforce phishing-resistant MFA on privileged accounts.

Microsoft says attackers exploited a flaw in the Entra Connect Health API to gain unauthorized read-only access to tenant-level metadata, according to a customer notification reported by BleepingComputer. Microsoft found the flaw on November 9, 2026, after it was reportedly introduced on July 23. Exposed data reportedly includes administrator and technical contact email addresses, tenant IDs, display names, initial domain names, country and region codes, license tiers, directory sync status, and an expired Connect Health agent certificate. Microsoft states that passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises topology, and Azure subscription information were not exposed, and that no unauthorized configuration changes were found. A server-side fix was deployed on November 19, and no customer software update is required. Microsoft has not disclosed how many organizations were affected, who was responsible, or when the exploitation began; more than a dozen administrators reported receiving the notice. Microsoft recommends watching for targeted phishing and social engineering that could use the exposed contact details, ensuring privileged accounts use phishing-resistant MFA, and reviewing Connect Health configurations and audit and sign-in logs. No CVE is listed for this flaw in the verified data.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-07-23
Vulnerability introduced in Entra Connect Health API
According to Microsoft's customer notification, the flaw was introduced on this date.
Bleepingcomputer
2026-11-09
Microsoft discovers the flaw
Microsoft found the vulnerability in the Entra Connect Health API, which reportedly had been exploited.
Bleepingcomputer
2026-11-19
Server-side fix deployed
Microsoft deployed a server-side fix; no customer software update is needed.
Businessupturn

More articles in this cluster (13)

Following this threat?

Track Microsoft and CVE-2025-42884 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Am I affected?
Microsoft is notifying affected tenant administrators directly; the number of affected organizations has not been disclosed. Review the Connect Health scripts Microsoft published to inspect the metadata your tenant returns.
Do I need to patch?
No customer update is required because Microsoft applied the fix server-side on November 19, 2026.
What should we do now?
Alert security teams to possible targeted phishing, enforce phishing-resistant MFA on privileged accounts, and review Connect Health configurations and audit and sign-in logs for suspicious activity.