az lab vm list fails with an MSI error when running from CloudShell
See original GitHub issueDescribe the bug
Command Name
az lab vm list
Errors:
AzureResponseError: Failed to connect to MSI. Please make sure MSI is configured correctly.
Get Token request returned: <Response [400]>
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az lab vm list --lab-name {} --resource-group {}
Expected Behavior
I can see the list of VMs
Environment Summary
Linux-4.15.0-1106-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB
azure-cli 2.18.0
azure-cli-ml 1.20.0
Extensions:
azure-iot 0.10.8
ai-examples 0.2.5
azure-cli-ml 1.20.0
Additional Context
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Troubleshooting & Limitations of Azure Cloud Shell
Details: When creating a storage account through Cloud Shell, it's unsuccessful due to an Azure Policy assignment placed by your admin. The ...
Read more >Getting started with Azure CLI 2.0
The complete command will be “az group list -o table“. ... Another method of using the Azure CLI is by using the cloud...
Read more >Automating Infrastructure Deployments in the Cloud with ...
Using the Azure Resource Manager modules requires authenticating with the Azure API. In this lab, you will use Azure service principal for ...
Read more >azure-cli 2.24.2
Compute * Hotfix: Fix the bad request issue when creating VMSS in Azure Stack ... az labs create environment : Fix error creating...
Read more >Lab: Create and manage session host images (AD DS)
An Azure subscription you will be using in this lab. ... PowerShell session in the Cloud Shell pane, run the following to deploy...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello - I had the same error in Azure Cloud Shell. I have solved by executing “az login --tenant xxxx-xxxxxxxxxxxxxx-xxxxx” inside the shell.
However it is still an unexpected behaviour.
Same here! Locally it doesn’t work. But in the Azure Portal Cloud Shell 😃