Protect.Computer
NEWS

Microsoft Entra Connect Health Flaw Exposed Tenant Metadata

· 2 min read · Got hacked Identity theft
Microsoft Entra Connect Health Flaw Exposed Tenant Metadata

Microsoft is warning customers that attackers exploited a vulnerability in the Microsoft Entra Connect Health API and gained unauthorized read-only access to tenant-level metadata, BleepingComputer reports. Entra Connect Health is a cloud service that lets administrators monitor the health and alerts of their on-premises identity infrastructure from the Entra admin center. According to a security notification sent to administrators and shared on Reddit, Microsoft found the flaw on November 9, 2026, and says it was introduced on July 23. It deployed a server-side fix on November 19 and concluded its investigation on November 20, finding unauthorized read-only access but no unauthorized configuration changes.

Microsoft says the exposed data included email addresses for tenant technical contacts and administrator accounts; tenant IDs, display names, initial domain names and country and region codes; Entra license tiers and directory-synchronization status (including whether sync was enabled and when it last ran); Connect Health onboarding status; and an expired certificate that was once used to register Connect Health agents with an internal Microsoft service decommissioned in late 2024. The notification says passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, and Azure subscription information were not exposed. Microsoft has not said who exploited the flaw, how many tenants were affected, or when the attacks began, though BleepingComputer notes more than a dozen administrators reported getting the notice and some managed service providers received one for several customer tenants.

How to check if you’re affected

Affected products are Microsoft Entra Connect Health tenants that received Microsoft’s notification; according to Microsoft’s spokesperson, impacted customers were notified through Azure Service Health. Microsoft’s notice says no software update or other customer remediation is required to close the flaw itself. The steps below are what the notification recommends, as relayed by BleepingComputer; we could not read the notice or Reddit thread directly.

  • Warn your security team about phishing. The exposed administrator and technical-contact email addresses and tenant details could be used for targeted phishing and social engineering.
  • Use phishing-resistant multifactor authentication on privileged accounts.
  • Review your Connect Health configuration and the Microsoft Entra audit and sign-in logs for suspicious activity.
  • Run Microsoft’s PowerShell script (linked below) to see the types of tenant metadata that could have been exposed. BleepingComputer notes it displays your current configuration values, not what was actually accessed in the breach.

Sources

Related reading