MicrosoftDocs
Baltimore CyberTrust Root chained up to itself
Why Baltimore CyberTrust Root chained up to itself? Is it a typo?
Prior to the change, most of the TLS certificates used by Azure services chained up to the following Root CA: Baltimore CyberTrust Root d4de20d05e66fc53fe1a50882c78db2852cae474
After the change, TLS certificates used by Azure services will chain up to one of the following Root CAs: DigiCert Global Root G2 df3c24f9bfd666761b268073fe06d1cc8d4f82a4 DigiCert Global Root CA a8985d3a65e5e5c4b2d7d66d40c6dd2fb19c5436 Baltimore CyberTrust Root d4de20d05e66fc53fe1a50882c78db2852cae474 D-TRUST Root Class 3 CA 2 2009 58e8abb0361533fb80f79b1b6d29d3ff8d5f00f0 Microsoft RSA Root Certificate Authority 2017 73a5e64a3bff8316ff0edccc618a906e4eae4d74 Microsoft ECC Root Certificate Authority 2017 999a64c37ff47d9fab95f14769891460eec4c3c5
[Enter feedback here]
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: b3c4368c-82a4-f82e-b1a7-41cfa694fa58
- Version Independent ID: 60a94729-02ad-0ef1-a642-63351d0171ea
- Content: Azure TLS Certificate Changes
- Content Source: articles/security/fundamentals/tls-certificate-changes.md
- Service: security
- Sub-service: security-fundamentals
- GitHub Login: @msmbaldwin
- Microsoft Alias: mbaldwin
@timzhang926 Thanks for your feedback! We will investigate and update as appropriate.
@timzhang926 Thank you for bringing this to our attention. I've delegated this to content author @msmbaldwin, who will review it and offer their insightful opinions.
