Microsoft has confirmed a security breach involving its Entra Connect Health service, a cloud-based monitoring tool used by administrators to track the performance and health of on-premises identity infrastructure. The vulnerability, located within the Entra Connect Health API, allowed unauthorized parties to gain read-only access to specific tenant-level metadata. Microsoft identified the flaw on November 9, 2026, and determined that it had been present in the system since July 23 of the same year.
According to the official notification provided to affected organizations, the unauthorized access resulted in the exposure of several categories of sensitive information. This includes the email addresses of technical contacts and administrators, tenant IDs, display names, initial domain names, country codes, and regional information. Additionally, the breach exposed details regarding Entra license tiers, directory synchronization status, and the onboarding status of the Connect Health service. The API also returned an expired certificate that had been used to register Connect Health agents with an internal service decommissioned in 2024; Microsoft maintains that this certificate was no longer active or functional.
Microsoft concluded its investigation on November 20, 2026, and stated that there is no evidence that the attackers were able to modify any Connect Health monitoring configurations. The company explicitly confirmed that the vulnerability did not lead to the exposure of user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises Active Directory topology details, or Azure subscription information. While Microsoft has not disclosed the total number of affected organizations, reports from administrators and managed service providers indicate that the impact is widespread, with multiple notifications being sent to various tenants.
To mitigate the issue, Microsoft deployed a server-side fix on November 19, 2026, which effectively closed the vulnerability. The company noted that no software updates or manual remediation steps are required from customers to address the flaw itself. However, because administrator email addresses and tenant configuration details were exposed, Microsoft has advised organizations to remain vigilant against potential phishing and social-engineering campaigns that may leverage this information.
As a precautionary measure, Microsoft recommends that organizations ensure all privileged accounts are protected by phishing-resistant multifactor authentication. Administrators are also encouraged to conduct a thorough review of their Entra audit and sign-in logs to detect any suspicious activity that may have occurred during the period of exposure. To assist with internal assessments, the company has provided a PowerShell script that allows administrators to view the types of tenant metadata currently associated with their configurations, though it does not provide a historical record of what was accessed during the breach.
Microsoft has not released information regarding the identity of the threat actors responsible for the exploitation or the specific timeline of when the unauthorized access began. The company has declined to provide further technical details beyond the confirmation that the vulnerability was addressed and that affected parties have been notified through Azure Service Health. Organizations seeking further guidance are directed to the resources provided within their service health portals.





