A vulnerability in Microsoft Entra Connect Health, a cloud-based service for monitoring on-premises identity infrastructure, was exploited to breach administrator credentials and tenant metadata across multiple organizations. The company notified affected customers of the incident, which involved unauthorized read-only access to sensitive organizational information.
Microsoft Entra Connect Health provides administrators with visibility into the health, performance, and operational alerts of their on-premises identity systems through the Microsoft Entra admin center. The flaw was first introduced on July 23 and discovered on November 9, 2026, according to security notifications sent to administrators.

An investigation concluded on November 20 determined that unauthorized parties had accessed tenant-level metadata associated with affected organizations. Microsoft stated in its notification: "On 20 November 2026, we concluded our investigation and determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred. We did not identify any unauthorized configuration changes."
What was exposed
The breach exposed several categories of sensitive information tied to affected tenants:
- Email addresses of tenant technical contacts and administrator accounts
- Tenant IDs, display names, initial domain names, country codes, and regional information
- Microsoft Entra license tiers and directory synchronization status, including whether synchronization was enabled and the last synchronization timestamp
- Connect Health onboarding status
- An expired certificate previously used to register Connect Health agents with a Microsoft internal service that was decommissioned in late 2024
The expired certificate remained in Connect Health storage and continued to be returned by the API despite no longer being in use. Microsoft confirmed that the vulnerability did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, or Azure subscription information.
Response and remediation
Microsoft deployed a server-side fix on November 19 to stop further exploitation and analyzed telemetry to identify unauthorized API calls affecting customers. The company completed its investigation on November 20 and began notifying impacted organizations. No software updates or customer remediation are required to address the vulnerability.
The company recommends that organizations take several precautions in response to the exposure. These include alerting security teams to potential targeted phishing and social-engineering attacks that could leverage the exposed administrator email addresses and tenant information. Organizations should also ensure privileged accounts use phishing-resistant multifactor authentication, review their Connect Health configurations, and examine Microsoft Entra audit and sign-in logs for suspicious activity.
Microsoft published a PowerShell script at https://aka.ms/ConnectHealth/scripts that allows administrators to view the types of tenant metadata that could have been exposed. The script displays current configuration values rather than the information that was accessed during the breach.
Scope and disclosure gaps
Microsoft has not disclosed the total number of organizations impacted by the vulnerability, though more than a dozen administrators reported receiving notifications in discussions on Reddit. Some managed service providers also reported receiving notifications for multiple customer tenants, with notifications arriving hours apart.
The company has not revealed who exploited the vulnerability, how many tenants were affected, or when attacks first began. When contacted by BleepingComputer, a Microsoft spokesperson confirmed the fix and customer notifications: "We identified and addressed a security issue affecting Microsoft Entra Connect Health that could have resulted in unauthorized access to tenant-level contact and configuration metadata. We deployed a fix on November 19, 2026, and have notified impacted customers through Azure Service Health, providing guidance and support." Microsoft declined to provide additional details about the breach.