NEWS

Microsoft Entra Connect Health Flaw Exploited to Steal Tenant Metadata

Microsoft says attackers abused an Entra Connect Health API flaw for read-only access to admin emails and tenant details. A server-side fix shipped Nov 19.

Dylan H.

News Desk

November 21, 2026
2 min read
Microsoft Entra Connect Health Flaw Exploited to Steal Tenant Metadata

Overview

Microsoft is notifying customers that attackers exploited a vulnerability in the Microsoft Entra Connect Health service to gain unauthorized, read-only access to tenant-level metadata, according to BleepingComputer's report on Nov 21, 2026. No CVE identifier has been published.

Timeline

  • Jul 23: Microsoft says the flaw was introduced.
  • Nov 9: Microsoft discovered it.
  • Nov 19: A server-side fix was deployed.
  • Nov 20: The investigation concluded and customer notifications began through Azure Service Health.

What was exposed

Microsoft says the accessed data included:

  • Email addresses of tenant technical contacts and administrators
  • Tenant IDs, display names, initial domain names, country codes and regional information
  • Entra license tiers and directory sync status, including the last sync time
  • Connect Health onboarding status
  • An expired certificate once used to register Connect Health agents with a decommissioned internal service

Microsoft says passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology, and Azure subscription information were not exposed. It found no unauthorized configuration changes.

Scope

Microsoft has not said how many tenants were affected, who exploited the flaw or when attacks began. More than a dozen administrators reported receiving notices, and some managed service providers were notified about several tenants. Microsoft also published a PowerShell script (aka.ms/ConnectHealth/scripts), but it shows current configuration values rather than the data accessed.

What to do

No customer software update is required. Microsoft's data is low-sensitivity on its own, but the exposed admin emails and tenant details suit targeted phishing. Sensible steps:

  • Warn administrators and security teams to expect convincing social engineering that references their tenant.
  • Require phishing-resistant MFA for privileged accounts.
  • Review Entra Connect Health configuration.
  • Check Entra audit and sign-in logs for suspicious activity.
  • Check Azure Service Health for a notice, including for tenants you manage for clients.

Sources