TL;DR
A recent Microsoft Entra Connect Health exposure allowed unauthorized parties to read tenant metadata and administrator email addresses. The API vulnerability remained active from July 23, 2026, until Microsoft patched it on November 19, 2026. Fortunately, the incident did not expose passwords, active cryptographic keys, or authentication tokens.
What was exposed
Microsoft confirmed that unauthorized callers accessed API responses containing tenant-level configuration metadata and contact details. Specifically, the leaked fields included email addresses for each tenant’s technical contact and administrator accounts. The API responses also revealed tenant IDs, display names, initial domains, country codes, region scopes, license tiers, and directory synchronization timestamps.
Additionally, the API returned an expired certificate under the pksCertificate field. Microsoft noted, “The certificate poses no risk and is no longer used by that service; the expired certificate had not been removed from Connect Health storage and continued to be included in the GetTenant API response.” Importantly, the company stated, “This vulnerability did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, or on-premises server and Active Directory topology details.”
Confirmed scope vs. undisclosed counts
Microsoft verified unauthorized read-only access through internal telemetry logs, though it has not disclosed how many tenants were affected. Investigators also confirmed that attackers made no unauthorized configuration changes.
How it happened
The Entra Connect Health exposure stemmed from a flaw introduced into the service API on July 23, 2026. According to the Microsoft security notification shared by administrators on Reddit, engineers discovered the issue months later. Microsoft wrote, “On 9 November 2026, we detected a vulnerability in the Microsoft Entra Connect Health API that was introduced on 23 July 2026.”
While the bug theoretically allowed configuration edits, forensic logs showed only read-only activity. Meanwhile, security researcher Dave Kennedy highlighted the advisory on X as enterprise defenders reviewed their hybrid identity logs.
Who is affected
This Entra Connect Health exposure impacts organizations using Microsoft Entra Connect Health to monitor on-premises identity infrastructure. Only tenants that received a direct advisory notice in Azure Service Health experienced confirmed unauthorized read activity.
What affected people should do
Administrators do not need to install patches because Microsoft resolved the API flaw on the server side. However, security teams should warn technical contacts and Global Administrators about targeted phishing emails referencing Microsoft Entra. Organizations should also enforce phishing-resistant multi-factor authentication and Privileged Identity Management for privileged accounts.
Next, defenders can run Microsoft’s read-only GetTenant PowerShell script to inspect current metadata fields. Finally, administrators should sign in directly to the Azure Portal to verify the notice under Azure Service Health and review Entra audit logs.
Company response
Microsoft deployed a service-side fix on November 19, 2026, to block further unauthorized API queries. By November 20, 2026, security investigators finished reviewing telemetry and notified impacted organizations. The company also released PowerShell inspection scripts to help administrators audit their exposed metadata fields.
Support Our Threat Intelligence
Find our threat intelligence and malware analysis helpful? Support our work today and unlock a 100% ad-free reading experience!