Microsoft Entra Connect Health metadata incident

Microsoft notified affected customers after fixing a Connect Health metadata security issue on November 19.

Last modified

Summary

  • Environment: Microsoft Entra Connect Health monitoring API
  • Operational impact: Tenant metadata access reported; no unauthorized configuration changes identified in the reported notice.
  • Financial impact: No verified financial-loss total has been disclosed.
  • Record status: Developing record. Reviewed November 22, 2026; updated as evidence emerges.

What happened

Microsoft confirmed to BleepingComputer that it fixed an Entra Connect Health issue involving possible unauthorized access to tenant contact and configuration metadata and notified affected customers. [1]

Impact

The notification reported by BleepingComputer described unauthorized read-only access to administrator and technical-contact email addresses, tenant identifiers, configuration fields and an expired legacy certificate. It said passwords, authentication tokens and valid cryptographic keys were not exposed, and no unauthorized configuration changes were identified. [1]

The number of affected tenants has not been established publicly.

Timeline

  1. API vulnerability discovered

    The reported notice gives this discovery date, not the start of exploitation.

    [1]
  2. Server-side fix deployed

    Microsoft confirmed the fix date.

    [1]
  3. Investigation conclusion communicated

    The reported notice describes the finding of unauthorized metadata access.

    [1]
  4. Briefing updated

    This briefing was last reviewed and updated on November 22, 2026.

Threat Group & Attack Vector

The reported notice describes an API vulnerability introduced on July 23. That date does not establish when attackers began exploiting it. [1]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

Microsoft notified customers through Azure Service Health. The reported guidance required no software update and advised vigilance for targeted phishing and review of privileged-account security. [1]