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
Describe the issue or the bug
When using azd up for HCI Box scenarios, the command failed at pre-provision script. Please see screen shot
To Reproduce
1 - Login with powershell with credential - X
2 - Login with azd auth login for HCI box using anther credential - Y - which does not have the same access to X ie different tenant.
3 - Run azd up
Expected behavior
Pre-provision step using PowerShell will consider the context from azd auth
Environment summary
az 2.57.0
azd v1.6.1
Powershell 7.4.1
Have you looked at the Troubleshooting and Logs section?
Yes I did
Screenshots Additional context
I volunteer to look into this issue please.
The text was updated successfully, but these errors were encountered:
Hi duongthaiha! Thank you for opening this issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on the Azure Arc Jumpstart.
likamrat
changed the title
HCI Box AZD use the current PowerShell context different to azd auth context
HCIBox AZD use the current PowerShell context different to azd auth context
Mar 31, 2024
Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
I was following the instruction from this documentation (https://azurearcjumpstart.io/azure_jumpstart_hcibox/deployment_azd)
Describe the issue or the bug
When using azd up for HCI Box scenarios, the command failed at pre-provision script. Please see screen shot
To Reproduce
1 - Login with powershell with credential - X
2 - Login with azd auth login for HCI box using anther credential - Y - which does not have the same access to X ie different tenant.
3 - Run azd up
Expected behavior
Pre-provision step using PowerShell will consider the context from azd auth
Environment summary
az 2.57.0
azd v1.6.1
Powershell 7.4.1
Have you looked at the Troubleshooting and Logs section?
Yes I did
Screenshots
Additional context
I volunteer to look into this issue please.
The text was updated successfully, but these errors were encountered: