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

What error are you getting? Did you add the PULUMI_ACCESS_TOKEN as an environment variable to you Azure CLI task?

This works for me:
```- bash: |
    pulumi stack select $(stack) --cwd $(pulumiFolder)
    pulumi stack output -j --cwd $(pulumiFolder)
  env: 
    PULUMI_ACCESS_TOKEN: $(pulumi.access.token)```

There is no pulumi access token as I'm using an azure blob container for the back end. If I _had_ an access token the problem wouldn't exist because there'd be no confusion between the SP settings for running the script and settings for the connection to the container.

However I _do_ have an answer - I can do a pulumi stack _export_ to a file and since the export contains the outputs for the stack I can pull those out of the json without much effort (powershell is a wonderful thing at times) I'm potentially sorted

pulumi stack output still needs a --file option though