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
Revise Azure root CA import instructions for SQL Server (#35573)
* Revise Azure root CA import instructions for SQL Server
Updated the instructions for importing Azure-trusted root CA keys to SQL Server, including changes to certificate names and paths. Added a note about the certification path for SQL Managed Instance public key certificates.
---------
Co-authored-by: Masha Thomas (MSFT) <32783170+MashaMSFT@users.noreply.github.com>
### Import Azure-trusted root certificate authority keys to SQL Server
321
321
322
-
Importing Azure-trusted root certificate authority (CA) keys to SQL Server is required for your SQL Server to trust the SQL managed instance certificates issued by Azure.
322
+
Importing Azure-trusted root certificate authority (CA) keys to SQL Server is required for your SQL Server to trust the SQL Managed Instance public key certificates issued by Azure.
323
323
324
-
You can download the necessary root CA certificates from [Root Certificate Authorities](/azure/security/fundamentals/azure-ca-details?tabs=root-and-subordinate-cas-list). Save it locally, such as to the sample `C:\Path\To\<name of certificate>.crt` path, and then import the certificate from that path.
325
-
326
-
327
-
First, import the *DigiCert Global Root CA* root-authority certificate to SQL Server:
328
-
329
-
```sql
330
-
-- Run on SQL Server
331
-
-- Import DigiCertGlobalRootCA root-authority certificate (trusted by Azure), if not already present
332
-
IF NOT EXISTS (SELECT name FROMsys.certificatesWHERE name = N'DigiCertGlobalRootCA')
Then, import the *DigiCert TLS ECC P384 Root G5* root-authority certificate to SQL Server:
324
+
You can download the necessary root CA keys from [Root Certificate Authorities](/azure/security/fundamentals/azure-ca-details?tabs=root-and-subordinate-cas-list). Save them locally, such as to the sample `C:\Path\To\<name of certificate>.crt` path, and then import the certificates from that path:
391
325
392
326
```sql
393
327
-- Run on SQL Server
394
-
-- Import DigiCertTLSECCP384RootG5 root-authority certificate (trusted by Azure), if not already present
395
-
IF NOT EXISTS (SELECT name FROMsys.certificatesWHERE name = N'DigiCertTLSECCP384RootG5')
328
+
-- Import <name of certificate> root-authority certificate (trusted by Azure), if not already present
329
+
IF NOT EXISTS (SELECT name FROMsys.certificatesWHERE name = N'<name of certificate>')
PRINT 'Certificate Microsoft RSA Root Certificate Authority 2017 already exists.'
341
+
PRINT 'Certificate <name of certificate> already exists.'
471
342
GO
472
343
```
473
344
345
+
> [!NOTE]
346
+
> The root certificate in the certification path for a SQL Managed Instance public key certificate is issued by an Azure trusted root Certificate Authority (CA). The specific root CA can change over time as Azure updates its trusted CA list.
347
+
> For a simplified setup, install all root CA certificates listed in [Azure Root Certificate Authorities](/azure/security/fundamentals/azure-ca-details?tabs=root-and-subordinate-cas-list). You can install just the required CA key by identifying the issuer of a previously-imported SQL Managed Instance public key.
348
+
474
349
Finally, verify all the created certificates by using the following dynamic management view (DMV):
0 commit comments