enzosoler.comreviews 09bench 9 deviceslive test Can a ring and a watch replace my Apple Watch?
Published

Microsoft Entra Connect Health flaw exposed tenant admin emails; expect targeted phishing

Rows of server racks with blue status lights in a data center aisle
Image: Pexels

Microsoft told customers that attackers exploited a flaw in the Entra Connect Health API to read tenant metadata, including administrator and technical contact email addresses, tenant IDs and license tiers. Microsoft fixed it server-side on November 19. No patch is needed, but admins should expect targeted phishing.

If your company syncs on-premises Active Directory to Microsoft Entra ID and uses Connect Health, assume your admin and technical contact email addresses are now in an attacker’s hands, and get ready for phishing aimed at them. Microsoft is notifying customers that a flaw in the Entra Connect Health API was exploited to read tenant data, according to BleepingComputer, which saw the notification.

What Microsoft says happened

Entra Connect Health is the cloud service that monitors hybrid identity setups: Entra Connect sync servers, AD FS and domain controllers. Per the notification as BleepingComputer reports it:

  • The flaw sat in a Connect Health API capability “first introduced on July 23.”
  • Microsoft found it on November 9, 2026, deployed a server-side fix on November 19 and closed its investigation on November 20.
  • Attackers got “unauthorized read-only access to tenant-level metadata.”
  • Exposed: administrator and technical contact email addresses, tenant IDs, license tiers and directory sync status.
  • Not exposed, per Microsoft: passwords, password hashes, tokens or valid cryptographic keys. It found no unauthorized configuration changes.

Microsoft has not said who exploited the flaw, how many tenants were hit or when the attacks began. No CVE or public security advisory was listed at the time of writing. The notification links a PowerShell script at aka.ms/ConnectHealth/scripts that shows your tenant’s current metadata. It shows today’s values. It cannot tell you what was read during the attack.

What to do this week

  1. Warn the named contacts. Tell every person listed as a administrator or technical contact that phishing using real tenant details is likely. A message that quotes your tenant ID or license tier proves nothing.
  2. Require phishing-resistant MFA for privileged accounts. Microsoft’s notification recommends it. Passkeys and FIDO2 security keys qualify; SMS codes and push approvals do not.
  3. Read the logs. Check Entra sign-in and audit logs for privileged accounts since July 23, the date the vulnerable capability shipped.
  4. Review Connect Health. Confirm who holds roles on it and remove access nobody uses.

There is nothing to install. The fix was on Microsoft’s side.

Metadata leaks make the phishing believable

The leak contains no credentials, and that limits the direct damage. The risk is what comes next. A list of the exact people who run each tenant, with the license tier and sync status attached, lets an attacker write a convincing “Microsoft support” email or call to the one person who can approve a sign-in or reset MFA. For this month’s other Microsoft fixes, see November’s Patch Tuesday and its Outlook zero-day.

One email when a review goes up. Unsubscribe from any of them.