Images

Author: baanders

articles/digital-twins/media/troubleshoot-known-issues/event-route-need-permission.png

@@ -19,7 +19,7 @@ This article provides information about known issues associated with Azure Digit
 
 | Does this affect me? | Cause | Resolution |
 | --- | --- | --- |
-| For Azure Digital Twins specifically, this affects the following command groups:<br>`az dt route`<br>`az dt model`<br>`az dt twin` | This is the result of a known issue in Cloud Shell: [*Getting token from Cloud Shell intermittently fails with 400 Client Error: Bad Request*](https://github.com/Azure/azure-cli/issues/11749).<br><br>This presents a problem with Azure Digital Twins instance auth tokens and the Cloud Shell's default [managed identity](../active-directory/managed-identities-azure-resources/overview.md) based authentication. The troubleshooting step of running `az login` switches you out of managed identity authentication, thus stepping over this problem.<br><br>This doesn't affect Azure Digital Twins commands from the `az dt` or `az dt endpoint` command groups, because they use a different type of authentication token (ARM-based), which doesn't have an issue with the Cloud Shell's managed identity authentication. | This can be resolved by rerunning the `az login` command in Cloud Shell and completing subsequent login steps. After this, you should be able to rerun the command.<br><br>Alternatively, you can open the Cloud Shell pane in the Azure portal and complete your Cloud Shell work from there.<br><br>Finally, another solution is to [install the Azure CLI](/cli/azure/install-azure-cli?view=azure-cli-latest&preserve-view=true) on your machine so you can run Azure CLI commands locally. The local CLI does not experience this issue. |
+| For Azure Digital Twins specifically, this affects the following command groups:<br>`az dt route`<br>`az dt model`<br>`az dt twin` | This is the result of a known issue in Cloud Shell: [*Getting token from Cloud Shell intermittently fails with 400 Client Error: Bad Request*](https://github.com/Azure/azure-cli/issues/11749).<br><br>This presents a problem with Azure Digital Twins instance auth tokens and the Cloud Shell's default [managed identity](../active-directory/managed-identities-azure-resources/overview.md) based authentication. The troubleshooting step of running `az login` switches you out of managed identity authentication, thus stepping over this problem.<br><br>This doesn't affect Azure Digital Twins commands from the `az dt` or `az dt endpoint` command groups, because they use a different type of authentication token (ARM-based), which doesn't have an issue with the Cloud Shell's managed identity authentication. | This can be resolved by rerunning the `az login` command in Cloud Shell and completing subsequent login steps. After this, you should be able to rerun the command.<br><br>Alternatively, you can open the Cloud Shell pane in the Azure portal and complete your Cloud Shell work from there.<img src="media/troubleshoot-known-issues/portal-launch-icon.png" alt="Image of the Cloud Shell icon in the Azure portal icon bar."/><br><br>Finally, another solution is to [install the Azure CLI](/cli/azure/install-azure-cli?view=azure-cli-latest&preserve-view=true) on your machine so you can run Azure CLI commands locally. The local CLI does not experience this issue. |
 
 ## Missing role assignment after scripted setup