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

I know nothing about azure but you kind of get the same in AWS for resources that are in use, you can't force delete them as they are attached to instances. you need to (probably manually) delete all the things attached to the subnets first.

Nothing should be deleted if the code hasn't changed... we'll need to see some code to see what's going wrong.

Maybe you have non-constant resource names?