Microsoft Confirms Unauthorized Access to Entra Connect Health Tenant Metadata

Summary
Microsoft confirmed unauthorized read-only access to Entra Connect Health tenant metadata and administrator emails. The API flaw was fixed server-side on November 19, 2026; the number of affected tenants was not disclosed.
Key points
- Microsoft says unauthorized callers accessed API responses containing tenant configuration metadata and technical contact and administrator email addresses.
- Exposed fields included tenant IDs, display names, initial domains, country codes, region scopes, license tiers, and directory synchronization timestamps.
- Microsoft's telemetry review confirmed read-only access and no unauthorized configuration changes; the number of affected tenants was not disclosed.
- The flaw was introduced on July 23, 2026, and Microsoft deployed a server-side fix on November 19, 2026. No administrator patch installation is required.
- Microsoft said the exposure did not include passwords, password hashes, authentication tokens, valid cryptographic keys, or on-premises server and Active Directory topology details.
- Administrators are advised to alert relevant contacts about targeted phishing, use phishing-resistant MFA and Privileged Identity Management, and review Azure Service Health notices and Entra audit logs.
Article Details
- Victim Organization
- Organizations using Microsoft Entra Connect Health; specific affected organizations were not disclosed.
- Incident Type
- Unauthorized read-only access to API responses, exposing tenant metadata and administrator contact details.
- Data Types Exposed
- Tenant technical-contact and administrator email addresses
- Tenant IDs, display names, initial domains, country codes, region scopes, license tiers, and directory synchronization timestamps
- An expired certificate returned in the pksCertificate field
- Affected Records
- Not disclosed
- Affected Data Size
- Not disclosed
- Operational Impact
- Microsoft confirmed unauthorized read-only access through telemetry logs. Investigators found no unauthorized configuration changes. The flaw was fixed server-side on November 19, 2026. Microsoft said passwords, password hashes, authentication tokens, valid cryptographic keys, and on-premises server and Active Directory topology details were not exposed.
- Ransom Or Extortion
- Unknown
- Claim Status
- confirmed
