Help with azd deploy in sample Devops pipeline - fails with "not logged in" error

[kevcrooks]

I'm attempting to use the sample pipeline here:
https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/configure-devops-pipeline?tabs=azdo

I've set up the pipeline correctly, and run on Azure Devops. The problem is that the azd provision step works fine, but when it gets to the azd deploy step, I get the following error:

ERROR: getting resource group name: getting resource group for environment: XXXX: not logged in, run `azd auth login` to login

I'm not sure why this is happening, since the provision step worked, and in the logs I'm seeing that it is connecting:

C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" account set --subscription XXXX"

Does anyone have advice on how to get this working? My understanding is that the azd config set auth... step should have sorted all the login for me?

[vhvb1989]

Can you share your pipeline yaml definition?

Are you using a federated-credential for your service connection? (did you use azd pipeline config? )
Try using keepAzSessionActive: true AzureCLIV2` task, like

- task: AzureCLI@2
      displayName: Deploy Application
      inputs:
         azureSubscription: azconnection
         keepAzSessionActive: true
         scriptType: bash
         scriptLocation: inlineScript
         inlineScript: |
         azd deploy --no-prompt

[kevcrooks]

Thank you, yes I did run the config to set up the pipeline and the service connection. I also tried setting keepAzSessionActive.

What was strange was that my tasks for provision and deploy were otherwise identical, yet it only failed on the deploy step.

In the end, I deleted the entire pipeline and yaml and recreated again, which fixed the issue.

The yaml files were all the same as before, as far as I can tell. The only item I couldn't identify was the secret pipeline parameter (it's a shame I couldn't see documentation on what the value/structure of this secret is.)

So it's possible there was an issue with the secret, but otherwise it remains a mystery to me what the problem was.