You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Database for MySQL Single Server successfully completed the root certificate change on **February 15, 2021 (02/15/2021)**as part of standard maintenance and security best practices. This article gives you more details about the changes, the resources affected, and the steps needed to ensure that your application maintains connectivity to your database server.
16
+
Azure Database for MySQL Single Server as part of standard maintenance and security best practices will complete the root certificate change starting October 2022. This article gives you more details about the changes, the resources affected, and the steps needed to ensure that your application maintains connectivity to your database server.
17
17
18
18
> [!NOTE]
19
19
> This article applies to [Azure Database for MySQL - Single Server](single-server-overview.md) ONLY. For [Azure Database for MySQL - Flexible Server](../flexible-server/overview.md), the certificate needed to communicate over SSL is [DigiCert Global Root CA](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem)
@@ -79,7 +79,7 @@ To avoid interruption of your application's availability as a result of certif
79
79
In the future, after the new certificate is deployed on the server side, you can change your CA pem file to DigiCertGlobalRootG2.crt.pem.
80
80
81
81
> [!NOTE]
82
-
> Please don't drop or alter **Baltimore certificate** until the cert change is made. We'll send a communication after the change is done, and then it will be safe to drop the **Baltimore certificate**.
82
+
> Please don't drop or alter **Baltimore certificate** until the cert change is made. We'll send a communication after the change is done and then it will be safe to drop the **Baltimore certificate**.
83
83
84
84
#### What if we removed the BaltimoreCyberTrustRoot certificate?
85
85
@@ -89,7 +89,24 @@ You'll start to encounter connectivity errors while connecting to your Azure Dat
89
89
90
90
#### If I'm not using SSL/TLS, do I still need to update the root CA?
91
91
92
-
No actions are required if you aren't using SSL/TLS.
92
+
No actions are required if you aren't using SSL/TLS.
93
+
94
+
#### When will my single server instance undergo root certificate change?
95
+
96
+
The migration from **BaltimoreCyberTrustRoot** to **DigiCertGlobalRootG2** will be carried out across all regions of Azure starting **October 2022** in phases.
97
+
To make sure that you do not lose connectivity to your server, follow the steps mentioned under [Create a combined CA certificate](#create-a-combined-ca-certificate).
98
+
Combined CA certificate will allow connectivity over SSL to your single server instance with either of these two certificates.
99
+
100
+
101
+
#### When can I remove BaltimoreCyberTrustRoot certificate completely?
102
+
103
+
Once the migration is completed successfully across all Azure regions we'll send a communication post that you're safe to change single CA **DigiCertGlobalRootG2** certificate.
104
+
105
+
106
+
#### I don't specify any CA cert while connecting to my single server instance over SSL, do I still need to perform [the steps](#create-a-combined-ca-certificate) mentioned above?
107
+
108
+
If you have both the CA root cert in your [trusted root store](/windows-hardware/drivers/install/trusted-root-certification-authorities-certificate-store), then no further actions are required. This also applies to your client drivers that use local store for accessing root CA certificate.
109
+
93
110
94
111
#### If I'm using SSL/TLS, do I need to restart my database server to update the root CA?
95
112
@@ -126,10 +143,6 @@ For a connector using Self-hosted Integration Runtime where you explicitly inclu
126
143
127
144
No. Since the change is only on the client side to connect to the database server, there's no maintenance downtime needed for the database server for this change.
128
145
129
-
#### If I create a new server after February 15, 2021 (02/15/2021), will I be impacted?
130
-
131
-
For servers created after February 15, 2021 (02/15/2021), you will continue to use the [BaltimoreCyberTrustRoot](https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem) for your applications to connect using SSL.
132
-
133
146
#### How often does Microsoft update their certificates or what is the expiry policy?
134
147
135
148
These certificates used by Azure Database for MySQL are provided by trusted Certificate Authorities (CA). So the support of these certificates is tied to the support of these certificates by CA. The [BaltimoreCyberTrustRoot](https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem) certificate is scheduled to expire in 2025 so Microsoft will need to perform a certificate change before the expiry. Also in case if there are unforeseen bugs in these predefined certificates, Microsoft will need to make the certificate rotation at the earliest similar to the change performed on February 15, 2021 to ensure the service is secure and compliant at all times.
0 commit comments