Microsoft is notifying organizations that attackers exploited a vulnerability in its Microsoft Entra Connect Health service to gain unauthorized read-only access to tenant-level metadata, including the email addresses of administrator accounts and technical contacts, according to a customer notification reported by BleepingComputer.
The company said it deployed a server-side fix on November 19, 2026, and that customers do not need to install any software update. Microsoft has not said how many tenants were affected, when exploitation began or who was responsible, and no CVE identifier has been published for the issue.
What happened
According to the notification, Microsoft discovered the flaw in the Entra Connect Health API on November 9, 2026. BleepingComputer reports that the bug was introduced on July 23, meaning the vulnerable code appears to have been live for several months before it was found. After deploying the fix, Microsoft reviewed telemetry for unauthorized API calls and concluded its investigation on November 20, at which point it began notifying affected organizations through Azure Service Health.
Microsoft told customers it had confirmed unauthorized read-only access to tenant metadata. The company said the flaw could potentially also have allowed changes to Connect Health monitoring configurations, but stated: “We did not identify any unauthorized configuration changes.”
A Microsoft spokesperson confirmed the issue to BleepingComputer and said impacted customers had been notified with guidance, but declined to provide further details. Microsoft has not published a public security advisory for the incident at the time of writing.
Who is affected
The notification is going to organizations whose tenants use Entra Connect Health, the service that monitors hybrid identity components such as Entra Connect sync servers. More than a dozen administrators reported receiving the notice on the r/sysadmin forum, and some managed service providers said they had received notices for multiple customer tenants, according to BleepingComputer.
According to Microsoft, the data that could be read included:
- Email addresses of tenant technical contacts and administrator accounts
- Tenant IDs, display names, initial domain names, country codes and regional information
- Microsoft Entra license tier and directory synchronization status, including the last sync timestamp
- Connect Health onboarding status
- An expired certificate formerly used to register Connect Health agents with an internal Microsoft service that was decommissioned in late 2024
Microsoft said the flaw did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server or Active Directory topology, or Azure subscription information.
Severity and exploitation
This is a confirmed exploitation of a cloud service flaw rather than a vulnerability in customer-managed software, so there is nothing for defenders to patch. The direct impact is limited to metadata, but the exposed information is useful for reconnaissance: verified administrator email addresses combined with tenant names, domains and licensing details give an attacker a ready-made target list for credential phishing, help desk impersonation and MFA fatigue campaigns against the most privileged identities in an organization.
The number of affected tenants, the identity of the attacker and the start date of exploitation have not been disclosed.
What defenders should do now
- Check Azure Service Health and Entra admin center notifications for a security notice about Entra Connect Health, including for every customer tenant if you are an MSP.
- Warn administrators and technical contacts listed on affected tenants to expect targeted phishing and social engineering that references accurate tenant details.
- Require phishing-resistant MFA, such as FIDO2 security keys or Windows Hello for Business, on all privileged accounts, as Microsoft recommends.
- Review Microsoft Entra audit logs and sign-in logs for suspicious activity against administrator accounts, including unusual sign-in locations and new MFA method registrations.
- Review Entra Connect Health configurations for unexpected changes, even though Microsoft reports finding none.
- Run the PowerShell script Microsoft published at
https://aka.ms/ConnectHealth/scriptsto see which metadata types apply to your tenant, noting that it shows current values rather than the data actually accessed.
SCVM analysis
The incident is a reminder that identity providers are a dependency defenders cannot patch themselves. A bug that sat in a monitoring API for months handed an unknown party verified contact details for the people who hold the keys to Entra tenants. That is low-volume data with high targeting value.
The practical response is to treat administrator email addresses as known to attackers and harden accordingly: phishing-resistant MFA, conditional access restricting admin sign-ins to managed devices, and help desk procedures that do not reset admin credentials on the strength of tenant details a caller can recite. The lack of a public advisory, a CVE or tenant counts also leaves customers dependent on in-portal notices, so organizations should ensure Service Health alerts reach a monitored security mailbox rather than a single administrator inbox.
Sources
About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

