You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuing the attempt to follow Deploy to Azure instructions, I was able to get past #8 but then hit another error when attempting to deploy.
Your device is required to be managed to access this resource
However, my device is managed.
I think this may have to do with the container. The host is not allowing the container to recognize that it is managed.
Error
╷
│ Error: building account: getting authenticated object ID: parsing json result from the Azure CLI: waiting for the Azure CLI: exit status 1: ERROR: AADSTS530003: Your device is required to be managed to access this resource. Trace ID: bb2c0ee3-51ee-4881-8f5d-c4a302f55300 Correlation ID: d4ca1f84-57e5-4a56-8467-8b6441f303c8 Timestamp: 2024-06-11 16:57:36Z
│ Interactive authentication is needed. Please run:
│ az login --scope https://graph.microsoft.com//.default
│
│ with provider["registry.terraform.io/hashicorp/azurerm"],
│ on main.tf line 13, in provider "azurerm":
│ 13: provider "azurerm" {
│
╵
I did run az login --scope https://graph.microsoft.com//.default but it prints out another message and doesn't succeed no effect.
Help us keep your device secure
Your sign-in was successful but your admin requires the device requesting access to be managed by Microsoft to access this resource.
Oddly, in the error details it even says: Device state: Compliant
🤔
The text was updated successfully, but these errors were encountered:
Continuing the attempt to follow Deploy to Azure instructions, I was able to get past #8 but then hit another error when attempting to deploy.
However, my device is managed.
I think this may have to do with the container. The host is not allowing the container to recognize that it is managed.
Error
I did run
az login --scope https://graph.microsoft.com//.default
but it prints out another message and doesn't succeed no effect.Oddly, in the error details it even says:
Device state: Compliant
🤔
The text was updated successfully, but these errors were encountered: