November 22, 2026

Attackers Read Admin Emails and Tenant Details Through a Microsoft Entra Connect Health Flaw: A Step-by-Step Response Plan for Small IT Teams

Microsoft is notifying organizations that a flaw in its Entra Connect Health service was exploited to read administrator email addresses and tenant configuration details. No passwords or tokens were exposed and no fix is needed on your end, but the leaked details are ideal for targeted phishing. Here is what to do next.

An IT administrator at a small business office reviewing a laptop while holding a smartphone

Here Is How Layered Defenses Help Blunt the Phishing That Follows a Cloud Provider’s Data Exposure

Some administrators opened an unwelcome message from Microsoft this week: a notice that a flaw in one of its identity services had been exploited and that details about their organization had been read. As BleepingComputer reports, the affected service is Microsoft Entra Connect Health, which lets administrators monitor the health and alerts of their on-premises identity infrastructure from the Entra admin center.

The facts first

  • The flaw was in the Connect Health API. It was introduced on July 23 and discovered by Microsoft on November 9.
  • Microsoft deployed a server-side fix on November 19, finished its investigation on November 20 and began notifying affected organizations through Azure Service Health.
  • Exposed: email addresses of tenant technical contacts and administrator accounts; tenant IDs, display names, initial domain names, country codes and regional information; license tiers and directory synchronization status, including the last sync time; and an expired certificate once used to register Connect Health agents with an internal service retired in late 2024.
  • Not exposed, per Microsoft: passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology, or Azure subscription information.
  • Microsoft says the access was read-only and it found no unauthorized configuration changes.
  • Unknown: who exploited the flaw, how many tenants were hit and when exploitation began. More than a dozen administrators reported the notice on Reddit, and some managed service providers received notices for several client tenants.

Your response, step by step

  1. Check whether you were notified. Look in Azure Service Health and in the inboxes of your technical contacts. If an IT provider manages your tenant, ask them directly whether a notice arrived for your organization.
  2. Warn the people whose addresses leaked. Microsoft recommends alerting security teams to targeted phishing and social engineering. For a small company, that means telling every administrator and technical contact by name that they are now likely targets, and that messages referencing your tenant name, domain or license details are not proof of legitimacy.
  3. Move privileged accounts to phishing-resistant sign-in. Microsoft advises phishing-resistant multi-factor authentication for privileged accounts. Security keys or passkeys hold up far better against a convincing fake login page than text codes or push approvals.
  4. Review audit and sign-in logs. Look through your directory audit and sign-in logs for unfamiliar locations, new devices, added administrators or changed security settings since the summer.
  5. Review your Connect Health configuration. Microsoft recommends confirming it looks as expected. Its published PowerShell script shows the types of metadata that could have been exposed, but note that it displays current values, not what was actually accessed.
  6. Reduce the number of administrators. Every admin address that leaked is a target. Remove standing admin rights that are not needed daily and use separate admin accounts that are never used for email or browsing.
  7. Write down what happened. Record the notice, what you checked and what you changed. If something suspicious turns up later, that record will save time.

Where the layers fit

Microsoft says no customer remediation is required for the flaw itself, and that is true. The risk is what an attacker can do with a list of your administrators, your domain and your license level. Each layer below makes that information less useful:

  • Email filtering and impersonation protection catch many lures before they land.
  • Staff awareness turns a well-informed fake into a reported one.
  • Phishing-resistant authentication means a stolen password alone does not open the account.
  • Least privilege and separate admin accounts limit what a compromised account can change.
  • Logging and alerting, through tools such as Microsoft Entra ID’s sign-in logs or any comparable identity monitoring service, surface the attempt that gets through.

What this means for your company

This incident is a reminder that even when your own settings are perfect, a provider can expose information about you. You cannot control that, but you can control how much damage the leaked details can do. If your administrators sign in with phishing-resistant methods, use separate admin accounts, and know they are likely targets this month, a list of their email addresses is worth very little to an attacker.

If you received a notice, are not sure whether you did, or want your admin accounts hardened before the follow-up phishing starts, we can walk through it with you. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author