Microsoft Entra Connect Health has become the latest Microsoft service to face a security incident after attackers exploited a vulnerability that exposed sensitive tenant information belonging to affected organizations. Microsoft has confirmed that unauthorized individuals gained read only access to certain customer metadata, including administrator email addresses, tenant identification details and information about directory synchronization.
The incident highlights the security risks associated with cloud based identity management services, particularly when they are connected to an organization’s internal infrastructure. Although Microsoft says the vulnerability did not expose passwords, authentication tokens or valid cryptographic keys, the stolen information could still provide attackers with useful intelligence for launching targeted phishing and social engineering campaigns.
According to a security notification sent to administrators on November 20, 2026, Microsoft discovered the vulnerability in the Entra Connect Health API on November 9. The investigation found that the issue had been present since July 23, 2026.
Microsoft completed its investigation on November 20 and confirmed that unauthorized parties had accessed tenant level metadata associated with affected organizations. The company said it had found no evidence of unauthorized changes to customer configurations.
Attackers Exploited a Vulnerability in Microsoft’s Entra Connect Health API
Microsoft Entra Connect Health is a cloud based monitoring service designed to help administrators oversee the performance, availability and operational health of their on premises identity infrastructure.
The service allows organizations to monitor identity synchronization, receive alerts and identify potential problems through the Microsoft Entra admin center. This makes it an important part of identity management for businesses that rely on a combination of on premises Active Directory environments and Microsoft’s cloud services.
The security issue affected the API used by Entra Connect Health. Microsoft said the vulnerability was introduced on July 23, 2026, but was not discovered until November 9.
Following its discovery, the company investigated the incident and reviewed available telemetry to determine whether attackers had accessed customer information.
The investigation confirmed that unauthorized parties had obtained read only access to tenant level metadata. Microsoft also acknowledged that the vulnerability could potentially have allowed attackers to modify Connect Health monitoring configurations.
However, the company found no evidence that unauthorized configuration changes had actually taken place.
Microsoft deployed a server side fix on November 19 to close the security gap and prevent further exploitation. Affected organizations subsequently received notifications through Azure Service Health.
What Information Was Exposed in the Security Incident?
Although the breach did not expose authentication credentials, the information accessed by attackers included several details that could be useful in identifying and targeting organizations.
Microsoft confirmed that the exposed data included email addresses associated with tenant technical contacts and administrator accounts. This is particularly concerning because attackers could use these addresses to create convincing phishing messages impersonating Microsoft support teams or other trusted service providers.
The exposed information also included tenant IDs, display names, initial domain names, country codes and regional details.
In addition, attackers could access information about Microsoft Entra licensing levels and directory synchronization status. This included whether directory synchronization was enabled and the timestamp of the most recent synchronization.
The breach also exposed Connect Health onboarding status and an expired certificate that had previously been used to register Connect Health agents with an internal Microsoft service.
Microsoft clarified that the certificate was no longer active. It had remained in Connect Health storage even though the internal service associated with it was decommissioned in late 2024. The API continued returning the expired certificate despite it no longer being used.
Importantly, Microsoft said the incident did not expose user passwords, password hashes, authentication tokens or valid cryptographic keys. Attackers also did not gain access to on premises server details, Active Directory topology information or Azure subscription data.
While these limitations reduce the immediate risk of account compromise, the exposed metadata could still help attackers understand an organization’s identity infrastructure and identify valuable administrative targets.
Microsoft Recommends Security Reviews and Phishing Protection
Microsoft says customers do not need to install software updates or perform additional remediation to address the vulnerability. The server side fix has already been deployed, and the company has notified organizations identified as affected.
However, administrators should not treat the incident as something that requires no further attention.
Microsoft recommends that affected organizations notify their security teams and remain alert for phishing attempts and social engineering campaigns. Since administrator email addresses and tenant information were exposed, attackers may use these details to make fraudulent communications appear more credible.
Organizations should also review their privileged account security policies and ensure that administrative accounts use phishing resistant multifactor authentication.
Security teams are advised to examine Microsoft Entra audit logs and sign in logs for suspicious activity. They should also review their Connect Health configurations to ensure that monitoring settings remain as expected.
Microsoft has additionally published a PowerShell script that allows administrators to inspect the types of tenant metadata that could have been exposed during the incident.
However, there is an important limitation. The script displays current configuration information rather than providing a historical record of the specific information accessed by attackers. Therefore, running it cannot independently establish exactly what data was viewed during the breach.
Microsoft Has Not Disclosed the Number of Affected Organizations
Microsoft has not revealed how many organizations were affected or identified the individuals or groups responsible for exploiting the vulnerability. The company has also not disclosed when the attacks first began.
Reports from administrators suggest that the incident may have affected multiple organizations. More than a dozen administrators reportedly confirmed receiving Microsoft’s security notification in an online discussion. Some managed service providers also said they received alerts for several customer tenants, with notifications arriving at different times.
When contacted about the incident, Microsoft confirmed that it had identified and addressed a security issue affecting Entra Connect Health. The company said it deployed a fix on November 19 and notified impacted customers through Azure Service Health.
Microsoft has not provided further technical details about the attackers or the full extent of the breach.
For organizations using Microsoft Entra Connect Health, the incident serves as a reminder that even metadata can become valuable to cybercriminals. Information such as administrator email addresses, tenant names, licensing details and synchronization status may not provide direct access to an organization’s systems, but it can help attackers build convincing and highly targeted campaigns.
The immediate vulnerability has been addressed, but affected organizations should continue monitoring their identity environments and strengthening protections around privileged accounts.
Follow TechBSB For More Updates
