Azure THIM SGX collateral service unreachable from nonAzure networks

Sravani Ketha 0 Reputation points
2026-11-17T13:23:19.95+00:00

I use the Azure SGX DCAP collateral service at global.acccache.azure.net (path sgx/certification/v3) for attestation.

From my Azure confidential VM, a request to the rootcacrl endpoint returns HTTP 200.

From a machine outside Azure (Ubuntu, home broadband in India), the TCP connection to port 443 times out. The name resolves to 20.135.140.93 (West Europe, thim.azure.net), but curl reports a connection timeout after 15 seconds, and a netcat test to port 443 also times out.

What I have ruled out:

  • DNS resolves correctly.
  • General HTTPS works from the same machine (microsoft.com returns 200).
  • No proxy is set, and the local firewall has no blocking rules.
  • A TCP traceroute to port 443 enters Microsoft’s network in Hyderabad and travels through Europe, but no reply comes back after the last hop at 51.10.25.146.

My questions:

  1. Is global.acccache.azure.net intended to be reachable only from Azure VMs, or should it be public?
  2. If it is Azure-only, what is the recommended collateral source for a verifier outside Azure that must verify attestation from an Azure confidential VM (for example Intel PCS or a self-hosted PCCS)?
  3. Is there documentation that describes this restriction?

I use the Azure SGX DCAP collateral service at global.acccache.azure.net (path sgx/certification/v3) for attestation.

From my Azure confidential VM, a request to the rootcacrl endpoint returns HTTP 200.

From a machine outside Azure (Ubuntu, home broadband in India), the TCP connection to port 443 times out. The name resolves to 20.135.140.93 (West Europe, thim.azure.net), but curl reports a connection timeout after 15 seconds, and a netcat test to port 443 also times out.

What I have ruled out:

  1. DNS resolves correctly.
  2. General HTTPS works from the same machine (microsoft.com returns 200).
  3. No proxy is set, and the local firewall has no blocking rules.
  4. A TCP traceroute to port 443 enters Microsoft’s network in Hyderabad and travels through Europe, but no reply comes back after the last hop at 51.10.25.146.

My questions:

  1. Is global.acccache.azure.net intended to be reachable only from Azure VMs, or should it be public?
  2. If it is Azure-only, what is the recommended collateral source for a verifier outside Azure that must verify attestation from an Azure confidential VM (for example Intel PCS or a self-hosted PCCS)?
  3. Is there documentation that describes this restriction?

Thanks in advance for any guidance.

Azure Cloud Services
Azure Cloud Services

An Azure platform as a service offer that is used to deploy web and cloud applications.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Manasa Akula 775 Reputation points Microsoft External Staff Moderator
    2026-11-20T21:43:15.8433333+00:00

    Hi Sravani,

    Thank you for providing the detailed connectivity findings.

    Azure THIM is designed to supply attestation collateral for Azure confidential computing workloads. However, an Azure-only network restriction for global.acccache.azure.net is not explicitly documented.

    For verification outside Azure, we recommend:

    1. Using Intel PCS for supported SGX verification collateral.
    2. Using Azure THIM for Azure-specific PCK certificates.
    3. Considering Azure Attestation for remote verification through signed attestation tokens.

    Microsoft Documentation:

    Best regards,
    Manasa Akula

    Was this answer helpful?

    0 comments No comments

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.