Felix ReportIndependent Reporting and News

Entra Connect Health notice separates exposed admin data from stolen credentials

Conceptual illustration of administrative contact cards beside a secured cloud-shaped enclosure.

Microsoft has confirmed a security issue affecting Entra Connect Health, with affected customers notified through Azure Service Health. The public notice describes access to administrator contacts and tenant metadata, while excluding passwords, authentication tokens and valid cryptographic keys from the exposed information.

Lawrence Abrams reported Microsoft's confirmation for BleepingComputer on November 21. A customer had also posted the notice in Reddit's sysadmin community. That public copy offers detail about the incident; an organization should check its own advisory directly in Azure Service Health to establish whether its tenant is affected.

What the notice distinguishes

The notice says Microsoft detected the API vulnerability on November 9, fixed it on November 19 and concluded its investigation on November 20. It reports unauthorized read-only access and says investigators did not identify unauthorized configuration changes.

The listed fields include technical-contact and administrator email addresses, tenant identifiers, domain and regional information, license tier, synchronization status and Connect Health onboarding status. A legacy certificate associated with a service retired in late 2024 also appeared in the API response. The notice describes that certificate as expired and no longer used.

This distinction matters: configuration information can give a convincing message more context without giving its sender a working password. The notice therefore recommends attention to targeted phishing while explicitly ruling out several categories of credentials and on-premises topology details. It does not describe every Entra service or every Microsoft customer as compromised.

Check the advisory, then the relevant controls

The >publicly posted notice (opens in a new tab) directs customers to sign into the Azure portal themselves and check the Security Advisory. It says the flaw was repaired on the service side, with no customer software update required to fix this particular vulnerability.

Its precautionary steps include alerting security staff, checking notification contacts, using phishing-resistant multifactor authentication for privileged accounts, reviewing Connect Health settings and examining relevant audit and sign-in logs. Those precautions address potential follow-on risk; they are not evidence that additional compromise has occurred.

A snapshot is not an exposure log

The notice describes a read-only GetTenant script that shows current metadata. It explicitly warns that today's values may differ from those present during the exposure. Running it would therefore not reconstruct precisely what an intruder saw. We have not run that script or inspected any customer's tenant.

The number of affected organizations, the attackers' identity and the beginning of exploitation were not established in the public material reviewed. Administrators' reports can identify a problem worth checking, but counting comments cannot measure the incident's reach.