The short version
- The flaw. Microsoft discovered a vulnerability in the Entra Connect Health API on 9 November 2026; the flaw had been introduced on 23 July. Microsoft says it was exploited and has since been fixed on its servers.
- What was read. Microsoft concluded that unauthorised parties had read-only access to tenant-level metadata. This included administrator and technical contact email addresses, tenant IDs, display names, initial domain names, country codes, licence tiers, directory synchronisation status and Connect Health onboarding status.
- What was not. According to Microsoft, 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.
- The response. Microsoft deployed a server-side fix on 19 November, finished its investigation on 20 November and began notifying affected organisations. It says no customer software update is required, but warns that the exposed addresses and tenant details could be used for targeted phishing.
Timeline
| Date | Event |
|---|---|
| 23 July | The vulnerability is introduced in the Entra Connect Health API, according to Microsoft. |
| 9 Nov | Microsoft discovers the vulnerability. |
| 19 Nov | Microsoft deploys a server-side fix to stop further exploitation. |
| 20 Nov | Microsoft concludes its investigation, determines read-only access to tenant metadata occurred, and begins notifying affected organisations. |
What happened
Microsoft Entra Connect Health is a cloud service that lets administrators monitor the health and performance of their on-premises identity infrastructure from the Entra admin centre. Microsoft says a vulnerability in the service's API, present since 23 July 2026, was found on 9 November and had been exploited.
In a notification to administrators, Microsoft said its investigation established that unauthorised read-only access to tenant-level metadata had occurred, and that it found no unauthorised configuration changes. An investigation determined the flaw could potentially allow monitoring configurations to be modified. Microsoft deployed a server-side fix on 19 November, closed the investigation on 20 November and began notifying customers through Azure Service Health.
Who is affected and what was exposed
Microsoft has not said how many organisations were affected. More than a dozen administrators reported receiving the notification in a Reddit thread, and some managed service providers said they received notices for several customer tenants, in one case arriving hours apart.
The exposed metadata covers administrator and technical contact email addresses; tenant IDs, display names, initial domain names, country codes and regional information; Entra licence tiers; whether directory synchronisation was enabled and when it last ran; and Connect Health onboarding status. Microsoft also said an expired certificate, once used to register Connect Health agents with an internal Microsoft service decommissioned in late 2024, remained in storage and was still returned by the API.
Microsoft says passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, and Azure subscription information were not exposed.
What Microsoft advises
Microsoft says no software update or other customer remediation is needed for the flaw itself. It does warn that the exposed administrator email addresses and tenant information could support targeted phishing and social engineering, and asks organisations to brief their security teams accordingly.
It also recommends phishing-resistant multifactor authentication for privileged accounts, a review of Connect Health configurations, and checks of Entra audit and sign-in logs for suspicious activity. A PowerShell script published at aka.ms/ConnectHealth/scripts shows the kinds of tenant metadata that could have been exposed, but displays current configuration values rather than what was actually accessed.
What is not known yet
- Who exploited the vulnerability, and whether they are linked to any known group.
- How many tenants and organisations were affected.
- When exploitation first began, and how long it continued before discovery on 9 November.
- Whether the exposed administrator addresses and tenant details have since been used in phishing or social-engineering attempts.
What to do
If you use Microsoft Entra Connect Health
- Brief your security team that administrator email addresses and tenant details may be known to an unauthorised party, and watch for targeted phishing and social engineering.
- Make sure privileged accounts use phishing-resistant multifactor authentication.
- Review your Connect Health configurations.
- Examine Microsoft Entra audit and sign-in logs for suspicious activity.
For everyone else
- Treat unsolicited requests that quote tenant identifiers, domain names or licence details as unverified until checked through a separate channel.
- Apply phishing-resistant multifactor authentication to administrative accounts as a default, not only after a vendor notice.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.