Skip to content

Commit b5a8dfa

Browse files
authored
Merge pull request #94629 from winthrop28/patch-63
removing preview tag
2 parents 4a3b2db + ab18b7d commit b5a8dfa

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

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

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,9 @@ ms.author: victorh
1111

1212
# SSL termination with Key Vault certificates
1313

14-
[Azure Key Vault](../key-vault/key-vault-overview.md) is a platform-managed secret store that you can use to safeguard secrets, keys, and SSL certificates. Azure Application Gateway supports integration with Key Vault (in public preview) for server certificates that are attached to HTTPS-enabled listeners. This support is limited to the v2 SKU of Application Gateway.
14+
[Azure Key Vault](../key-vault/key-vault-overview.md) is a platform-managed secret store that you can use to safeguard secrets, keys, and SSL certificates. Azure Application Gateway supports integration with Key Vault for server certificates that are attached to HTTPS-enabled listeners. This support is limited to the v2 SKU of Application Gateway.
1515

16-
> [!IMPORTANT]
17-
> Integration of Application Gateway with Key Vault is currently in public preview. This preview is provided without a service-level agreement (SLA) and isn't recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
18-
19-
This public preview offers two models for SSL termination:
16+
Key Vault integration offers two models for SSL termination:
2017

2118
- You can explicitly provide SSL certificates attached to the listener. This model is the traditional way to pass SSL certificates to Application Gateway for SSL termination.
2219
- You can optionally provide a reference to an existing Key Vault certificate or secret when you create an HTTPS-enabled listener.

0 commit comments

Comments
 (0)