- Home
- Azure
- Azure Storage Blog
- Azure Storage TLS: Critical changes are almost here! (…and why you should care)
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
This blog contains important information about TLS certificate changes for Azure Storage endpoints that may impact client connectivity.
In 2020 most Azure services were updated to use TLS certificates from Certificate Authorities (CAs) that chain up to the DigiCert Global G2 root. However, Azure Storage, remained on TLS certificates issued by the Baltimore CyberTrust Root. The time has now come for Azure Storage to switch from the Baltimore CyberTrust CA Root to the DigiCert Global G2 CA Root*. The migration will start in July 2022, and finish by end of October 2022.
We expect that most Azure Storage customers will not be impacted; however, your application may be impacted if you explicitly specify a list of acceptable CAs (a practice known as “certificate pinning”). In scope Azure Storage services include Blob, File, Table, Queue, Static Website, ADLS Gen2. This change is limited to public Azure cloud and US Government cloud. There are no changes in other sovereign clouds like Azure China.
This change is being made because the current "Baltimore CyberTrust Root" will expire in May 2025.
If any client application has pinned to the root CA Baltimore CyberTrust Root or current intermediate CAs listed in the table below, immediate action is required to prevent disruption to connectivity to Azure Storage.
* Other Azure service TLS certificates may be issued by a different PKI.
Action Required
- If your client application has pinned to the Baltimore CyberTrust Root CA, in addition to Baltimore, add the DigiCert Global Root G2 to your trusted root store before February 2022.
- If your client application has pinned to the intermediate CAs, in addition to Microsoft RSA TLS CAs, add the Microsoft Azure TLS Issuing CAs to your trusted root store before February 2022.
- Keep using the current root or intermediate CAs in your applications or devices until the transition period is completed (necessary to prevent connection interruption).
- Make sure SHA384 for Server certificate processing is enabled on the device.
How to check
1. If your client application has pinned to
- Root CA: Baltimore CyberTrust Root CA or,
- Intermediate CA: Microsoft RSA TLS CA 01
- Intermediate CA: Microsoft RSA TLS CA 02
detailed in the table below, then search your source code for the thumbprint, Common Name, and other cert properties of any of the root CA or intermediate CAs. If there is a match, then your application will be impacted, immediate action is required:
- To continue without disruption due to this change, Microsoft recommends that client applications or devices trust the root CA – DigiCert Global Root G2:
DigiCert Global Root G2
(Thumbprint: df3c24f9bfd666761b268073fe06d1cc8d4f82a4)
- Intermediate certificates are expected to change more frequently than root CA. Customers who use certificate pinning are recommended to not taking dependencies on them and instead pin to the root certificate as it rolls less frequently.
If you are currently pinning to the intermediate CAs and have a requirement to continue pinning to intermediate CAs, to prevent disruption due to this change, you should update the source code to add the intermediate Microsoft Azure TLS Issuing CAs listed in the table below to the trusted store.
2. To prevent future disruption, you should also add the following roots to the trusted store. This will save you from the allowlist effort in near future if you add the recommended root CAs now:
- DigiCert Global Root G3
(Thumbprint: 7e04de896a3e666d00e687d33ffad93be83d349e) - Microsoft RSA Root Certificate Authority 2017
(Thumbprint: 73a5e64a3bff8316ff0edccc618a906e4eae4d74) - Microsoft ECC Root Certificate Authority 2017
(Thumbprint: 999a64c37ff47d9fab95f14769891460eec4c3c5)
Note: If you have a requirement to pin to intermediate CAs, to prevent future disruption, you should also add the intermediate Microsoft Azure ECC TLS CAs listed in the table below to the trusted store.
3. If you have completed the step 1 and need to validate your changes, we can provide a test environment on demand for your convenience to verify prior to July 2022. To request a test storage account, please open a support request with the options below and a member from our engineering team will get back to you.
- For Issue type, select Technical.
- For Subscription, select your subscription.
- For Service, select My Services, then select Blob Storage.
- For Resource, select your resource.
- For Summary, enter #storagecertificatetest.
- For Problem type, select Connectivity.
- For Problem subtype, select Dropped or terminated connections.
Certificate Renewal Summary
The table below provides information about the certificates that are being rolled. Depending on which certificate your service uses for establishing TLS connections, action may be needed to prevent loss of connectivity.
|
Certificate |
Current |
Post Rollover (July 1, 2022 – October 31, 2022) |
Action |
|
Root |
Thumbprint (SHA1): d4de20d05e66fc53fe1a50882c78db2852cae474 OU = CyberTrust |
Thumbprint (SHA1): df3c24f9bfd666761b268073fe06d1cc8d4f82a4 Expiration: Friday, January 15, 2038 5:00:00 AM |
Required by 30 June 2022 |
|
Root |
|
Thumbprint (SHA1):
Thumbprint (SHA1):
Thumbprint (SHA1):
|
Recommended to prevent disruption |
|
Intermediates |
Thumbprints (SHA1):
CN = Microsoft RSA TLS CA 01 Thumbprint: 703d7a8f0ebf55aaa59f98eaf4a206004eb2516a
CN = Microsoft RSA TLS CA 02 Thumbprint: b0c2d2d13cdd56cdaa6ab6e2c04440be4a429c75
Expiration: Tuesday, October 8, 2024 12:00:00 AM; O = Microsoft Corporation C = US |
Thumbprints (SHA1):
CN = Microsoft Azure TLS Issuing CA 01 b9ed88eb05c15c79639493016200fdab08137af3
CN = Microsoft Azure TLS Issuing CA 02 Thumbprint: c5fb956a0e7672e9857b402008e7ccad031f9b08
CN = Microsoft Azure TLS Issuing CA 05 Thumbprint: 56f1ca470bb94e274b516a330494c792c419cf87
CN = Microsoft Azure TLS Issuing CA 06 Thumbprint: 8f1fd57f27c828d7be29743b4d02cd7e6e5f43e6
Expiration: Thursday, June 27, 2024 4:59:59 PM; Issuer = Microsoft RSA Root Certificate Authority 2017 O = Microsoft Corporation C = US
-------------------------------------------------------
CN = Microsoft Azure TLS Issuing CA 01 2f2877c5d778c31e0f29c7e371df5471bd673173
CN = Microsoft Azure TLS Issuing CA 02 Thumbprint: e7eea674ca718e3befd90858e09f8372ad0ae2aa
CN = Microsoft Azure TLS Issuing CA 05 6c3af02e7f269aa73afd0eff2a88a4a1f04ed1e5
CN = Microsoft Azure TLS Issuing CA 06 Thumbprint: 30e01761ab97e59a06b41ef20af6f2de7ef4f7b0
Expiration: Thursday, June 27, 2024 4:59:59 PM; Issuer = DigiCert Global Root G2 O = DigiCert Inc C = US
|
Required by 30 June 2022 |
|
Intermediates |
|
Thumbprints (SHA1):
CN = Microsoft Azure ECC TLS Issuing CA 01 Thumbprint: cda57423ec5e7192901ca1bf6169dbe48e8d1268
CN = Microsoft Azure ECC TLS Issuing CA 02 Thumbprint: 489ff5765030eb28342477693eb183a4ded4d2a6
CN = Microsoft Azure ECC TLS Issuing CA 05 Thumbprint: 4c15bc8d7aa5089a84f2ac4750f040d064040cd4
CN = Microsoft Azure ECC TLS Issuing CA 06 Thumbprint: dfeb65e575d03d0cc59fd60066c6d39421e65483
Expiration: Thursday, June 27, 2024 4:59:59 PM; Issuer = Microsoft ECC Root Certificate Authority 2017 O = Microsoft Corporation C = US
-------------------------------------------------------
CN = Microsoft Azure ECC TLS Issuing CA 01 Thumbprint: 92503d0d74a7d3708197b6ee13082d52117a6ab0
CN = Microsoft Azure ECC TLS Issuing CA 02 Thumbprint: 1e981ccddc69102a45c6693ee84389c3cf2329f1
CN = Microsoft Azure ECC TLS Issuing CA 05 Thumbprint: c6363570af8303cdf31c1d5ad81e19dbfe172531
CN = Microsoft Azure ECC TLS Issuing CA 06 Thumbprint: 7365adaedfea4909c1baadbab68719ad0c381163
Expiration: Thursday, June 27, 2024 4:59:59 PM; Issuer = DigiCert Global Root G3 O = DigiCert Inc C = US |
Recommended to prevent disruption from |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.