-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AzureCLI task is failing with error "The term 'Get-AzADGroup' is not recognized as a name of a cmdlet, function, script file, or executable program" #19861
Comments
@jakerosedatacom Could you please share the detailed logs of the pipeline by adding the variable system.debug to "true". |
@v-schhabra , here you go 2024-05-19T21:09:27.8195721Z ##[debug]Evaluating condition for step: 'Provision Resource Group' |
@jakerosedatacom We are checking on the issue above and will share the updates soon. |
@jakerosedatacom we have modified your script https://gist.github.com/DmitriiBobreshev/221c9dc5ac7d8348b7ff50c4b1347990. |
@v-schhabra , I tried that new script and got a very similar looking error message 2024-05-28T04:25:46.5352575Z ##[debug]Evaluating condition for step: 'Provision Resource Group' |
Hi @jakerosedatacom |
Is it expected behaviour in the AzureCli@2 update that I should now have to login using Connect-AzAccount? It used to work before without the Connect-AzAccount command. Is there anywhere to see documentation about these changes so we can track changes that will break functionality? And if it is expected behaviour, why does the AzurePowershell@5 task not require me to use Connect-AzAccount? Will this also change at some point to require the use of Connect-AzAccount? |
New issue checklist
Task name
AzureCLI
Breaking task version
2.237.3
Last working task version
2.230.0
Regression Description
As of 2.237.3 I am getting lots of different errors all centering around the Az context being invalid and a message to "Please login using Connect-AzAccount.
At 2.230.0 I didn't have any issues and the code hasn't changed.
In order to test the Service Principal still has the correct permissions I have converted certain scripts to instead use the AzurePowershell@5 task and they are all completing successfully.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
ubuntu-latest
Relevant log output
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
The text was updated successfully, but these errors were encountered: