Skip to content

Commit b34f9d7

Browse files
Merge pull request #287059 from jcjiang/patch-4
Update key-vault-certificates-manage.md
2 parents ff1ecbc + d0ba586 commit b34f9d7

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/container-apps/key-vault-certificates-manage.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,12 @@ You can set up Azure Key Vault to centrally manage your container app's TLS/SSL
1717

1818
An Azure Key Vault resource is required to store your certificate. See [Import a certificate in Azure Key Vault](/azure/key-vault/certificates/tutorial-import-certificate?tabs=azure-portal) or [Configure certificate auto-rotation in Key Vault](/azure/key-vault/certificates/tutorial-rotate-certificates) to create a Key Vault and add a certificate.
1919

20+
## Exceptions
21+
22+
While the majority of certificate types are supported, there are a few exceptions to keep in mind.
23+
- ECDSA p384 and p521 certificates are not supported.
24+
- Due to how App Services certificates are saved in Key Vault, they cannot be imported using the Azure Portal and require the Azure CLI.
25+
2026
## Enable managed identity for Container Apps environment
2127

2228
Azure Container Apps uses an environment level managed identity to access your Key Vault and import your certificate. To enable system-assigned managed identity, follow these steps:

0 commit comments

Comments
 (0)