Microsoft Entra Connect Health Flaw Exposed Admin Emails
TL;DR · the short version
Microsoft has told affected organisations that a vulnerability in the Microsoft Entra Connect Health API was exploited to get unauthorized read-only access to tenant-level metadata. Per its Azure Service Health notice, as reported by BleepingComputer, the flaw was introduced on 23 July, found by Microsoft on 9 November 2026, fixed server-side on 19 November, and the investigation concluded on 20 November. Exposed: administrator and technical-contact email addresses, tenant IDs, names, initial domains, country and region, license tier, directory sync status and an expired, decommissioned agent-registration certificate. Microsoft says no passwords, hashes, tokens, valid keys, AD topology or Azure subscription data were exposed and no configuration was changed. No customer patch is needed. Microsoft has not said who exploited it or how many tenants were hit. Expect targeted phishing at the named admins.
Microsoft has told affected organisations that attackers exploited a vulnerability in the Microsoft Entra Connect Health API to read tenant-level metadata, including the email addresses of their administrators and technical contacts. In an Azure Service Health notice sent to admins on 20 November 2026 and quoted by BleepingComputer, Microsoft says it found the flaw on 9 November, deployed a server-side fix on 19 November and "determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred". It says it found no unauthorized configuration changes, and that no passwords, tokens or valid keys were exposed. Customers do not need to patch anything. The practical risk is targeted phishing at the people Microsoft's API named.
Who this is for: CISOs, identity and Microsoft 365 administrators, and managed service providers who run Entra ID tenants with Connect Health for hybrid identity.
Microsoft has not published an advisory, MSRC post or CVE for this. Its words below come from its Service Health notice and a spokesperson statement, both as published by BleepingComputer on 21 November 2026, and from Microsoft's own script repository, read on 22 November 2026. PlayCISO is not affiliated with Microsoft.
Confirmed vs not yet known
Microsoft says (notice to admins, as reported): a flaw in the Entra Connect Health API, introduced on 23 July and found on 9 November 2026, was exploited; unauthorized read-only access to tenant-level metadata occurred; a server-side fix went in on 19 November; the investigation concluded on 20 November; no unauthorized configuration changes were found; no customer remediation is required.
Microsoft spokesperson (to BleepingComputer): "We identified and addressed a security issue affecting Microsoft Entra Connect Health that could have resulted in unauthorized access to tenant-level contact and configuration metadata. We deployed a fix on November 19, 2026, and have notified impacted customers through Azure Service Health."
Not yet known: who exploited it, how many tenants were affected, when exploitation began, and whether a CVE will be assigned. Microsoft declined to give BleepingComputer further details. BleepingComputer reports that more than a dozen admins posted notices on Reddit and that some MSPs received notices for several customer tenants; that is not a count.
What Microsoft says was and was not exposed
| Exposed (per Microsoft's notice) | Not exposed (per Microsoft's notice) |
|---|---|
| Email addresses of tenant technical contacts and administrator accounts | User passwords and password hashes |
| Tenant IDs, display names, initial domain names, country codes and regional information | Authentication tokens and valid cryptographic keys |
| Entra license tiers and directory sync status, including the last sync timestamp | On-premises server and Active Directory topology details |
| Connect Health onboarding status | Azure subscription information |
| An expired certificate once used to register Connect Health agents with an internal Microsoft service decommissioned in late 2024 (Microsoft says it was no longer in use but was still returned by the API) | Configuration changes: Microsoft says it found none |
Read together, this is a reconnaissance haul, not a credential haul: who administers the tenant, which domain it uses, whether it syncs from on-premises Active Directory and when it last did, and which Entra license tier it pays for. That is exactly what a convincing phishing or help-desk social-engineering pretext needs. BleepingComputer also reports that Microsoft's investigation looked at whether the flaw could let attackers "potentially modify Connect Health monitoring configurations"; Microsoft's notice says it found no such changes.
What Entra Connect Health is
Microsoft Entra Connect Health is the cloud service that monitors the on-premises side of hybrid identity: Entra Connect sync servers, AD FS and domain controllers. Agents installed on those servers report into the cloud service, which shows alerts and health data in the Entra admin centre. The flaw was in that cloud service's API, so the fix was Microsoft's to make and there is nothing to install. Notices went out through Azure Service Health, which is why some admins who do not watch Service Health may not have seen theirs.
Useful next, if this was relevant to you
Timeline
| Date | Event | Source |
|---|---|---|
| Late 2024 | The internal Microsoft service the exposed certificate was used with is decommissioned | Microsoft notice, via BleepingComputer |
| 23 July (year not stated) | The flaw is introduced in the Connect Health API | Microsoft notice, via BleepingComputer |
| 9 Nov 2026 | Microsoft discovers the vulnerability | Microsoft notice, via BleepingComputer |
| 19 Nov 2026 | Microsoft deploys a server-side fix and reviews telemetry for unauthorized API calls | Microsoft notice and spokesperson, via BleepingComputer |
| 20 Nov 2026 | Microsoft concludes its investigation and notifies affected organisations through Azure Service Health | Microsoft notice, via BleepingComputer |
| 21 Nov 2026 | BleepingComputer reports the incident and Microsoft's statement | BleepingComputer |
What security leaders should do this week
- Check Azure Service Health for the notice, in every tenant you run. MSPs: check each customer tenant. Make sure Service Health alerts go to a mailbox someone reads.
- Warn the named people. Tell every global administrator and technical contact, and your help desk, to expect phishing and calls that quote your tenant ID, domain, license tier or sync details. Knowing those details proves nothing about who is calling.
- Move privileged accounts to phishing-resistant MFA (FIDO2 security keys, passkeys or Windows Hello for Business), as Microsoft recommends. Plan the rollout with the phishing-resistant MFA planner and test your assumptions in the MFA Bypass Lab. Block device-code phishing while you are at it (device code phishing blocker).
- Review Connect Health and the logs. Look over Connect Health configuration and alert recipients, then review Entra audit and sign-in logs for new admin role assignments, new app consents and unusual sign-ins to admin accounts since July. Microsoft's read-only PowerShell scripts show your current Connect Health metadata; they do not show what was accessed. If anything looks wrong, work it through the identity compromise response checklist.
- Record it as a supplier incident. Log the notice, Microsoft's statements and your actions in your risk register, and ask your Microsoft account team for the dates of any unauthorized calls against your tenant: Microsoft says it reviewed telemetry for them.
How this fits Microsoft's record
This is a confirmed security incident in a Microsoft cloud service, smaller in what was taken than Storm-0558 in 2023 or Midnight Blizzard in 2024, but the same theme: Microsoft's identity platform is part of your attack surface, and you learn about problems in it from Microsoft's notices. See Microsoft in the Breach Index for the full record, including this month's agent-framework release pipeline hijack.
Frequently asked questions
What happened with Microsoft Entra Connect Health?
Microsoft told affected organisations that a vulnerability in the Entra Connect Health API was exploited to get unauthorized read-only access to tenant-level metadata, including the email addresses of tenant technical contacts and administrators. Per its notice to admins, as reported by BleepingComputer, Microsoft found the flaw on 9 November 2026, deployed a server-side fix on 19 November and concluded its investigation on 20 November.
What data was exposed in the Entra Connect Health incident?
Per Microsoft's notice as quoted by BleepingComputer: email addresses of tenant technical contacts and administrator accounts; tenant IDs, display names, initial domain names, country codes and regional information; Entra license tiers and directory sync status, including the last sync timestamp; Connect Health onboarding status; and an expired certificate once used to register Connect Health agents with an internal Microsoft service decommissioned in late 2024.
Were passwords or tokens stolen?
Microsoft says no. Its notice, as reported, says the flaw did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, or Azure subscription information, and that it found no unauthorized configuration changes.
Do I need to patch anything for the Entra Connect Health flaw?
No. Microsoft fixed it on its own servers on 19 November 2026, and its notice says no software updates or other customer remediation are required. Microsoft recommends warning your security team about targeted phishing, using phishing-resistant MFA on privileged accounts, reviewing Connect Health configuration and checking Entra audit and sign-in logs.
How do I know if my tenant was affected?
Microsoft says it notified affected organisations through Azure Service Health. Check Service Health in the Azure portal (and any email alerts it is set to send) for a security notice about Entra Connect Health. Microsoft has not published a list or a count of affected tenants.
Is there a CVE for the Entra Connect Health vulnerability?
None has been published that we could find as of 22 November 2026. It was a flaw in a Microsoft cloud service fixed server-side, and Microsoft has given no CVE, MSRC advisory or public blog post; its statements so far are the Service Health notice and a statement to BleepingComputer.
Who exploited the Entra Connect Health flaw?
Not disclosed. Microsoft has not said who exploited it, how many tenants were affected or when exploitation began. The flaw was introduced on 23 July, per the notice as reported, so the exposure window could be months long.
Sources
- BleepingComputer: Microsoft Entra Connect Health flaw exploited to steal tenant data (21 November 2026), quoting Microsoft's Azure Service Health notice and a Microsoft spokesperson
- Microsoft (GitHub, AzureAD/EntraIDGovernance): Connect Health read-only PowerShell scripts (aka.ms/ConnectHealth/scripts)
- Microsoft Learn: What is Microsoft Entra Connect and Connect Health
- Microsoft Learn: Azure Service Health overview