Windows Device Health Attestation Failure

Sarah 20 Reputation points
2026-09-17T02:24:29.13+00:00

Laptops fail conditional access checks due to failed Device Health Attestation. How do we verify TPM 2.0 status, Secure Boot, and DHA endpoint access?

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 32,865 Reputation points Independent Advisor
    2026-09-17T02:57:14.06+00:00

    Hello,

    When laptops fail conditional access checks due to Device Health Attestation (DHA), the root cause is usually one of three things: TPM 2.0 not being active or ready, Secure Boot not being enforced, or the client failing to reach the DHA service endpoint. Each of these needs to be verified systematically.

    For TPM 2.0, open an elevated PowerShell session and run Get-TPM. The output should show TpmPresent: True, TpmReady: True, and SpecVersion: 2.0. If the TPM is present but not ready, you may need to clear and reinitialize it from the BIOS/UEFI firmware settings. Also confirm that the BIOS is not set to “Discrete TPM disabled” or “Firmware TPM off.”

    For Secure Boot, check with Confirm-SecureBootUEFI. If the command returns True, Secure Boot is enabled. If it returns False or throws an error, you need to enable Secure Boot in the UEFI firmware. Note that Secure Boot requires UEFI mode; if the machine is running in legacy BIOS mode, it cannot be enabled.

    For DHA endpoint access, the client must reach the Microsoft Health Attestation Service. The endpoint is https://attestation.microsoft.com. In an enterprise environment, conditional access policies rely on the device submitting its health report to this service. If the laptops are behind a proxy or firewall, ensure outbound HTTPS traffic to that endpoint is allowed. You can test connectivity with Test-NetConnection attestation.microsoft.com -Port 443. If this fails, the device cannot complete health attestation and will be blocked.

    In practice, the verification sequence is: confirm TPM 2.0 is active and owned, confirm Secure Boot is enabled, and confirm the client can reach the DHA endpoint. If all three are correct, the device should pass conditional access checks. If any of these fail, remediation must be done at the firmware or network level before the device can be considered compliant.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    Domic Vo.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-17T02:24:50.3+00:00

    Use this verification path on an affected laptop:

    1. Check TPM version.
      • Press Win + R, run tpm.msc.
      • In TPM Management on Local Computer, check Specification Version.
      • Device Health Attestation supports devices with TPM 1.2 or 2.0, but for Intune health attestation compliance checks, if the device is on TPM 1.2 and supports TPM 2.0, update to TPM 2.0.
    2. Verify UEFI and PCR7 binding.
      • Open an elevated Command Prompt and run msinfo32.
      • In System Summary, confirm:
        • BIOS Mode = UEFI
        • PCR7 Configuration = Bound
      • A computer with legacy BIOS and TPM 2.0 will not work as expected for this scenario.
    3. Verify Secure Boot state.
      • Open an elevated PowerShell window and run: 
             Confirm-SecureBootUEFI
      • Expected result: True.
    4. Verify BitLocker PCR protection.
      • Run: 
             manage-bde -protectors -get $env:systemdrive
      • Confirm the system drive is protected by PCR 7.
    5. Verify DHA service connectivity.
      • Both the device and the MDM server must be able to reach has.spserv.microsoft.com over TCP 443 (HTTPS).
      • If that endpoint is unreachable, health attestation validation can fail.
    6. Check DHA/HealthAttestation errors if connectivity is suspected.
      • Relevant HealthAttestation CSP errors include:
        • 30 = failed to send HTTP request
        • 31 = failed to receive response
        • 32 = failed to query HTTP headers
        • 33 = empty response with HTTP OK
        • 34 = empty response with HTTP error
        • 404 = DHA service endpoint not reachable
    7. Validate what DHA reports to MDM.
      • Health Attestation can provide MDM with device state such as:
        • Secure Boot enabled
        • BitLocker enabled
        • ELAM loaded
        • Boot and kernel debug enabled/disabled
        • VSM enabled
        • TPM provisioned with a trusted endorsement certificate
      • Conditional access decisions depend on the MDM evaluating that attestation state and updating device compliance in Microsoft Entra ID.

    If devices still fail conditional access after these checks, focus on mismatches in TPM version, UEFI/PCR7 state, Secure Boot result, or blocked access to has.spserv.microsoft.com:443.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.