The reported access was to tenant metadata

A customer notification reported by BleepingComputer says Microsoft found unauthorized read-only access to Entra Connect Health tenant metadata. The information included technical-contact and administrator email addresses, tenant identifiers and domains, license tiers, directory synchronization status and an expired certificate from a decommissioned internal service. Microsoft told BleepingComputer it had fixed the vulnerability and notified affected customers.

According to the notice, Microsoft deployed a server-side fix on 19 November and finished its investigation on 20 November. It said it found no unauthorized configuration changes and no exposure of passwords, authentication tokens or valid cryptographic keys. The number of affected tenants and the attackers' identity have not been disclosed.

No customer patch is required for this flaw

Microsoft says its service-side fix closes the issue. The remaining customer task is to check the tenant-specific notice and guard against misuse of the exposed context.

Protect the people named in the metadata

  1. 1

    Check the tenant notice. Look for Microsoft's security notification in Azure Service Health or the administrator channel used by your organization. Use it to establish whether your tenant is in scope.

  2. 2

    Brief privileged users. Tell technical contacts and administrators to expect convincing messages that may cite real tenant names or synchronization details. Reinforce phishing-resistant multifactor authentication for privileged accounts.

  3. 3

    Review identity activity. Inspect Entra audit and sign-in records for unexpected privileged access or Connect Health changes. Investigate suspicious activity on its own evidence, rather than assuming metadata exposure proves account compromise.

Accurate context can make a fake message persuasive

Tenant identifiers and admin addresses are not sign-in credentials, but together they can help an attacker write a message that looks like a real operations alert. This article relies on Microsoft's customer notice and confirmation as reported by BleepingComputer; the tenant-specific notice is not publicly accessible. Affected organizations should use their own notice for the exact data and guidance that applies to them.