edit pass: articles-about-ingress-for-aks

Author: ShawnJackson

articles/application-gateway/ingress-controller-disable-addon.md

@@ -1,6 +1,6 @@
 ---
 title: Disable and re-enable Application Gateway Ingress Controller add-on for Azure Kubernetes Service cluster
-description: This article provides information on how to disable and re-enable the AGIC add-on for your AKS cluster
+description: This article provides information on how to disable and re-enable the AGIC add-on for your AKS cluster.
 services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
@@ -9,34 +9,42 @@ ms.date: 9/17/2024
 ms.author: greglin
 ---
 
-# Disable and re-enable AGIC add-on for your AKS cluster
-Application Gateway Ingress Controller (AGIC) deployed as an AKS add-on allows you to enable and disable the add-on with one line in Azure CLI. The life cycle of the Application Gateway differs when you disable the AGIC add-on, depending on if the Application Gateway was created by the AGIC add-on, or if it was deployed separately from the AGIC add-on. You can run the same command to re-enable the AGIC add-on if you ever disable it, or to enable the AGIC add-on using an existing AKS cluster and Application Gateway.
+# Disable and re-enable the AGIC add-on for your AKS cluster
 
-> [!TIP]
-> Also see [What is Application Gateway for Containers](for-containers/overview.md).
+The Application Gateway Ingress Controller (AGIC) deployed as an Azure Kubernetes Service (AKS) add-on allows you to enable and disable the add-on with one line in the Azure CLI.
+
+The life cycle of the Azure Application Gateway instance differs when you disable the AGIC add-on, depending on if the Application Gateway was created by the AGIC add-on, or if it was deployed separately from the AGIC add-on. You can run the same command to re-enable the AGIC add-on if you ever disable it, or to enable the AGIC add-on using an existing AKS cluster and Application Gateway.
+
+## Disabling AGIC add-on with associated Application Gateway
 
-## Disabling AGIC add-on with associated Application Gateway 
 If the AGIC add-on automatically deployed the Application Gateway for you when you first set up everything, then disabling the AGIC add-on will by default delete the Application Gateway based on a couple criteria. There are two criteria that the AGIC add-on looks for to determine if it should delete the associated Application Gateway when you disable it:
-- Is the Application Gateway that the AGIC add-on is associated with deployed in the MC_* node resource group? 
-- Does the Application Gateway that the AGIC add-on is associated with have the tag "created-by: ingress-appgw"? The tag is used by AGIC to determine if the Application Gateway was deployed by the add-on or not. 
 
-If both criteria are met, then the AGIC add-on will delete the Application Gateway it created when the add-on is disabled; however, it won't delete the public IP or the subnet in which the Application Gateway was deployed with/in. If the first criteria isn't met, then it won't matter if the Application Gateway has the "created-by: ingress-appgw" tag - disabling the add-on won't delete the Application Gateway. Likewise, if the second criteria isn't met, that is. The Application Gateway lacks that tag, then disabling the add-on won't delete the Application Gateway in the MC_* node resource group. 
+- Is the Application Gateway that the AGIC add-on is associated with deployed in the MC_* node resource group?
+- Does the Application Gateway that the AGIC add-on is associated with have the tag "created-by: ingress-appgw"? The tag is used by AGIC to determine if the Application Gateway was deployed by the add-on or not.
 
-> [!TIP] 
-> If you don't want the Application Gateway to be deleted when disabling the add-on, but it meets both criteria then remove the "created-by: ingress-appgw" tag to prevent the add-on from deleting your Application Gateway. 
+If both criteria are met, then the AGIC add-on will delete the Application Gateway it created when the add-on is disabled; however, it won't delete the public IP or the subnet in which the Application Gateway was deployed with/in.
+
+If the first criteria isn't met, then it won't matter if the Application Gateway has the "created-by: ingress-appgw" tag - disabling the add-on won't delete the Application Gateway. Likewise, if the second criteria isn't met, that is. The Application Gateway lacks that tag, then disabling the add-on won't delete the Application Gateway in the MC_* node resource group.
+
+> [!TIP]
+> If you don't want the Application Gateway to be deleted when disabling the add-on, but it meets both criteria then remove the "created-by: ingress-appgw" tag to prevent the add-on from deleting your Application Gateway.
+
+To disable the AGIC add-on, run the following command:
 
-To disable the AGIC add-on, run the following command: 
 ```azurecli-interactive
 az aks disable-addons -n <AKS-cluster-name> -g <AKS-resource-group-name> -a ingress-appgw 
 ```
 
 ## Enable AGIC add-on on existing Application Gateway and AKS Cluster
+
 If you ever disable the AGIC add-on and need to re-enable the add-on, or want to enable the add-on using an existing Application Gateway and AKS cluster, then run the following command:
 
 ```azurecli-interactive
 appgwId=$(az network application-gateway show -n <application-gateway-name> -g <resource-group-name> -o tsv --query "id") 
 az aks enable-addons -n <AKS-cluster-name> -g <AKS-cluster-resource-group> -a ingress-appgw --appgw-id $appgwId
 ```
 
-## Next steps
-For more information on how to enable the AGIC add-on using an existing Application Gateway and AKS cluster, see [AGIC add-on brownfield deployment](tutorial-ingress-controller-add-on-existing.md).
+## Related content
+
+- For more information on how to enable the AGIC add-on using an existing Application Gateway and AKS cluster, see [AGIC add-on brownfield deployment](tutorial-ingress-controller-add-on-existing.md).
+- For information about Application Gateway for Containers, see [What is Application Gateway for Containers?](for-containers/overview.md).