Attackers exploited a flaw in the Microsoft Entra Connect Health application programming interface (API) to read administrator email addresses and tenant metadata, according to a Microsoft customer notification reported by BleepingComputer. Microsoft deployed a server-side fix on November 19, 2026, and says it has notified affected customers through Azure Service Health. Source
Microsoft says passwords and authentication tokens weren’t exposed. That isn’t an all-clear: the company warns that the exposed contact details and configuration information could be used in targeted phishing and social-engineering attempts. Source
Entra Connect Health is a cloud-based service for monitoring an organization’s locally hosted identity systems through the Microsoft Entra admin center. A tenant is an organization’s Microsoft Entra environment; its metadata includes identifiers, settings and status information. Source
What Microsoft says happened
According to the notification described by BleepingComputer, the vulnerability was introduced on July 23, 2026, detected on November 9 and fixed server-side on November 19. Microsoft concluded its investigation on November 20. Source
The flaw could have allowed changes to Connect Health monitoring configurations, according to BleepingComputer. Microsoft said in the notification quoted by the outlet: Source
“On 20 November 2026, we concluded our investigation and determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred. We did not identify any unauthorized configuration changes.” Source
Microsoft says the exposed information included:
- Email addresses for tenant technical contacts and administrator accounts.
- Tenant IDs, display names, initial domain names, country codes and regional information.
- Microsoft Entra license tiers and directory synchronization status, including whether synchronization was enabled and the time of the last synchronization.
- Connect Health onboarding status.
- An expired certificate previously used to register Connect Health agents with an internal Microsoft service decommissioned in late 2024. Source
Microsoft says the API continued returning the expired, unused certificate because it remained in Connect Health storage. Source
Beyond passwords and authentication tokens, Microsoft says the vulnerability did not expose password hashes, valid cryptographic keys, on-premises server or Active Directory topology details, or Azure subscription information. Source
No customer patch, but still some defensive homework
Microsoft’s notification says customers do not need to install software updates or perform other remediation to fix the vulnerability itself. Source
Microsoft recommends alerting security teams to the possibility of targeted phishing and social engineering involving the exposed email addresses and tenant information. It also advises organizations to ensure privileged accounts use phishing-resistant multifactor authentication, review Connect Health configurations, and examine Microsoft Entra audit and sign-in logs for suspicious activity. Source
As of BleepingComputer’s November 21 report, Microsoft had not disclosed how many tenants were affected, who exploited the flaw or when the attacks began. Source
Comments