Skip to content

Commit a35d56b

Browse files
Merge pull request #186130 from vhorne/ag-renew-certs
split into two sections for cert location
2 parents a2431c4 + bdabcac commit a35d56b

File tree

1 file changed

+21
-6
lines changed

1 file changed

+21
-6
lines changed

articles/application-gateway/renew-certificates.md

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: vhorne
66

77
ms.service: application-gateway
88
ms.topic: how-to
9-
ms.date: 01/20/2021
9+
ms.date: 01/25/2022
1010
ms.author: victorh
1111
ms.custom: devx-track-azurepowershell
1212
---
@@ -15,9 +15,22 @@ ms.custom: devx-track-azurepowershell
1515

1616
At some point, you'll need to renew your certificates if you configured your application gateway for TLS/SSL encryption.
1717

18-
You can renew a certificate associated with a listener using either the Azure portal, Azure PowerShell, or Azure CLI:
18+
There are two locations where certificates may exist: certificates stored in Azure Key Vault, or certificates uploaded to an application gateway.
1919

20-
## Azure portal
20+
## Certificates on Azure Key Vault
21+
22+
When Application Gateway is configured to use Key Vault certificates, its instances retrieve the certificate from Key Vault and install them locally for TLS termination. The instances poll Key Vault at four-hour intervals to retrieve a renewed version of the certificate if it exists. If an updated certificate is found, the TLS/SSL certificate that's currently associated with the HTTPS listener is automatically rotated.
23+
24+
> [!TIP]
25+
> Any change to Application Gateway will force a check against Key Vault to see if any new versions of certificates are available. This includes, but is not limited to, changes to Frontend IP Configurations, Listeners, Rules, Backend Pools, Resource Tags, and more. If an updated certificate is found, the new certificate will immediately be presented.
26+
27+
Application Gateway uses a secret identifier in Key Vault to reference the certificates. For Azure PowerShell, the Azure CLI, or Azure Resource Manager, we strongly recommend that you use a secret identifier that doesn't specify a version. This way, Application Gateway will automatically rotate the certificate if a newer version is available in your key vault. An example of a secret URI without a version is `https://myvault.vault.azure.net/secrets/mysecret/`.
28+
29+
## Certificates on an application gateway
30+
31+
Application Gateway supports certificate upload without the need to configure Azure Key Vault. To renew the uploaded certificates, use the following steps for the Azure portal, Azure PowerShell, or Azure CLI.
32+
33+
### Azure portal
2134

2235
To renew a listener certificate from the portal, navigate to your application gateway listeners.
2336
Select the listener that has a certificate that needs to be renewed, and then select **Renew or edit selected certificate**.
@@ -26,7 +39,7 @@ Select the listener that has a certificate that needs to be renewed, and then se
2639

2740
Upload your new PFX certificate, give it a name, type the password, and then select **Save**.
2841

29-
## Azure PowerShell
42+
### Azure PowerShell
3043

3144
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
3245

@@ -47,7 +60,7 @@ set-AzApplicationGatewaySSLCertificate -Name <oldcertname> `
4760
4861
Set-AzApplicationGateway -ApplicationGateway $appgw
4962
```
50-
## Azure CLI
63+
### Azure CLI
5164

5265
```azurecli-interactive
5366
az network application-gateway ssl-cert update \
@@ -58,6 +71,8 @@ az network application-gateway ssl-cert update \
5871
--cert-password "<password>"
5972
```
6073

74+
75+
6176
## Next steps
6277

63-
To learn how to configure TLS Offloading with Azure Application Gateway, see [Configure TLS Offload](./create-ssl-portal.md)
78+
To learn how to configure TLS Offloading with Azure Application Gateway, see [Configure TLS Offload](./create-ssl-portal.md).

0 commit comments

Comments
 (0)