Skip to content

Commit a6a628f

Browse files
authored
Merge pull request #103967 from winthrop28/patch-91
adding note with Portal limitation
2 parents e1de65e + b751b2a commit a6a628f

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/application-gateway/key-vault-certs.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,9 @@ Application Gateway integration with Key Vault offers many benefits, including:
2929

3030
Application Gateway currently supports software-validated certificates only. Hardware security module (HSM)-validated certificates are not supported. After Application Gateway is configured to use Key Vault certificates, its instances retrieve the certificate from Key Vault and install them locally for SSL termination. The instances also poll Key Vault at 24-hour intervals to retrieve a renewed version of the certificate, if it exists. If an updated certificate is found, the SSL certificate currently associated with the HTTPS listener is automatically rotated.
3131

32+
> [!NOTE]
33+
> The Azure portal only supports KeyVault Certificates, not secrets. Application Gateway still supports referencing secrets from KeyVault, but only through non-Portal resources like PowerShell, CLI, API, ARM templates, etc.
34+
3235
## How integration works
3336

3437
Application Gateway integration with Key Vault requires a three-step configuration process:

0 commit comments

Comments
 (0)