Update troubleshoot-dns-load-balancing.md

Edit review per CI 5910

Author: przlplx

support/azure/kubernetes-fleet/networking/troubleshoot-dns-load-balancing.md

@@ -1,5 +1,5 @@
 ---
-title: Troubleshoot Azure Kubernetes Fleet Manager DNS load balancing
+title: Troubleshoot Azure Kubernetes Fleet Manager DNS Load Balancing
 description: Troubleshoot errors that occur when using DNS load balancing in Azure Kubernetes Fleet Manager.
 author: sjwaight
 ms.author: simonwaight
@@ -9,24 +9,24 @@ ms.date: 05/13/2025
 
 # Troubleshoot Azure Kubernetes Fleet Manager DNS load balancing
 
-This article provides troubleshooting information for Azure Kubernetes Fleet Manager's DNS-based load balancing. Fleet Manager DNS load balancing uses Azure Traffic Manager to balance traffic across public endpoints from multiple AKS member clusters.
+This article provides troubleshooting information for Azure Kubernetes Fleet Manager DNS-based load balancing. Fleet Manager DNS load balancing uses Azure Traffic Manager to balance traffic across public endpoints from multiple AKS member clusters.
 
 ## Use Fleet Manager hub cluster to troubleshoot
 
 1. User should have access to the Azure subscription and resource group where the Azure Traffic Manager profile is created.
