Update known-issues-disconnected-operations.md

Author: ronmiab

azure-local/known-issues-disconnected-operations.md

@@ -22,7 +22,7 @@ These release notes update continuously, and we add critical issues that require
 
 Role-Based Access Control (RBAC) permissions on a newly created Azure Key Vault take up to 20 minutes to propagate. If you create the Azure Key Vault in the local portal and try to finish the cloud deployment, you might encounter permission issues when validating the cluster before deployment.
 
-- **Resolution**: Wait 20 minutes after you create the Azure Key Vault to finish deploying the cluster, or create the key vault ahead of time. Assign the managed identity for each node, the key vault admin, and the user deploying to the cloud explicit roles on the key vault: **Key Vault Secrets Officer** and **Key Vault Data Access Administrator**.
+**Mitigation**: Wait 20 minutes after you create the Azure Key Vault to finish deploying the cluster, or create the key vault ahead of time. Assign the managed identity for each node, the key vault admin, and the user deploying to the cloud explicit roles on the key vault: **Key Vault Secrets Officer** and **Key Vault Data Access Administrator**.
 
 Here's an example script. Modify and use this script to create the key vault ahead of time:
 
@@ -74,25 +74,25 @@ Write-Verbose "Wait 30 min before running cloud deployment from portal"
 
 ### Arc-initialization (node) fails with error code 42
 
-Error: When attempting to initialize an Arc-enabled node, you may encounter error code 42.
+When attempting to initialize an Arc-enabled node, you may encounter error code 42.
 
-Cause: Signing in with a service principal name (SPN) causes arc initialization to fail.
+**Cause**: Signing in with a service principal name (SPN) causes arc initialization to fail.
 
-Mitigation: Until the underlying issue is fixed, sign in to each Azure Local node by running `az login –use-device-code` instead of using a SPN.
+**Mitigation**: Until the underlying issue is fixed, sign in to each Azure Local node by running `az login –use-device-code` instead of using a SPN.
 
 ### Azure Local VMs (Arc VMs)
 
 #### Azure Resource Graph add or edit tags error
 
-Error: When adding or editing a tag on an Arc VM, you might see an Azure Resource Graph error.
+When adding or editing a tag on an Arc VM, you might see an Azure Resource Graph error.
 
-Mitigation: Use Azure Command-Line Interface (CLI) to add or edit tags for the resource.
+**Mitigation**: Use Azure Command-Line Interface (CLI) to add or edit tags for the resource.
 
 #### Start, restart, or delete buttons disabled after stopping VM
 
-Error: After you stop an Arc VM, the start, restart, and delete buttons in the Azure portal are disabled.
+After you stop an Arc VM, the start, restart, and delete buttons in the Azure portal are disabled.
 
-Mitigation: Refresh your browser and the page.
+**Mitigation**: Refresh your browser and the page.
 
 #### Unable to view the network interface or read properties on an Arc VM
 
@@ -102,11 +102,11 @@ Viewing the network interface or properties on an Arc VM in the portal isn't sup
 
 If the notification in the top right shows that the save operation is complete, you can ignore the unsaved message and continue navigating away. The VM size is updated.
 
-#### Error deleting a VM resource
+#### Deleting a VM resource
 
-Error: When you delete a VM from the portal, you might see the message ***Delete associated resource failed*** and ***Failed to delete the associated resource 'name' of type 'Network interface***.
+When you delete a VM from the portal, you might see the message ***Delete associated resource failed*** and ***Failed to delete the associated resource 'name' of type 'Network interface***.
 
-Mitigation: After you delete the VM, use the CLI to delete the associated network interface. Run this command:
+**Mitigation**: After you delete the VM, use the CLI to delete the associated network interface. Run this command:
 
 ```azurecli
 az stack-hci-vm network nic delete
@@ -118,7 +118,7 @@ az stack-hci-vm network nic delete
 
 In this release, you can only use an existing public key when creating an AKS cluster.
 
-Mitigation: To create an SSH key, use the following command-line tool and paste the public key in the UI:
+**Mitigation**: To create an SSH key, use the following command-line tool and paste the public key in the UI:
 
 ```powershell
 ssh-keygen -t rsa 
@@ -129,7 +129,7 @@ ssh-keygen -t rsa
 
 Updating or scaling a node pool from the portal is currently not supported.
 
