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
Copy file name to clipboardExpand all lines: articles/key-vault/certificates/certificate-scenarios.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Get started with Key Vault certificates
3
-
description: The following scenarios outline several of the primary usages of Key Vault’s certificate management service including the additional steps required for creating your first certificate in your key vault.
3
+
description: Get started with Key Vault certificates management.
4
4
services: key-vault
5
5
author: msmbaldwin
6
6
ms.service: key-vault
@@ -12,9 +12,9 @@ ms.author: mbaldwin
12
12
---
13
13
14
14
# Get started with Key Vault certificates
15
-
The following scenarios outline several of the primary usages of Key Vault’s certificate management service including the additional steps required for creating your first certificate in your key vault.
15
+
This guideline helps you get started with certificate management in Key Vault.
16
16
17
-
The following are outlined:
17
+
List of scenarios covered here:
18
18
- Creating your first Key Vault certificate
19
19
- Creating a certificate with a Certificate Authority that is partnered with Key Vault
20
20
- Creating a certificate with a Certificate Authority that is not partnered with Key Vault
@@ -113,13 +113,14 @@ When you are importing the certificate, you need to ensure that the key is inclu
113
113
114
114
### Formats of Merge CSR we support
115
115
116
-
AKV supports 2 PEM based formats. You can either merge a single PKCS#8 encoded certificate or a base64 encoded P7B (chain of certificates signed by CA).
117
-
If you need to covert the P7B's format to the supported one, you can use [certutil -encode](/windows-server/administration/windows-commands/certutil#-encode)
116
+
Azure Key Vault supports PKCS#8 encoded certificate with below headers:
118
117
119
118
-----BEGIN CERTIFICATE-----
120
119
121
120
-----END CERTIFICATE-----
122
121
122
+
>[!Note]
123
+
> P7B (PKCS#7) signed certificates chain, commonly used by Certificate Authorities (CAs), is supported as long as is base64 encoded. You may use [certutil -encode](/windows-server/administration/windows-commands/certutil#-encode) to convert to supported format.
123
124
124
125
## Creating a certificate with a CA not partnered with Key Vault
125
126
This method allows working with other CAs than Key Vault's partnered providers, meaning your organization can work with a CA of its choice.
0 commit comments