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:
- Is global.acccache.azure.net intended to be reachable only from Azure VMs, or should it be public?
- 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)?
- 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:
- 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:
- Is global.acccache.azure.net intended to be reachable only from Azure VMs, or should it be public?
- 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)?
- Is there documentation that describes this restriction?
Thanks in advance for any guidance.