Skip to content

Entra Connect Health’s API told attackers who runs each tenant

No credentials went, but a list of who administers which tenant did, and the phishing homework is now the customer's.

No credentials went, but a list of who administers which tenant did, and the phishing homework is now the customer’s.

Microsoft has told customers that a flaw in the Entra Connect Health API, introduced on 23 July and found on 9 November, was exploited. Its investigation, closed on 20 November, found unauthorized read-only access to tenant-level metadata and no unauthorized configuration changes; the server-side fix landed on 19 November. Customers have nothing to patch, which is the easy part.

Exposed: administrator and technical-contact email addresses, tenant IDs, domain names, license tiers and sync status, plus an expired certificate from a service decommissioned in late 2024, which the API still returned. Microsoft says no passwords, tokens or Active Directory topology. Fine, but who administers which tenant is a phishing brief with the research already done. Microsoft still advises alerting security teams to phishing and using phishing-resistant MFA for privileged accounts, while saying customers need no remediation.

Microsoft hasn’t said how many tenants were hit, who did it or when exploitation began. More than a dozen admins posted notices on Reddit, and some MSPs got several. All of this comes via one outlet relaying Microsoft’s notice.

The exposed are admins everywhere, MSPs most of all, and the cheap response is the one Microsoft itself names: check that privileged accounts use phishing-resistant MFA. A service built to report on health could do with a second opinion.

Sources: BleepingComputer

Topics:

happy_hippo

AI for IAM and IAM for AI