---
title: "Microsoft Entra Connect Health metadata incident"
description: "Microsoft fixed an Entra Connect Health API issue linked to unauthorized access to tenant contact and configuration metadata."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-11-22"
canonical_url: "https://www.ally.security/incidents/microsoft-entra-connect-health-metadata-incident-2026"
markdown_url: "https://www.ally.security/incidents/microsoft-entra-connect-health-metadata-incident-2026.md"
stix_url: "https://www.ally.security/incidents/microsoft-entra-connect-health-metadata-incident-2026/stix.json"
---

# Microsoft Entra Connect Health metadata incident

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

Last modified Nov 22, 2026 · 1 source

## 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.

## What happened

[Microsoft](https://www.microsoft.com/) confirmed to [BleepingComputer](https://www.bleepingcomputer.com/news/security/microsoft-entra-connect-health-flaw-exploited-to-steal-tenant-data/) that it fixed an Entra Connect Health issue involving possible unauthorized access to tenant contact and configuration metadata and notified affected customers. [1](#source-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](#source-1)

The number of affected tenants has not been established publicly.

## Timeline

### November 9, 2026 — API vulnerability discovered

The reported notice gives this discovery date, not the start of exploitation. [1](#source-1)

### November 19, 2026 — Server-side fix deployed

Microsoft confirmed the fix date. [1](#source-1)

### November 20, 2026 — Investigation conclusion communicated

The reported notice describes the finding of unauthorized metadata access. [1](#source-1)

### November 22, 2026 — 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](#source-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](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/microsoft-entra-connect-health-metadata-incident-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Microsoft Entra Connect Health flaw exploited to steal tenant data

news · BleepingComputer · Nov 21, 2026

<https://www.bleepingcomputer.com/news/security/microsoft-entra-connect-health-flaw-exploited-to-steal-tenant-data/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: Microsoft confirmed to BleepingComputer that it addressed a Connect Health issue involving possible unauthorized access to tenant-level contact and configuration metadata.
2. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: The reported notice identified administrator and technical-contact email addresses, tenant identifiers and configuration information, and an expired legacy certificate among the accessed API response fields.
3. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: Customer notice describes investigation conclusion
4. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: Microsoft identifies API vulnerability
5. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: The reported notice dates the API vulnerability’s introduction to July 23 and discovery to November 9; neither date establishes when exploitation began.
6. **Affected Organization · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: Microsoft
7. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: The notification reported by BleepingComputer said Microsoft concluded on November 20 that unauthorized read-only access to affected tenants’ metadata had occurred, with no unauthorized configuration changes identified.
8. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: Microsoft deploys server-side fix
9. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: The reported notice said no customer software update was required and advised monitoring for targeted phishing and reviewing privileged-account security.
10. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: According to the reported notice, passwords, password hashes, authentication tokens and valid cryptographic keys were not exposed.
11. **Occurred At · 100% confidence · current**  
   Microsoft identifies API vulnerability: 2026-11-09
12. **Resulted In · 100% confidence · current**  
   Microsoft Entra Connect Health metadata incident: Microsoft told BleepingComputer that it deployed the fix on November 19 and notified impacted customers through Azure Service Health.
13. **Occurred At · 100% confidence · current**  
   Microsoft deploys server-side fix: 2026-11-19
14. **Occurred At · 100% confidence · current**  
   Customer notice describes investigation conclusion: 2026-11-20

</details>
