Skip to content

Commit def6206

Browse files
authored
Merge pull request #233308 from JackStromberg/patch-108
Updating keyvault steps
2 parents 7f249e2 + 50ac1a0 commit def6206

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Application Gateway uses a secret identifier in Key Vault to reference the certi
4040

4141
The Azure portal supports only Key Vault certificates, not secrets. Application Gateway still supports referencing secrets from Key Vault, but only through non-portal resources like PowerShell, the Azure CLI, APIs, and Azure Resource Manager templates (ARM templates).
4242

43-
References to Key Vaults in other Azure subscriptions is supported, but must be configured via ARM Template, Azure PowerShell, CLI, Bicep, etc. Cross-subscription key vault configuration is not supported by Application Gateway via Azure Portal today.
43+
References to Key Vaults in other Azure subscriptions are supported, but must be configured via ARM Template, Azure PowerShell, CLI, Bicep, etc. Cross-subscription key vault configuration is not supported by Application Gateway via Azure portal today.
4444

4545
## Certificate settings in Key Vault
4646

@@ -85,7 +85,7 @@ When you're using a restricted Key Vault, use the following steps to configure A
8585
8686
1. In the Azure portal, in your Key Vault, select **Networking**.
8787
1. On the **Firewalls and virtual networks** tab, select **Selected networks**.
88-
1. For **Virtual networks**, select **+ Add existing virtual networks**, and then add the virtual network and subnet for your Application Gateway instance. During the process, also configure the `Microsoft.KeyVault` service endpoint by selecting its checkbox.
88+
1. For **Virtual networks**, select **+ Add existing virtual networks**, and then add the virtual network and subnet for your Application Gateway instance. If prompted, ensure the _Do not configure 'Microsoft.KeyVault' service endpoint(s) at this time_ checkbox is unchecked to ensure the `Microsoft.KeyVault` service endpoint is enabled on the subnet.
8989
1. Select **Yes** to allow trusted services to bypass the Key Vault's firewall.
9090

9191
![Screenshot that shows selections for configuring Application Gateway to use firewalls and virtual networks.](media/key-vault-certs/key-vault-firewall.png)

0 commit comments

Comments
 (0)