Microsoft has told customers that a flaw in its Entra Connect Health service gave outsiders “unauthorized read-only access to tenant-level metadata,” including administrator email addresses, BleepingComputer reported on 21 November. The flaw was introduced on 23 July 2026 and detected on 9 November, so it went unnoticed for 109 days, by our arithmetic.
A Microsoft spokesperson said: “We deployed a fix on November 19, 2026, and have notified impacted customers through Azure Service Health.” Microsoft has not said how many organisations were affected or who exploited the flaw.
Entra is Microsoft’s identity service, the system companies use to sign staff in to Microsoft 365 and other apps. Our Microsoft stock page tracks the company’s price and key dates.
Business Pill · Least Privilege
An evergreen Business Engineer explainer. It teaches the general idea only and does not discuss this incident.
The key insight: Microsoft says a flaw in Entra Connect Health, introduced on 23 July and detected on 9 November 2026, let outsiders read tenant metadata, including administrator email addresses; passwords and tokens were not exposed, per Microsoft.
What Was Exposed
Connect Health is a monitoring tool that reports on how a company’s own servers sync with Entra. According to Microsoft’s notice as reported by BleepingComputer, the flaw sat in the Connect Health API, the interface that returns that monitoring data.
The data exposed included email addresses for tenants’ technical contacts and administrator accounts, tenant IDs, display names, initial domain names, country and regional information, Entra licence tiers, directory sync status and Connect Health onboarding status, BleepingComputer reported. It also included an expired certificate that was no longer in use but was still returned by the API.

What Microsoft Says Was Not Exposed
Microsoft’s notice says the flaw “did not expose user passwords, password hashes, authentication tokens”, SecurityOnline reported. BleepingComputer adds that valid cryptographic keys, on-premises server and Active Directory details and Azure subscription information were also not exposed, per Microsoft, and quotes the notice: “We did not identify any unauthorized configuration changes.”
Only tenants that “received a direct advisory notice in Azure Service Health” had confirmed unauthorized read activity, SecurityOnline reported. More than a dozen administrators said on Reddit that they had received the notice, and some IT service firms reported notices for several client tenants, according to BleepingComputer.
109 Days Undetected, 10 Days to Fix
By our arithmetic, the flaw was live for 109 days before Microsoft detected it on 9 November. The fix followed 10 days later, on 19 November, and Microsoft says it began notifying affected customers on 20 November. That is 120 days from the flaw’s introduction to the first notices.
Why It Matters
Administrator email addresses are a target in themselves: Microsoft’s own advice is to watch for targeted phishing and social engineering that uses the exposed details, to require phishing-resistant multifactor sign-in for privileged accounts, and to check Entra audit and sign-in logs, BleepingComputer reported. Microsoft says no software update is needed.
It is the latest in a run of supplier-side incidents we have covered this month, including the latent bug behind a 36-hour Microsoft 365 outage, Infoblox’s vendor breach, the Optimizely script attack and the European Commission intrusion.
The Structural Read
As we read it, the exposed data is the raw material for phishing: who the administrators are and how to reach them.
As we read it, the gap between introduction and detection is the number to watch in Microsoft’s follow-up, not the fix time.
Microsoft spokesperson, via BleepingComputer, 21 Nov 2026
“We deployed a fix on November 19, 2026, and have notified impacted customers through Azure Service Health.”
Three Implications
FOR IT TEAMS Microsoft advises watching for targeted phishing aimed at administrator addresses.
FOR MICROSOFT CUSTOMERS Only tenants that received an Azure Service Health notice had confirmed read activity, per Microsoft.
FOR SECURITY BUYERS The flaw was in a monitoring tool, a supplier-side layer companies do not run themselves.
What Is Not Established
Microsoft has not disclosed how many tenants were affected, when exploitation began or who was behind it, and its notice went privately to customers rather than to a public advisory page. Microsoft published read-only PowerShell scripts that show the kinds of metadata the API returns, though BleepingComputer notes they display current values, not the data that was accessed.
The Bottom Line
Microsoft says a Connect Health flaw, undetected for 109 days, let outsiders read tenant metadata, including administrator email addresses, and that passwords and tokens were not exposed. The unanswered questions are how many companies were affected and who took the data. This is not investment advice.
97,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.
A note on sourcing. Microsoft sent its notice privately to affected customers through Azure Service Health; we have not seen it directly. Its wording here is as quoted by BleepingComputer and SecurityOnline, and the spokesperson statement is as given to BleepingComputer. The 109, 10 and 120 day figures are our arithmetic from the dates Microsoft gave. This is not investment advice.
Sources: BleepingComputer, Lawrence Abrams, ‘Microsoft Entra Connect Health flaw exploited to steal tenant data’, 21 Nov 2026 · SecurityOnline, ‘Microsoft Entra Connect Health Exposure Leaked Tenant Metadata’, 21 Nov 2026 · Microsoft, Entra Connect Health reference scripts (GitHub, AzureAD/EntraIDGovernance) · FourWeekMBA on the Microsoft 365 outage root cause, 15 Nov 2026 · FourWeekMBA on the Infoblox vendor breach, 17 Nov 2026 · FourWeekMBA on the Optimizely script attack, 17 Nov 2026 · FourWeekMBA on the European Commission intrusion, 19 Nov 2026