-Mitigation: Use CLI to update or scale a node pool.
+**Mitigation**: Use the CLI to update or scale a node pool.
 
 ```azurecli
 az aksarc nodepool update
@@ -138,25 +138,25 @@ az aksarc nodepool scale
 
 #### Kubernetes cluster list empty under Azure Local (Kubernetes clusters)
 
-Error: When you navigate to Azure Local and click **Kubernetes clusters**, you might see an empty list of clusters.
+When you navigate to Azure Local and click **Kubernetes clusters**, you might see an empty list of clusters.
 
-Mitigation: Navigate to **Kubernetes** > **Azure Arc** in the left menu or using the search bar. Your clusters should appear in the list.
+**Mitigation**: Navigate to **Kubernetes** > **Azure Arc** in the left menu or using the search bar. Your clusters should appear in the list.
 
 #### Save Kubernetes service notification stuck
 
-Error: After updating to a newer version of Kubernetes, you might encounter a stuck notification, `Save Kubernetes service`.
+After updating to a newer version of Kubernetes, you might encounter a stuck notification, `Save Kubernetes service`.
 
-Mitigation: Navigate to the cluster view page and refresh it. Verify that the state is still upgrading or has completed. If it's completed, you can ignore the notification.
+**Mitigation**: Navigate to the cluster view page and refresh it. Verify that the state is still upgrading or has completed. If it's completed, you can ignore the notification.
 
 #### Activity log shows authentication issue
 
 Ignore the portal warning for this release.
 
 #### Microsoft Entra authentication with Kubernetes RBAC fails
 
-Error: When attempting to create a Kubernetes cluster with Entra authentication, you encounter an error.
+When attempting to create a Kubernetes cluster with Entra authentication, you encounter an error.
 
-Mitigation: Only local accounts with Kubernetes RBAC are supported in this preview.
+**Mitigation**: Only local accounts with Kubernetes RBAC are supported in this preview.
 
 #### Arc extensions
 
@@ -166,9 +166,9 @@ Arc extensions are unsupported in this release.
 
 #### AKS resource shows on portal after deletion
 
-Error: After successfully deleting an AKS cluster from portal the resource continues to show.
+After successfully deleting an AKS cluster from portal the resource continues to show.
 
-Mitigation: Use cli to delete and clean up the cluster. Run this command:
+**Mitigation**: Use the CLI to delete and clean up the cluster. Run this command:
 
 ```azurecli
 az aksarc delete
@@ -188,37 +188,37 @@ After you restart a node or the control plane VM, the system might take up to an
 
 After you create a new subscription as an operator, the subscription appears in the list as non-clickable and displays ***no access*** for the owner.
 
-Mitigation: Refresh your browser window.
+**Mitigation**: Refresh your browser window.
 
 ### Operator subscriptions view (timeout)
 
-Error: If you're signed in as an operator, you might see a timeout screen and be unable to view, list, or create subscriptions.
+If you're signed in as an operator, you might see a timeout screen and be unable to view, list, or create subscriptions.
 
-Cause: This issue happens when a subscription owner is deleted or isn't synced from the source identity system to the local control plane. When you try to view subscriptions, the process fails because the owner's identity isn't available.
+**Cause**: This issue happens when a subscription owner is deleted or isn't synced from the source identity system to the local control plane. When you try to view subscriptions, the process fails because the owner's identity isn't available.
 
-Mitigation: If the portal doesn't work, use Azure CLI or REST API to create and list subscriptions. To assign a different owner, use the REST API and enter the `subscriptionOwnerId` parameter when you create the subscription.
+**Mitigation**: If the portal doesn't work, use Azure CLI or REST API to create and list subscriptions. To assign a different owner, use the REST API and enter the `subscriptionOwnerId` parameter when you create the subscription.
 
 ### Azure CLI
 
 #### Manage clouds
 
-Error: When you use the `az cloud` commands, such as `az cloud register`, `az cloud show`, or `az cloud set`, you might encounter issues if you use uppercase letters in the cloud name.
+When you use the `az cloud` commands, such as `az cloud register`, `az cloud show`, or `az cloud set`, you might encounter issues if you use uppercase letters in the cloud name.
 
-Mitigation: Only use lowercase letters for cloud names in `az cloud` subcommands, such as `register`, `show`, or `set`.
+**Mitigation**: Only use lowercase letters for cloud names in `az cloud` subcommands, such as `register`, `show`, or `set`.
 
 #### Create subscriptions
 
 Azure CLI doesn't support providing `subscriptionOwnerId` for new subscriptions. This makes the operator the default owner of newly created subscriptions without a way of changing the owner currently.
 
-Mitigation: Use `az rest` to create subscriptions with a different owner if required to automate directly with different owner
+**Mitigation**: Use `az rest` to create subscriptions with a different owner if required to automate directly with different owner
 
 ### Azure Portal
 
 #### Signout fails
 
-Error: When you select Sign-out, the request doesn't work.
+When you select Sign-out, the request doesn't work.
 
-Mitigation: Close your browser, then go to the portal URL.
+**Mitigation**: Close your browser, then go to the portal URL.
 
 <!--### Deployment