Update unable-connect-azure-fleet-manager.md

Edit review per CI 8945

Author: przlplx

support/azure/kubernetes-fleet/unable-connect-azure-fleet-manager.md

@@ -1,6 +1,6 @@
 ---
-title: Unable to connect to Azure Fleet Manager
-description: This article provides guidance for when you’re unable to connect to Azure Fleet Manager.
+title: Can't connect to Azure Fleet Manager
+description: This article provides guidance for actions to take when you can't connect to Azure Fleet Manager.
 ms.date: 01/13/2026
 ms.author: jarrettr
 ms.reviewer: chiragpa, v-ryanberg 
@@ -9,46 +9,42 @@ ms.custom: sap:Other issue or questions related to Fleet manager
 ---
 # Unable to connect to Azure Fleet Manager
 
-This article provides guidance for when you’re unable to connect to Azure Fleet Manager.
+This article helps you resolve an issue that prevents you from connecting to Azure Fleet Manager.
 
 ## Symptoms
 
-You try to connect to Azure Fleet Manager by retrieving the kubeconfig file for the Fleet Manager hub cluster. You initially run this command: 
+You try to connect to Azure Fleet Manager by retrieving the kubeconfig file for the Fleet Manager hub cluster. You initially run the following command: 
 
 ```powershell
-
 az fleet get-credentials --resource-group \${GROUP} --name
-
 ```
 
-You then run this command:
+Then, you run the following command:
 
 ```powershell
-
 kubectl get pods
-
 ```
 
-On the Fleet Manager API server, you see a prompt asking you to enter a device code in another browser to authenticate.
+On the Fleet Manager API server, you're prompted to enter a device code in another browser to authenticate your identity.
 
-If your organization enforces Conditional Access policies that block device code flows, you might see something like the following message: “Your sign-in was successful but does not meet the criteria to access this resource. For example, you might be signing in from a browser, app, location, or an authentication flow that is restricted by your admin.”
+If your organization enforces Conditional Access policies that block device code flows, you might receive a message that resembles the following message:
 
-The following is an example of such a message:
+> Your sign-in was successful but does not meet the criteria to access this resource. For example, you might be signing in from a browser, app, location, or an authentication flow that is restricted by your admin.
+
+The following screenshot shows an example of this kind of message.
 
 :::image type="content" source="../media/unable-connect-azure-fleet-manager/no-access-message.png" alt-text="Example of Conditional Access blocking device code flow." lightbox="../media/unable-connect-azure-fleet-manager/no-access-message.png":::
 
 ## Cause
 
-The kubeconfig generated by `az fleet get-credentials` defaults to device code authentication. Conditional Access policies can block this flow, preventing access to the Fleet Manager API server.
+The kubeconfig file that's generated by the `az fleet get-credentials` command defaults to device code authentication. Conditional Access policies can block this flow and prevent access to the Fleet Manager API server.
 
 ## Resolution
 
-Convert the kubeconfig to use Azure CLI authentication instead of device code authentication with the following command:
+To resolve this issue, modify kubeconfig to use Azure CLI authentication instead of device code authentication. To make this change, run the following command:
 
 ```powershell
-
 kubelogin convert-kubeconfig -l azurecli
-
 ```
 
-This updates the kubeconfig so that it authenticates using your existing Azure CLI sign-in session, bypassing the device code prompt.
+This command updates the kubeconfig file so that it authenticates by using your existing Azure CLI sign-in session. This action bypasses the device code prompt.