Move to troubleshooting

Author: bishal41

articles/iot-operations/troubleshoot/known-issues.md

@@ -17,8 +17,6 @@ This article lists the known issues for Azure IoT Operations.
 
 - If you prefer to have no updates made to your cluster without giving explicit consent, you should disable Arc updates when you enable the cluster. This is due to the fact that some system extensions are automatically updated by the Arc agent. To disable updates, include the `--disable-auto-upgrade` flag as part of the `az connectedk8s connect` command.
 
-- If your deployment fails with the `"code":"LinkedAuthorizationFailed"` error, it means that you don't have **Microsoft.Authorization/roleAssignments/write** permissions on the resource group that contains your cluster.
-
 - Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can break the secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience UI.
 
 - During and after deploying Azure IoT Operations, you might see warnings about `Unable to retrieve some image pull secrets (regcred)` in the logs and Kubernetes events. These warnings are expected and don't affect the deployment and use of Azure IoT Operations.

articles/iot-operations/troubleshoot/troubleshoot.md

@@ -23,6 +23,11 @@ For general deployment and configuration troubleshooting, you can use the Azure
 
 - Use [az iot ops support create-bundle](/cli/azure/iot/ops/support#az-iot-ops-support-create-bundle) to collect logs and traces to help you diagnose problems. The `support create-bundle` command creates a standard support bundle zip archive you can review or provide to Microsoft Support.
 
+### You see a "code":"LinkedAuthorizationFailed” error message
+If your deployment fails with the "code":"LinkedAuthorizationFailed" error, it indicates that the required permissions on the resource group containing the cluster are not available.
+
+To resolve this issue, ensure that **Microsoft.Authorization/roleAssignments/write** permissions are granted at the resource group level.
+
 ### You see an UnauthorizedNamespaceError error message
 
 If you see the following error message, you either didn't enable the required Azure-arc custom locations feature, or you enabled the custom locations feature with an incorrect custom locations RP OID.