No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Are they different steps in the pipeline? Note this rule from Azure Pipelines:
&gt; A step is a linear sequence of operations that make up a job. Each step runs in its own process on an agent and has access to the pipeline workspace on a local hard drive. This behavior means environment variables aren't preserved between steps but file system changes are.
(<https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&amp;tabs=schema%2Cparameter-schema#steps>)

So if you're relying on PULUMI_ACCESS_TOKEN being set, and it's happening in one step (script #1), it won't still be there in the next step (script #2).

I have no pulumi access token set. The state is stored on azure blob storage. Login and the stack commands are in one step.