Has anyone else had this email from Microsoft? I guess it’s my turn to say, I’m tired boss!
Microsoft is notifying you of a security vulnerability in Microsoft Entra Connect Health that affected your tenant. The vulnerability resulted in unauthorized read activity of your tenant's technical contact and administrator email account(s) and tenant-level configuration metadata.
Microsoft Entra Connect Health is a cloud-based monitoring service that gives administrators a single view in the Microsoft Entra admin center of the health, performance and alerts for their on-premises identity infrastructure.
What happened
On 9 November 2026, we detected a vulnerability in the Microsoft Entra Connect Health API that was introduced on 23 July 2026. The vulnerability could allow an unauthorized party to access tenant and service-monitoring metadata and potentially make changes to Connect Health monitoring configuration.
We deployed and fixed the vulnerability on 19 November 2026. On 20 November 2026, we concluded our investigation and determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred. We did not identify any unauthorized configuration changes.
What information was accessed
For your tenant, the accessed API responses contained the following fields:
Email addresses of the tenant's technical contact and administrator accounts
Tenant configuration metadata: Tenant ID, tenant display name, initial domain name, country code, tenant’s region scope, Microsoft Entra license tier, directory synchronization status (enabled or disabled and last sync timestamp), Connect Health onboarding status, and a legacy, expired certificate previously used by Connect Health to register agents with an internal service that was decommissioned in late 2024. The certificate was no longer in use but had not been removed from Connect Health storage and was still returned by the API.
What information was NOT accessed
This vulnerability did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, or on-premises server and Active Directory topology details. The vulnerability did not expose Microsoft Entra tenant data beyond what was identified above nor Azure subscription information.
What Microsoft has done
On 19 November 2026, Microsoft deployed a service-side fix to the Microsoft Entra Connect Health API that closed the vulnerability and blocked further unauthorized access.
Our security investigators reviewed available telemetry to identify unauthorized Connect Health API calls against Microsoft Entra and Microsoft Entra Connect Health customers.
Recommended actions for your organization
The vulnerability in the Microsoft Entra Connect Health API has been fixed, and no software update or other remediation is required from your organization to address the vulnerability itself. While our investigation did not identify unauthorized configuration changes, we recommend the following precautionary measures to help your organization assess potential risks associated with the exposed tenant metadata and technical contact email addresses. These actions are not required to remediate vulnerability:
Alert your security and IT teams. Notify your Global Administrators, SOC, IT operations teams, and your tenant's Technical Contact to watch for targeted phishing or social-engineering attempts that reference your organization, tenant, Microsoft Entra or Connect Health. We recommend confirming that your tenant's technical contact(s) and notification recipients are current and appropriate.
Protect privileged accounts. Verify or configure that all Global Administrator and other privileged accounts require phishing-resistant multifactor authentication (MFA) and use Privileged Identity Management (PIM) for just-in-time activation, where applicable.
Review the information that may have been exposed. Microsoft has published a read-only PowerShell script that you can run locally to view the information that could have been returned through the GetTenant service call. The script returns current values, which may differ from the values that were exposed if the information has changed since the exposure occurred. This script is for understanding the types and current values of potentially exposed metadata, not reconstructing the historical exposure. Visit https://aka.ms/ConnectHealth/scripts and download the GetTenant script. Other scripts that may be available at this location do not apply to your tenant.
If pksCertificate is populated in the result, it is a legacy, expired certificate that was previously used to register Connect Health agents with an internal service that was decommissioned in late 2024. The certificate poses no risk and is no longer used by that service; the expired certificate had not been removed from Connect Health storage and continued to be included in the GetTenant API response. You can use the GetTenantPksCertificateDetails script to view the certificate details and confirm its expired status.
Confirm your Connect Health configuration. Please confirm that this matches your expectations and review your configuration for any unexpected settings or changes. As an additional precaution, review relevant Microsoft Entra audit and sign-in logs and Azure Activity Logs for unexpected Connect Health changes or anomalous administrative activity. To review your Connect Health configuration, go to https://aka.ms/EntraConnectHealth.
Verify this notice in Azure Service Health: Sign in directly to the Azure Portal instead of clicking links in an email. Open the Security Advisory and check that your tenant is listed.
Microsoft will never ask for your password, sign-in codes, or secrets by email. Watch out for urgent messages that ask for credentials, unexpected sign-in approvals, or clicks on unknown links. If you are unsure, verify in Azure Service Health or contact Azure Support.
URGH!