Skip to content

Commit d5d08fa

Browse files
Merge pull request #274942 from jlichwa/patch-112
Update certificate-scenarios.md
2 parents 0c9bc59 + 5890240 commit d5d08fa

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

articles/key-vault/certificates/certificate-scenarios.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
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.
44
services: key-vault
55
author: msmbaldwin
66
ms.service: key-vault
@@ -12,9 +12,9 @@ ms.author: mbaldwin
1212
---
1313

1414
# 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.
1616

17-
The following are outlined:
17+
List of scenarios covered here:
1818
- Creating your first Key Vault certificate
1919
- Creating a certificate with a Certificate Authority that is partnered with Key Vault
2020
- 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
113113
114114
### Formats of Merge CSR we support
115115

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:
118117

119118
-----BEGIN CERTIFICATE-----
120119

121120
-----END CERTIFICATE-----
122121

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.
123124
124125
## Creating a certificate with a CA not partnered with Key Vault
125126
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

Comments
 (0)