Skip to content

Commit f2afeba

Browse files
authored
Update application-gateway-key-vault-common-errors.md
1 parent 1c514aa commit f2afeba

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/application-gateway-key-vault-common-errors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: jaysoni
1212

1313
# Common key vault errors in Azure Application Gateway
1414

15-
For using TLS certificate with HTTPS listeners on your Application Gateway, you can provide a reference to an existing Key Vault resource. When using such an integration, it is important that the gateway always has access to the linked key vault resource to ensure smooth operations of the TLS termination feature and maintain the overall health of your gateway. Failure to do so will automatically put that HTTPS listener in a disabled state. [Learn more](../application-gateway/disabled-listeners.md).
15+
Application Gateway enables customers to securely store TLS certificates in Azure Key Vault. When using a Key Vault resource, it is important that the gateway always has access to the linked key vault. If your Application Gateway is unable to fetch the certificate, the associated HTTPS listeners will be placed in a disabled state. [Learn more](../application-gateway/disabled-listeners.md).
1616

1717
This article helps you understand the details of key vault error codes you might encounter, including what is causing these errors. This article also contains steps to resolve such misconfigurations.
1818

0 commit comments

Comments
 (0)