Skip to content

Commit 134b7e3

Browse files
authored
Update certificate-scenarios.md
1 parent 7335ffb commit 134b7e3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ Azure Key Vault supports PKCS#8 encoded certificate with below headers:
120120
-----END CERTIFICATE-----
121121

122122
>[!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.
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.
124124
125125
## Creating a certificate with a CA not partnered with Key Vault
126126
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)