Microsoft says it fixed an Entra Connect Health flaw on 19 November and notified impacted customers after unauthorised read-only access to tenant-level metadata, including administrator email addresses, according to BleepingComputer
Microsoft told BleepingComputer it "identified and addressed a security issue affecting Microsoft Entra Connect Health that could have resulted in unauthorized access to tenant-level contact and configuration metadata", deployed a fix on November 19, 2026, and notified impacted customers through Azure Service Health (source: BleepingComputer).
In a notification to admins quoted by BleepingComputer, Microsoft said that on 20 November 2026 it concluded its investigation and "determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred" and that it "did not identify any unauthorized configuration changes"; according to BleepingComputer, the notification says the vulnerability in the Connect Health API was discovered on 9 November after being introduced on 23 July.
According to BleepingComputer, Microsoft says the exposed information included email addresses of tenant technical contacts and administrator accounts, tenant IDs, display names, initial domain names, country codes and regional information, Entra license tiers and directory synchronisation status, Connect Health onboarding status, and an expired certificate previously used to register Connect Health agents with an internal service decommissioned in late 2024; Microsoft says user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details and Azure subscription information were not exposed (source: BleepingComputer).
Microsoft has not disclosed how many organisations were impacted or who exploited the vulnerability, according to BleepingComputer.
- Product
- Microsoft Entra Connect Health (cloud monitoring service for on-premises identity infrastructure) — Connect Health API
- Versions
- n/a — cloud service; Microsoft deployed a server-side fix on 19 Nov 2026 (according to BleepingComputer)
- Exploited in Australia?
- unknown
- Patch to
- No software updates or other customer remediation are required, according to Microsoft's notification as reported by BleepingComputer. Microsoft recommends alerting security teams to potential targeted phishing and social-engineering attacks, ensuring privileged accounts use phishing-resistant MFA, reviewing Connect Health configurations, and examining Microsoft Entra audit and sign-in logs; its PowerShell script at https://aka.ms/ConnectHealth/scripts shows current configuration values rather than the information that was accessed (source: BleepingComputer).
