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

FWIW, I'm in the middle of doing this kind of work right now.

Within Github Actions, I set the `ARM_CLIENT_ID`, etc. environment variables via the `secrets` context (e.g. `${{ secrets.PULUMI_ARM_CLIENT_ID_DEV }}`). For this scenario, the Pulumi Github action works without any kind of az cli login.

When I'm running the same Pulumi program interactively (e.g. at a Powershell shell), I'm logged in via `az login`. But I don't have any reason to think that if I set the 4 `ARM_` environment variables that `pulumi up` wouldn't work - without being logged in to the az cli.

Is that what you're asking? Does that help?

It is what I'm asking - and yep, I can confirm that using the ARM_ variables it works.  What I was led to believe from the docs (could be my mistake in the interpretation though) is that this would work only with the pulumi stack config and no az login.  Doesn't seem to be the case.