Microsoft has patched a serious vulnerability in Entra Connect Health that allowed hackers to read administrators’ and technical contact email addresses, along with sensitive configuration data from impacted tenants. The flaw, residing in Entra’s cloud monitoring API, did not permit access to inboxes or email content, but gave unauthorized visibility into directory sync settings and organization details. The issue was fixed on November 19, 2026.
What Went Wrong
The vulnerability started on July 23 and remained undetected until November 9. Based on Microsoft’s investigation, attackers used the API to pull tenant information—such as tenant ID, display name, initial domain, country, licensing tier, whether directory sync was enabled, and when it last occurred—without requiring admin privileges. Entra Connect Health allows organizations to monitor directory sync errors, alerts, and performance for on-premises identity services.
Crucially, the exploit did not leak passwords, password hashes, valid cryptographic keys, Azure subscription info, or specific structuring details about local Active Directory servers. A piece of exposed data was an expired certificate used for registering monitoring agents to an internal Microsoft service that was discontinued in late 2024.
Scope & Timeline
Microsoft confirmed that data was accessed sometime between the introduction of the flaw on July 23 and the fix deployed on November 19. The internal audit identified unauthorized reads of tenant records on or before November 20. However, Microsoft didn’t specify who carried out the attack, how many organizations were affected, or when the unauthorized access began.
Although this incident involved confirmed read-only access, it differs from prior Entra ID issues that allowed attackers to use elevated privileges such as Global Administrator rights. Here, the privilege threshold was lower, but the results—exposure of organization configuration and contact information—still pose serious risks.
Recommended Actions
To reduce exposure to the fallout, Microsoft urged all customers to double-check their technical contact info, enforce phishing-resistant multifactor authentication for privileged users, and leverage Privileged Identity Management where possible. Admins are also advised to audit API usage, scan their Entra Connect Health settings, and review log activities—especially any irregular admin behavior.
Using Microsoft’s read-only GetTenant PowerShell script can help organizations see the kinds of data exposed, though it can’t reconstruct which exact records were accessed in the breach. Also worth checking: whether alerts about this advisory show up in Azure Service Health for specific tenants.
Security experts warn that simply knowing who administrates a directory and which domain is used can greatly aid phishing or social engineering attacks. While there are no confirmed phishing campaigns linked to this incident, past attacks indicate that the exposure of contact names and domains heightens risk significantly.
What this means going forward: even when a vulnerability offers only read-only access, the damage is often underappreciated. This case reaffirms that what may seem like “minor” exposure—admin emails, domain names—can be the foothold attackers need. The breach underlines the urgency of zero-trust principles, beyond just protecting credentials. Watching how Entra adjusts trust boundaries—and whether Microsoft enhances monitoring and response time—will be critical.