Microsoft alerted customers after attackers exploited an API bug in Entra Connect Health to steal tenant setup details and admin emails. The company found the security flaw on November 9, 2026, following months of exposure after a code change introduced the hole to the service on July 23. Microsoft deployed a cloud fix on November 19 to block rogue API queries before finishing its review. While the incident exposed contact records for technical staff, Microsoft confirmed that user passwords, password hashes, and cryptographic keys stayed safe [1].
Timeline of the Entra Connect Health Bug
Microsoft Entra Connect Health helps IT staff oversee on-premises identity setups through the central Microsoft Entra admin center. The tool watches server health, sync errors, and alerts on local domain environments. It monitors domain controllers and tracks synchronization performance between local networks and cloud directories. Security reporter Lawrence Abrams at BleepingComputer reported that attackers found a bug in the cloud API, allowing rogue parties to view tenant setup details and service logs without approval [1].
The software flaw entered the Entra Connect Health service on July 23, but Microsoft defense teams did not spot the bug until November 9, 2026, leaving cloud configurations exposed to rogue queries for months. Intruders targeted tenant settings. Microsoft opened an urgent probe to learn whether attackers manipulated alerts or disrupted health reporting. Engineers checked telemetry. Their analysis traced every query sent to the broken endpoint, proving that intruders only read tenant metadata and made no setup changes before Microsoft deployed a server patch to protect customers [1].
Microsoft confirmed that the intrusion produced read-only access. “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,” Microsoft said in the notification [1]. The company told Microsoft Entra customers that their local identity sync profiles remained unaltered and that attackers made no unauthorized adjustments to monitoring thresholds.
Stolen Directory Records
Microsoft revealed that the breach exposed technical contact email addresses and account names belonging to tenant admins in Microsoft Entra. Intruders also took tenant IDs, display names, first domain names, country codes, and regional details. Bad actors gained staff rosters. By collecting this data, intruders can map out company setups and identify the exact Microsoft Entra admins who manage identity systems for targeted accounts [1].
Intruders also accessed license tiers. The stolen data showed whether directory sync was enabled, displayed the last synchronization timestamp, and exposed the onboarding status of Connect Health agents operating on customer networks. Storage systems also returned an expired certificate tied to a Microsoft service decommissioned in late 2024. Microsoft said the certificate was no longer in use, but it stayed in storage and passed through the broken API when attackers queried tenant properties before engineers removed the credential [1]. Old data stayed exposed.
The stolen records do not allow direct sign-ins to Microsoft Entra. Adversaries can still see which Microsoft cloud license tier a company pays for and whether its identity data syncs with local Active Directory domain controllers. Knowing directory synchronization schedules and tenant domain names gives attackers valuable operational context. That insight helps attackers prepare spear-phishing attacks against company staff [1].
Data That Stayed Safe
Core login assets stayed safe. Microsoft stated that the flaw did not expose user passwords, password hashes, or valid auth tokens. Cryptographic keys used to secure sessions were completely protected, and because the broken API only handled monitoring metadata, core authentication stores remained isolated from outside intruders [1].
The security flaw also spared on-premises servers and Active Directory topology details that map out local domain controllers, server hostnames, and company network structures. Intruders saw no forest links, user password hashes, or authentication tokens. Azure subscription data and billing records also stayed inaccessible to intruders during the incident [1].

Authentication systems held. Because login secrets stayed secure, attackers can’t forge tokens or decrypt network traffic, and the barrier between Connect Health telemetry and Active Directory databases kept domain controllers isolated from outside tampering. Customer tenants faced no credential theft [1].
Alerts Sent to Admins
Engineers resolved the flaw on November 19, 2026, deploying a cloud update to prevent further exploitation of the Microsoft Entra Connect Health API. Microsoft reviewed system telemetry to find unauthorized API calls affecting customer tenants. Admins installed nothing locally. Because Microsoft applied the patch to its own servers, the update immediately cut off rogue access to tenant metadata across all customer environments [1].
Microsoft finished its inquiry on November 20 and alerted affected tenants through Azure Service Health. Over a dozen admins on Reddit reported getting notices. Several managed service providers (MSPs) that oversee multiple client environments reported receiving alerts for several customer tenants, with one admin on Reddit noting that emails arrived hours apart [1].
Microsoft declined to say who launched the attacks or when the intrusions began. “We 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. We deployed a fix on November 19, 2026, and have notified impacted customers through Azure Service Health, providing guidance and support,” a Microsoft spokesperson told BleepingComputer [1]. The company gave no extra details to reporters.
Security Steps for Entra Connect Health Admins
Microsoft said customers do not need to install patches, but warned admins to watch for phishing. Stolen emails feed phishing. To stop account takeovers, Microsoft urged organizations to enforce phishing-resistant multifactor authentication across all privileged admin accounts to protect identity systems from stolen contact data and social engineering attacks [1].
Microsoft released a PowerShell script (available at https://aka.ms/ConnectHealth/scripts) to show what categories of metadata were exposed. The script displays current settings rather than historical records stolen during the breach [1]. The script helps administrators identify exposed tenant properties without requiring remediation. The incident shows how cloud health tools face specific risks, unlike backup software breaches seen when ConnectWise cut cloud backup after hackers breached Microsoft 365 customer tenants.
Security teams should check their Microsoft Entra Connect Health settings and inspect Microsoft Entra sign-in and audit logs to spot unusual account events. Log reviews catch intrusions early. Routine inspection of identity telemetry lets teams protect hybrid setups and block follow-up attacks before adversaries can exploit stolen administrative contacts [1]. Microsoft advised administrators to keep monitoring logs while enforcing strong authentication controls.
- ONLINE NEWS Abrams, L. (2026, November 21). Microsoft Entra Connect Health flaw exploited to steal tenant data. BleepingComputer. [Article Link]