Merge pull request #235770 from jaesoni/disable-listener-update

Disable listener doc update

Author: v-regandowner

articles/application-gateway/disabled-listeners.md

@@ -5,7 +5,7 @@ description: The article explains the details of a disabled listener and ways to
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: troubleshooting
-ms.date: 02/22/2022
+ms.date: 04/25/2023
 ms.author: greglin
 
 ---
@@ -14,9 +14,9 @@ ms.author: greglin
 
 The SSL/TLS certificates for Azure Application Gateway’s listeners can be referenced from a customer’s Key Vault resource. Your application gateway must always have access to such linked key vault resource and its certificate object to ensure smooth operations of the TLS termination feature and the overall health of the gateway resource.
 
-It is important to consider any impact on your Application Gateway resource when making changes or revoking access to your Key Vault resource. In case your application gateway is unable to access the associated key vault or locate its certificate object, it will automatically put that listener in a disabled state. The action is triggered only for configuration errors. Transient connectivity problems do not have any impact on the listeners.
+It's important to consider any impact on your Application Gateway resource when making changes or revoking access to your Key Vault resource. In case your application gateway is unable to access the associated key vault or locate its certificate object, it will automatically put that listener in a disabled state. **The action is triggered only for configuration errors**. Any customer misconfigurations like deletion/disablement of certificates or prohibiting the application gateway's access through key vault's firewall or permissions cause the key vault-based HTTPS listener to get disabled. Transient connectivity problems don't have any impact on the listeners.
 
-A disabled listener doesn’t affect the traffic for other operational listeners on your Application Gateway. For example, the HTTP listeners or HTTPS listeners for which PFX certificate file is directly uploaded on Application Gateway resource will never go in a disabled state.
+A disabled listener doesn’t affect the traffic for other operational listeners on your Application Gateway. For example, the HTTP listeners or HTTPS listeners for which the PFX certificate file is directly uploaded on the Application Gateway resource are never disabled.
 
 [![An illustration showing affected listeners.](../application-gateway/media/disabled-listeners/affected-listener.png)](../application-gateway/media/disabled-listeners/affected-listener.png#lightbox)
 
@@ -35,7 +35,7 @@ Understanding the behavior of the Application Gateway’s periodic check and its
 
 [ ![Screenshot of client error will look.](../application-gateway/media/disabled-listeners/client-error.png) ](../application-gateway/media/disabled-listeners/client-error.png#lightbox)
 
-2. You can verify if the error is a result of a disabled listener on your gateway by checking your [Application Gateway’s Resource Health page](../application-gateway/resource-health-overview.md). You will see an event as shown below.
+2. You can verify if the client error results from a disabled listener on your gateway by checking your [Application Gateway’s Resource Health page](../application-gateway/resource-health-overview.md), as shown in the screenshot.
 
 ![A screenshot of user-driven resource health.](../application-gateway/media/disabled-listeners/resource-health-event.png)
 
@@ -44,7 +44,7 @@ You can narrow down to the exact cause and find steps to resolve the problem by
 1. Sign-in to your Azure portal
 1. Select Advisor
 1. Select Operational Excellence category from the left menu.
-1. You will find a recommendation titled **Resolve Azure Key Vault issue for your Application Gateway**, if your gateway is experiencing this issue. Ensure the correct Subscription is selcted from the drop-down options above.
+1. Find the recommendation titled **Resolve Azure Key Vault issue for your Application Gateway** (shown only if your gateway is experiencing this issue). Ensure the correct subscription is selected.
 1. Select it to view the error details and the associated key vault resource along with the [troubleshooting guide](../application-gateway/application-gateway-key-vault-common-errors.md) to fix your exact issue.
 
 > [!NOTE]