MC1473156 - Plan for Change: Intune migration for Windows Health Attestation to Microsoft Azure Attestation for Windows 11 devices

Microsoft 365 Message Center announcement MC1473156.

MS Message Center's Summary

Microsoft Intune is migrating Windows Health Attestation for Windows 11 devices to Microsoft Azure Attestation by the end of March 2027. Administrators must review network and firewall rules to permit access to the new Azure endpoints before the rollout completes. Failure to update network configurations will cause compliance policies relying on health signals to fail.

Administrator impact
Administrators must review network configurations to ensure devices can reach the required Azure Attestation endpoints before March 2027.
End user impact
Windows 11 devices might be marked as noncompliant if required network endpoints are blocked and health policies cannot be evaluated.
Importance
7/10: This change requires proactive network updates to prevent device compliance failures across the organisation.

Configure endpoints for Azure Attestation migration

Microsoft Summary

Intune will migrate Windows Health Attestation from Device Health Attestation to Microsoft Azure Attestation by early 2027. Organizations must ensure network access to Azure Attestation endpoints to maintain compliance evaluation for Windows 11 devices using health-based policies, or risk compliance failures.

Message Center ID
MC1473156
Category
plan For Change
Severity
normal
Services
Microsoft Intune
Tags
User impact, Admin impact
Published
2026-09-16
Last updated
2026-09-16
Expires
2027-07-31

[What and why:] Microsoft Intune will migrate Windows Health Attestation compliance evaluation from the current Device Health Attestation (DHA) service to Microsoft Azure Attestation (MAA). This is an Intune service-side change that will happen automatically. [Rollout schedule:] This migration is expected at the end of the first quarter in calendar year 2027. [Impact on your organization:] This change affects evaluation of Windows compliance policies that rely on Health Attestation signals. Action is required to avoid interruption. Organizations that do not allow access to the required Azure Attestation endpoints will experience issues with Health Attestation-based compliance evaluation after the migration is completed. [Action required/recommendations:] Review your network, firewall, proxy, and endpoint access configurations. Specifically, verify that your environment allows devices to access the required Microsoft Azure Attestation endpoints. For detailed guidance, including the required endpoints and configuration recommendations, refer to: Configure endpoints for Azure Attestation migration . [Compliance considerations:] If unaddressed, Windows 11 devices with assigned compliance policies using any of the device health settings (BitLocker, Secure Boot, Code Integrity) will fall out of compliance.