add permissions info to troubleshooting

Author: kgremban

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

@@ -23,7 +23,7 @@ Cloud resources:
 
 * Azure access permissions. At a minimum, have **Contributor** permissions in your Azure subscription. Depending on the deployment method and feature flag status you select, you may also need **Microsoft/Authorization/roleAssignments/write** permissions. If you *don't* have role assignment write permissions, take the following additional steps when deploying:
 
-  * If deploying with an Azure Resource Manager template, set the `deployResourceSyncRules` parameter set to `false`.
+  * If deploying with an Azure Resource Manager template, set the `deployResourceSyncRules` parameter to `false`.
   * If deploying with the Azure CLI, include the `--disable-rsync-rules`.
 
 * An [Azure Key Vault](../../key-vault/general/overview.md) that has the **Permission model** set to **Vault access policy**. You can check this setting in the **Access configuration** section of an existing key vault.

articles/iot-operations/troubleshoot/troubleshoot.md

@@ -25,6 +25,15 @@ 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.
 
+### Linked authorization failed error
+
+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.
+
+To resolve this issue, either request the required permissions or make the following adjustments to your deployment steps:
+
+  * If deploying with an Azure Resource Manager template, set the `deployResourceSyncRules` parameter to `false`.
+  * If deploying with the Azure CLI, include the `--disable-rsync-rules` flag with the [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command.
+
 ## Data Processor pipeline deployment status is failed
 
 Your Data Processor pipeline deployment status is showing as **Failed**.