Skip to content

Commit 7335ffb

Browse files
authored
Update certificate-scenarios.md
1 parent 82e016b commit 7335ffb

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -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` 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)