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

Hi Andreas. You are right, the nextgen provider exposes ARM API, so if something isn’t there, it’s not in the provider. For now, the advice is to use both providers at the same time and use `Blob` from the old provider in combination with NextGen provider for all ARM resources.

Okay, it just ends up a bit cumbersome as the way to get the signed Blob Url is through the Pulumi.Azure.Storage.SharedAccessSignature.SignedBlobReadUrl() which takes a Pulumi.Azure.Storage.Account (my storage account) meaning the storage account needs to be created through the old way, unless i want to extract and modify that method, right?

Is it the plan to amend the Azure next-gen with extensions similar to the old Azure package?

Yes, we intend to add data-plane operations (like Blob, key vault keys, etc.) before the new provider goes GA.