Microsoft Entra Connect Health Flaw Exposed Tenant Admin Email Addresses
Microsoft is notifying customers that attackers exploited an Entra Connect Health flaw to read tenant metadata, including administrator email addresses. No passwords or tokens were taken, but targeted phishing of admins is the likely next step.

Microsoft is notifying organisations that attackers exploited a flaw in its Entra Connect Health service to read tenant metadata, including the email addresses of administrator accounts and tenant technical contacts. Microsoft says it discovered the flaw on 9 November, deployed a server-side fix on 19 November and began notifying affected customers on 20 November, according to the notice it sent to customers.
No passwords or tokens were taken, Microsoft says, and customers do not need to install anything. The real risk is what comes next: attackers now hold a list of verified administrator addresses for Microsoft 365 and Entra tenants, which is exactly the starting point for targeted phishing and fake support calls.
Key facts
- Service: Microsoft Entra Connect Health, the cloud service that monitors on-premises identity infrastructure synced to Entra ID
- What was accessed: read-only tenant metadata, including email addresses of administrator accounts and technical contacts, tenant IDs and display names, initial domain names, country and region, Entra license tier, directory sync status and last sync time, and Connect Health onboarding status
- What was not accessed: passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises topology and Azure subscription information, according to Microsoft
- Timeline: flaw introduced on 23 July, discovered on 9 November, fixed server-side on 19 November, customer notices from 20 November
- Scope: Microsoft has not said how many tenants were affected, when the attacks began or who carried them out
- Customer action: no software update or remediation required, per the notice
What happened
The flaw sat in the Entra Connect Health API. It allowed unauthorised, read-only access to metadata about the tenants that use the service. Microsoft says it found no sign that any configuration was changed. The notice also mentions an expired certificate that had been used with a decommissioned internal Microsoft service.
Administrators began sharing the notice on public forums on 21 November, and some managed service providers reported receiving separate notices for several customer tenants. Microsoft has published a PowerShell script that lets administrators review the types of tenant metadata involved. The script shows current configuration values, not the data that was read during the incident.
Why email teams should care
The exposed fields are the ones a phisher needs. An attacker who knows a tenant's admin address, its display name, its initial onmicrosoft.com domain and its license tier can write a convincing fake Microsoft notice: a licence renewal, a sync error, a security alert. The same data can support helpdesk impersonation calls, the technique already seen in recent subscription bombing campaigns aimed at Microsoft Teams users.
Admin mailboxes are also where Microsoft 365 sends tenant warnings, including sending limit and outbound spam notices. If those addresses start receiving lookalike alerts, real warnings are more likely to be ignored, or a fake one acted on.
What it means for senders
What changes
Administrator email addresses of Microsoft 365 and Entra tenants that use Connect Health were exposed, making those admins likely targets for tailored phishing that imitates Microsoft. Nothing changes in how mail is sent or delivered.
Who is affected
Organisations that received Microsoft's notice, their IT and messaging administrators, and managed service providers that run tenants for clients.
When
The flaw was fixed on 19 November 2026 and notices went out from 20 November. Expect follow-up phishing in the coming weeks.
Action checklist
- Check the admin and technical contact inboxes for a Microsoft security notice about Entra Connect Health.
- Warn your administrators that any email claiming to be from Microsoft about licences, sync errors or account security must be checked in the admin center, not through links in the message.
- Enforce phishing-resistant MFA such as FIDO2 keys or passkeys on every privileged account.
- Review Entra audit and sign-in logs for unusual sign-ins to admin accounts since July.
- Run Microsoft's Connect Health script to see which metadata fields your tenant holds, and review your Connect Health configuration.
- Tighten inbound authentication checks so mail that claims a Microsoft sender but fails DMARC is quarantined; see how to detect phishing emails that pass every check.
Sources
- Security notification Microsoft sent to affected Entra customers on 20 November 2026 (not published as a public advisory)
- Microsoft: Entra Connect Health scripts on GitHub (tool to review the tenant metadata types involved)
- BleepingComputer report on the notification, 21 November 2026 (third-party report, cited because Microsoft has not published a public advisory)
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter