Microsoft says Entra Connect Health flaw exposed admin emails
A bug in the identity monitoring service's API, present since July, gave outsiders read-only access to tenant metadata. Microsoft says passwords and tokens were not exposed.
Key takeaways
- Microsoft says a flaw in the Entra Connect Health API was exploited to read administrator email addresses and tenant metadata.
- The bug was introduced on July 23, detected on November 9 and fixed on the server side on November 19, Microsoft says.
- Microsoft says passwords, password hashes, authentication tokens and valid keys were not exposed, and no configuration changes were found.
- Microsoft has not said how many organizations were affected.
- Microsoft advises customers to watch for targeted phishing and use phishing-resistant MFA on admin accounts.
Microsoft has told affected organizations that a flaw in its Entra Connect Health service was exploited to read administrator email addresses and tenant configuration data, according to a customer notification reported by BleepingComputer and SecurityOnline. The notice was shared by administrators on Reddit.
Entra Connect Health lets administrators track the health and alerts of their on-premises identity systems from the Microsoft Entra admin center, BleepingComputer explains. Microsoft says it found the vulnerability in the service's API on November 9, and that it had been introduced on July 23.
What was exposed?
"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 notice, according to BleepingComputer. Both reports say the flaw could potentially have allowed changes to Connect Health monitoring settings, but Microsoft says its logs showed only read-only access.
According to the reports, the data exposed included the email addresses of administrators and technical contacts, along with each tenant's ID, display name and initial domain, its country and region details, its license tier, directory sync status and last sync time, and its Connect Health onboarding status. The API also returned an expired certificate that had been used with an internal Microsoft service retired in late 2024; Microsoft says the certificate was no longer in use and poses no risk.
Microsoft says the flaw did not reveal passwords or password hashes, authentication tokens, valid cryptographic keys, or details of on-premises servers and Active Directory layout, according to both reports.
What has Microsoft done?
Microsoft deployed a server-side fix on November 19, finished its investigation the next day and began notifying affected organizations, BleepingComputer reports. A Microsoft spokesperson told BleepingComputer the company had "identified and addressed a security issue" and notified affected customers through Azure Service Health, but declined to give further details. Microsoft has not said who exploited the flaw or when the attacks began. The company has not disclosed how many tenants were affected, though more than a dozen administrators reported receiving the notice on Reddit, and some managed service providers said they got notices for several customer tenants.
The notice says customers do not need to install updates or take other steps to fix the flaw itself, BleepingComputer reports. Microsoft does recommend warning security teams about possible targeted phishing aimed at the exposed administrator addresses, using phishing-resistant multifactor authentication on privileged accounts, and reviewing Connect Health settings and Entra audit and sign-in logs. It has also published a PowerShell script to show which types of tenant metadata could have been exposed. The script shows current configuration values, not the data that was actually accessed, BleepingComputer notes.
Questions readers are asking
What did the Entra Connect Health flaw expose?
Read-only tenant metadata, including email addresses of technical contacts and administrators, tenant IDs, domain names, license tiers and sync status, according to Microsoft's notice as reported by BleepingComputer and SecurityOnline.
Do customers need to patch anything?
No. Microsoft fixed the flaw on the server side, but it recommends watching for targeted phishing and reviewing audit and sign-in logs.
How many organizations were affected?
Microsoft has not disclosed the number. More than a dozen administrators reported receiving notices on Reddit, BleepingComputer reports.
Sources
- #microsoft
- #entra
- #data-breach
- #identity-security
- #phishing
Get the day's top AI & tech stories on WhatsApp: Follow the NextFish channel
Get stories like this every morning.
Related
Cybersecurity2 min
FBI reportedly investigating breach of its NCIC crime database
The national database police use for warrants and background checks was reportedly breached, the second reported FBI intrusion in recent months. The USDA was also hit this week.
Big Tech2 min
Nadella expects more outages as AI-found bugs force rushed patches
Microsoft's CEO told the DealBook Summit that AI is finding flaws so fast that fixes go straight to production with little testing, adding instability.
Cybersecurity2 min
Canada warns servers running AI hacking tool ARTEX target its organizations
The Canadian Centre for Cyber Security says AI-enabled offensive security frameworks are spreading, and that servers running ARTEX have targeted Canadian organizations for months.
Cybersecurity3 min
Amazon says hackers used AI tool Cairn to find and exploit a zero-day
Amazon Threat Intelligence says AI agents found an unknown flaw in a medical imaging app and used it to take over a university server in East Asia, then breach a second university.