Was your Entra tenant hit by the Connect Health flaw?
The flaw ran from July 23 to a server-side fix on November 19. No patch is needed, and Microsoft is notifying affected tenants through Azure Service Health.

Possibly. Microsoft says attackers exploited a flaw in the Entra Connect Health API, introduced July 23 and found November 9, to read administrator email addresses and tenant metadata. It fixed the service on November 19 and is notifying affected tenants through Azure Service Health. Microsoft says passwords, tokens and on-premises topology were not exposed.
What did the attackers read?
Microsoft's notice, as reported by BleepingComputer, covers five kinds of data:
- The email addresses of tenant technical contacts and of administrators.
- Tenant IDs, display names and initial domains, plus country codes and regional details.
- Which Entra license tier the tenant holds, whether directory sync was on and when it last ran.
- Connect Health onboarding status.
- One expired certificate that Connect Health agents once used to enroll with a Microsoft service retired in late 2024.
Microsoft says that certificate was no longer in use but was still in Connect Health storage, and the API still returned it. Connect Health is the cloud service that lets administrators watch the health of their on-premises identity infrastructure from the Entra admin center.
What did Microsoft say was not exposed?
Microsoft says no passwords, password hashes, tokens or usable cryptographic keys were exposed. It also says nothing about the layout of on-premises servers or Active Directory, or about Azure subscriptions, was exposed. Microsoft finished its investigation on November 20 and concluded that read-only access to tenant-level metadata had occurred. It says it found no unauthorized configuration changes, though the flaw could have allowed changes to Connect Health monitoring configurations.
How do I know whether my tenant was affected?
Microsoft sent the notices on November 20 and says affected customers are being told through Azure Service Health. An administrator shared the notice on Reddit's r/sysadmin, and BleepingComputer reported that more than a dozen administrators said in the thread they had received it. Some managed service providers reported notices for several customer tenants, and one administrator said they arrived hours apart.
Microsoft has not said how many organizations were affected, who exploited the flaw, or when the attacks began. The sources read for this story do not say whether a tenant with no notice was untouched, so check Service Health directly instead of assuming.
Is this the same as the Global Reader flaw Cymulate reported?
No source read links the two, and they are different bugs in the same service. Cymulate's report was published September 3. A user holding only the Global Reader or Security Reader role could retrieve the Connect Health agent's client secret through an Azure Resource Manager call, and reading it rotated the key and knocked the real agent offline. Cymulate says Microsoft rated it Important and confirmed on August 10 that it was resolved, with rollout in progress.
Microsoft's November notice describes an API flaw introduced on July 23 that exposed metadata. Cymulate's September advice, to review who holds read-only Entra roles, concerned a different bug, and the November notice lists its own steps.
What should Entra admins do now?
- Check Azure Service Health for the Connect Health notice, tenant by tenant if you are an MSP.
- Tell your security team to expect targeted phishing and social engineering aimed at the exposed administrator and technical contact addresses.
- Make sure privileged accounts use phishing-resistant multifactor authentication.
- Review your Connect Health configurations.
- Examine Entra audit and sign-in logs for unusual activity.
- Run Microsoft's PowerShell script at aka.ms/ConnectHealth/scripts if you want to see which types of tenant metadata could have been exposed. It shows your current values and not what the attackers accessed.
- Install nothing. Microsoft says no software update or other remediation is needed to close the flaw, so these steps are precautions.
Sources: BleepingComputer, Cymulate, Cyber Security News, Ma-no.org. Related: WorkOS breach: indicators to check, DigiCert breach: questions for your vendors.
Sources
- BleepingComputer: Microsoft Entra Connect Health flaw exploited to steal tenant data
- Cymulate Research Lab: Read-Only Is a Lie: An Entra ID Privilege Escalation
- Cyber Security News: Hackers Exploit Microsoft Entra Connect Health Flaw to Access Admin Emails and Organization Data
- Ma-no.org: Microsoft confirms Entra Connect Health metadata was stolen