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

The second. I don't think you can deploy resources in the same stack to a separate subscription, but you can certainly deploy different stacks to different subscriptions

You can deploy resources in the same stack to different subs, you just need to create a second provider instance for the second sub and use that

Thanks <@U01FB0HRB2Q> and <@U014JNRGADD> but my question was about *different* stacks.

For example, I have 3 devs on a team.
One Pulumi project in version control. One shared Pulumi organization, to which all 3 devs have access. Each dev authenticated against Pulumi using their own individual accounts, but all have access to the shared org and that’s where the stacks go.
Now, can each dev do `pulumi up` with a new stack name, each against different Azure subscriptions?

Yes. You can either set the subscription id in the stack config or have it as an environment variable