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

My first guess is that you need to provide the full path to that property. In this case, I think it would be `storageProfile.imageReference`

You may also need to use `deleteBeforeReplace` with the same target, as <https://www.pulumi.com/docs/concepts/options/replaceonchanges/#:~:text=The%20replaceOnChanges%20resource%20option%20can,of%20an%20in%2Dplace%20update.|mentioned in the docs>

I agree with <@U03JNU76GAJ> on both of his recommendations.

Re: `deleteBeforeReplace`, the reason you'll need to use that is, it seems you are setting the VM name explicitly instead of using auto-naming, so you can't have two VMs with the same name. But it means for a moment you won't have any VM running until the new is setup after the original one is deleted. Is there a reason you don't want to use Pulumi's auto-naming feature?

Thank you both for your kind advisory. I will try and experiment. There's no specific reason for us not to use the auto-naming feature, we however just need this single low-performance for the purpose of DNS forwarding