-2. [Install or upgrade Azure CLI](/cli/azure/install-azure-cli) to version 2.72.0 or later.
+2. [Install or upgrade to Azure CLI](/cli/azure/install-azure-cli) version 2.72.0 or a later version.
 3. Make sure that the Kubernetes [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/) command-line tool is installed. You can install kubectl by running the [az aks install-cli](/cli/azure/aks#az-aks-install-cli) command.
-4. Install the **fleet** Azure CLI extension using the `az extension add`command, making sure your version is at least 1.5.2.
+4. Install the **fleet** Azure CLI extension by using the `az extension add`command. Make sure that your installed version is at least 1.5.2.
 
     ```azurecli-interactive
     az extension add --name fleet
     ```
 
-5. Access to the Fleet Manager hub cluster Kubernetes API. For more information, see [Access the Fleet Manager hub cluster API](/azure/kubernetes-fleet/access-fleet-hub-cluster-kubernetes-api).
+5. Access the Fleet Manager hub cluster Kubernetes API. For more information, see [Access the Fleet Manager hub cluster API](/azure/kubernetes-fleet/access-fleet-hub-cluster-kubernetes-api).
 
 ## Scenario 1: TrafficManagerProfile or Traffic Manager can't be created
 
-This section provides common reasons and solutions for the `TrafficManagerProfile` Kubernetes object and its associated Azure Traffic Manager resource not being created scenarios.
+This section provides common reasons and solutions for scenarios in which the `TrafficManagerProfile` Kubernetes object and its associated Azure Traffic Manager resource aren't created.
 
 To determine the appropriate resolution, check the status of the `TrafficManagerProfile` object on the Fleet Manager hub cluster for the error message.
 
@@ -36,13 +36,13 @@ kubectl get trafficmanagerprofile -n <namespace> <profile-name> -o yaml
 
 ### Error 1: The client does not have authorization to perform action 
 
-This issue may occur if one of the following conditions is met:
+This issue might occur if one of the following conditions is met:
 
-* A nonexistent Azure resource group was specified in the `TrafficManagerProfile` manifest.
-* The resource group isn't the same Azure Subscription as the Fleet Manager resource.
+* A nonexistent Azure resource group is specified in the `TrafficManagerProfile` manifest.
+* The resource group doesn't have the same Azure Subscription value that the Fleet Manager resource has.
 * The Fleet Manager hub cluster identity doesn't have permission to create and manage Azure Traffic Manager profiles in the specified resource group.
 
-You can check The `TrafficManagerProfile` status for details of the error. The following is the example of the `TrafficManagerProfile` status that shows the insufficient permissions issue.
+You can check The `TrafficManagerProfile` status for details of the error. The following example of the `TrafficManagerProfile` status shows insufficient permissions:
 
 ```yml
 status:
@@ -74,14 +74,14 @@ status:
 
 To resolve this issue, follow these steps:
 
-1. Ensure the Azure resource group exists and is the same Azure Subscription as the Fleet Manager.
-2. Check the Fleet Manager hub cluster identity has been granted the `Traffic Manager Contributor` role scoped to the resource group. For more information, see [Configure Fleet Manager permissions](/azure/kubernetes-fleet/howto-dns-load-balancing#configure-fleet-manager-permissions).
+1. Make sure that the Azure resource group exists and has the same Azure Subscription value that the Fleet Manager has.
+2. Verify that the Fleet Manager hub cluster identity is granted the `Traffic Manager Contributor` role scoped to the resource group. For more information, see [Configure Fleet Manager permissions](/azure/kubernetes-fleet/howto-dns-load-balancing#configure-fleet-manager-permissions).
 
 ### Error 2: Domain name is not available
 
-This issue may occur if the DNS prefix generated is already in use by another Azure Traffic Manager profile. The DNS prefix consists of the namespace and the `metadata.name` field in the `TrafficManagerProfile` manifest. For example, if the namespace is `team-a` and the `metadata.name` is `webapp`, the DNS prefix would `team-a-webapp`.
+This issue might occur if the generated DNS prefix is already used by another Azure Traffic Manager profile. The DNS prefix consists of the namespace and the `metadata.name` field in the `TrafficManagerProfile` manifest. For example, if the namespace is `team-a` and the `metadata.name` is `webapp`, the DNS prefix is `team-a-webapp`.
 
-The following is the example of the `TrafficManagerProfile` status that shows the Domain name is not available issue.
+The following example of the `TrafficManagerProfile` status shows that the Domain name is not available:
 
 ```yml
 status:
@@ -96,16 +96,16 @@ status:
 
 #### Solution
 
-To resolve this issue, use `nslookup` or a similar tool to check if the full DNS name ( for example `team-a-webapp.trafficmanager.net`) is available.  If it‘s not available, consider one of the following solutions:
+To resolve this issue, use `nslookup` or a similar tool to determine whether the full DNS name (for example, `team-a-webapp.trafficmanager.net`) is available. If the name is not available, consider one of the following alternative solutions:
 
 - Change the `metadata.name` field in the `TrafficManagerProfile` manifest to a unique name.
-- Use a different namespace for the `TrafficManagerProfile` manifest. This impacts the `TrafficManagerBackend` and `ServiceExport` objects, which must be in the same namespace.
+- Use a different namespace for the `TrafficManagerProfile` manifest. This affects the `TrafficManagerBackend` and `ServiceExport` objects. These objects must be in the same namespace.
 
 ### Error 3: Azure Traffic Manager subscription limits reached
 
-This issue may occur if more than 200 Traffic Manager Profiles or Endpoints within a single Azure Subscription.
+This issue might occur if more than 200 Traffic Manager Profiles or Endpoints exist within a single Azure Subscription.
 
-The following is the example of the `TrafficManagerProfile` status that shows the Azure Traffic Manager profile limits reached issue.
+The following example of the `TrafficManagerProfile` status shows that the Azure Traffic Manager profile limits are reached:
 
 ```yml
 status:
@@ -119,13 +119,13 @@ status:
 ```
 #### Solution
 
-Consider to delete unused profiles or requesting an increase in the limit. For more information, see [Azure Traffic Manager limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-traffic-manager-limits).
+Consider deleting unused profiles or requesting an increase in the limit. For more information, see [Azure Traffic Manager limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-traffic-manager-limits).
 
 ### Error 4: Azure Traffic Manager returns an error
 
-This issue may occur if the Azure Traffic Manager service returns an error when creating the profile.
+This issue might occur if the Azure Traffic Manager service returns an error when creating the profile.
 
-The following is the example of the `TrafficManagerProfile` status that shows this error.
+The following example of the `TrafficManagerProfile` status shows this error:
 
 ```yml
 status:
@@ -144,17 +144,17 @@ If the error persists, check the Azure Traffic Manager service health.
 
 ## Scenario 2: TrafficManagerBackend can't be created
 
-This section provides common causes and recommended solutions for scenarios that the `TrafficManagerBackend` Kubernetes can't be created.
+This section provides common causes and recommended solutions for scenarios in which the `TrafficManagerBackend` Kubernetes object can't be created.
 
-To determine the appropriate resolution, check the status of the `TrafficManagerBackend` object on the Fleet Manager hub cluster for the error message.
+To determine the appropriate resolution, check the status of the `TrafficManagerBackend` object on the Fleet Manager hub cluster for the following error message:
 
 ```bash
 kubectl get trafficmanagerbackend -n <namespace> <backend-name> -o yaml
 ```
 
 ### Error 1: TrafficManagerProfile is not found or Invalid trafficManagerProfile
 
-This issue may occur if one of the following conditions is met:
+This issue might occur if one of the following conditions is met:
 
 - The `TrafficManagerBackend` was created in a different namespace than the `TrafficManagerProfile`.
 - The `TrafficManagerProfile` object exists, but the associated Azure Traffic Manager resource couldn't be found.
@@ -190,20 +190,20 @@ status:
 
 To resolve this issue, follow these steps:
 
-1. Make sure to create the `TrafficManagerBackend` in the same namespace as the `TrafficManagerProfile`.
-2. Ensure that the `Programmed` condition of `TrafficManagerProfile` is `Accepted`. If not, check the profile definition for validity and resubmit.
-3. Ensure the Azure Traffic Manager resource exists. To recreate the resource, delete the `TrafficManagerProfile` from the Fleet Manager hub cluster and reapply it.
+1. Make sure that you create the `TrafficManagerBackend` in the same namespace as the `TrafficManagerProfile`.
+2. Make sure that the `Programmed` condition of `TrafficManagerProfile` is `Accepted`. If it's not, check the profile definition for validity, and then resubmit.
+3. Make sure the Azure Traffic Manager resource exists. To re-create the resource, delete the `TrafficManagerProfile` from the Fleet Manager hub cluster. and then reapply it.
 
 ### Error 2: Invalid Service or ServiceExport
 
-This issue may occur if one of the following conditions is met:
+This issue might occur if one of the following conditions is met:
 
-- The `Service` was created in a different namespace than the `TrafficManagerBackend`.
-- The `Service` exists, but the `ServiceExport` was not created in the same namespace as the `TrafficManagerBackend`.
+- The `Service` was created in a different namespace than the `TrafficManagerBackend` object.
+- The `Service` exists, but the `ServiceExport` object wasn't created in the same namespace as `TrafficManagerBackend`.
 - The `Service` isn't defined as a `LoadBalancer` type.
-- The `Service` isn't exposed via an Azure public IP address or doesn't have a DNS name assigned.
+- The `Service` isn't exposed through an Azure public IP address or doesn't have a DNS name assigned.
 
-The following are the examples of the `TrafficManagerBackend` status that shows the errors:
+The following examples of the `TrafficManagerBackend` status show the errors:
 
 ```yml
 status:
@@ -216,7 +216,7 @@ conditions:
   type: Accepted
 ```
 
-The `Service` is not defined as a `LoadBalancer` type.
+The `Service` is not defined as a `LoadBalancer` type:
 
 ```yml
 status:
@@ -235,17 +235,17 @@ conditions:
 
 To resolve this issue, follow these steps:
 
-1. Ensure at least one `Service` of a member cluster is exported in the same namespace of the `TrafficManagerBackend` by creating `ServiceExport`.
-2. Ensure that the exported `Service` is load balancer type and exposed via an Azure public IP address, which must have a DNS name assigned to be used in a Traffic Manager profile.
+1. Make sure that at least one `Service` of a member cluster is exported in the same namespace of the `TrafficManagerBackend` object by creating `ServiceExport`.
+2. Make sure that the exported `Service` is a load balancer type and is exposed through an Azure public IP address. This address must have an assigned DNS name to be used in a Traffic Manager profile.
 
 ### Error 3: Azure Traffic Manager profile is not found
 
-This issue may occur if one of the following conditions is met:
+This issue might occur if one of the following conditions is met:
 
-- The `TrafficManagerProfile` was object exists, but the associated Azure Traffic Manager resource couldn't be found.
+- The `TrafficManagerProfile` object exists, but the associated Azure Traffic Manager resource isn't found.
 - The Fleet Manager hub cluster identity doesn't have permission to create and manage Azure Traffic Manager profiles or endpoints in the specified resource group.
 
-The following is the example of the `TrafficManagerBackend` status that shows the error:
+The following example of the `TrafficManagerBackend` status shows the error:
 
 ```yml
 status:
@@ -262,12 +262,12 @@ conditions:
 
 To resolve this issue, follow these steps:
 
-1. Ensure the Azure Traffic Manager resource exists. To recreate the resource, delete the `TrafficManagerProfile` from the Fleet Manager hub cluster and reapply it.
-2. Check the Fleet Manager hub cluster identity has been granted the `Traffic Manager Contributor` role scoped to the resource group. For more information, see [Configure Fleet Manager permissions](/azure/kubernetes-fleet/howto-dns-load-balancing#configure-fleet-manager-permissions).
+1. Make sure that the Azure Traffic Manager resource exists. To re-create the resource, delete the `TrafficManagerProfile` profile from the Fleet Manager hub cluster, and then reapply it.
+2. Verify that the Fleet Manager hub cluster identity was granted the `Traffic Manager Contributor` role that's scoped to the resource group. For more information, see [Configure Fleet Manager permissions](/azure/kubernetes-fleet/howto-dns-load-balancing#configure-fleet-manager-permissions).
 
 ### Error 4: Azure Traffic Manager profile limits reached
 
-This issue may occur if more than 200 Azure Traffic Manager Endpoints would be created within a single Azure Subscription.
+This issue might occur if more than 200 Azure Traffic Manager Endpoints would be created within a single Azure subscription.
 
 The following is the example of the `TrafficManagerBackend` status that shows the error:
 
@@ -292,7 +292,7 @@ In addition to querying the Fleet Manager hub cluster, you can use Azure Log Ana
 
 ### TrafficManagerProfile
 
-Filter entries in the `fleet-hub-net-controller-manager` category using `trafficmanagerprofile/controller.go`.
+Filter the entries in the `fleet-hub-net-controller-manager` category by using `trafficmanagerprofile/controller.go`:
 
 ```kusto
 AzureDiagnostics
@@ -305,7 +305,7 @@ AzureDiagnostics
 
 ### TrafficManagerBackend
 
-Filter entries in the `fleet-hub-net-controller-manager` category using `trafficmanagerbackend/controller.go`.
+Filter the entries in the `fleet-hub-net-controller-manager` category by using `trafficmanagerbackend/controller.go`:
 
 ```kusto
 AzureDiagnostics