Microsoft Entra Connect Health API flaw gave unauthorised parties read access to tenant administrator emails and metadata
TLDR
- Microsoft told customers an Entra Connect Health API flaw allowed unauthorised read-only access to tenant metadata, BleepingComputer reports.1
- Exposed data included administrator and technical contact email addresses; Microsoft says passwords, tokens and valid keys were not exposed.12
- Microsoft says it deployed a server-side fix on 19 November and that customers need install no update.12
BleepingComputer reports that Microsoft is warning organisations of a data breach after attackers exploited a vulnerability in its Entra Connect Health service to gain unauthorised access to administrator email addresses and tenant configuration information.1 Connect Health is a cloud-based service that lets administrators monitor the health, performance and alerts of their on-premises identity infrastructure through the Microsoft Entra admin centre.1 According to a security notification sent to administrators on 20 November and shared on Reddit, Microsoft found the vulnerability in the Connect Health API on 9 November 2026, after it was introduced on 23 July.1 Microsoft says it concluded its investigation on 20 November and determined that unauthorised read-only access to tenant-level metadata had occurred, and that it identified no unauthorised configuration changes.1 Neowin gives the same timeline, and All About Security says Microsoft confirmed the access from internal telemetry logs.23
The notification lists the exposed information as email addresses of tenant technical contacts and administrator accounts; tenant IDs, display names, initial domain names, country codes and regional information; Entra licence tiers and directory synchronisation status, including the last synchronisation timestamp; and Connect Health onboarding status.1 It also lists an expired certificate once used to register Connect Health agents with a Microsoft internal service that was decommissioned in late 2024, which BleepingComputer says was no longer in use but remained in Connect Health storage and was still returned by the API.1 All About Security says the certificate sat in the pksCertificate field and was served by the GetTenant API.3 Microsoft says the flaw did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, or Azure subscription information.1 Microsoft's published reference scripts for Connect Health include GetTenant.ps1, which returns tenant-level Connect Health configuration as JSON, and its README says the scripts make read-only requests and change no configuration.4 BleepingComputer says the script Microsoft published displays current configuration values rather than the information that was accessed during the breach.1
Microsoft has not disclosed how many tenants were affected, who exploited the flaw, or when the attacks began, BleepingComputer reports.1 More than a dozen administrators said in the Reddit thread that they had received the notification, and some managed service providers reported notices covering several customer tenants.1 All About Security says confirmed unauthorised read access applied only to tenants that received a direct notification in Azure Service Health.3 In a statement to BleepingComputer, a Microsoft spokesperson said the issue could have resulted in unauthorised access to tenant-level contact and configuration metadata, that a fix was deployed on 19 November and that affected customers were notified through Azure Service Health, and declined to give further details.1 BleepingComputer's headline says the flaw was exploited, and the customer notification it quotes says access had occurred.1
Microsoft says no software update or other customer remediation is needed.12 It recommends alerting security teams to possible targeted phishing and social-engineering attacks against the exposed administrator addresses, using phishing-resistant multifactor authentication on privileged accounts, reviewing Connect Health configurations, and checking Entra audit and sign-in logs for suspicious activity.12 All About Security adds that Microsoft recommends Privileged Identity Management for just-in-time activation and signing in to the Azure portal directly rather than following email links to check Azure Service Health, and says it never asks for passwords, sign-in codes or secrets by email.3
Why it matters: Microsoft advises organisations to watch for targeted phishing aimed at the exposed administrator addresses, and it has not said how many tenants were affected.1
Sources
- Microsoft Entra Connect Health flaw exploited to steal tenant data (BleepingComputer)
- After outage, Microsoft confirms another July bug that led to Entra data breach (Neowin)
- Microsoft Entra Connect Health: Sicherheitslücke legte Mandanten-Metadaten offen (All About Security)
- ConnectHealth reference scripts (AzureAD/EntraIDGovernance) (Microsoft (GitHub))