This message was deleted.

Are you subnets nested in the virtual network or separate?

subnet is separate and it references the name of the vnet.

Azure resource manager (ARM) has a well known bug that has been around since the invention of ARM. Creating subnets separate from the vnet will cause the behavior your are seeing. This happens with ARM templates and bicep too because we all call the same API. Just nest the subnets inside the vnet.

@clean-truck-93285 Thanks for the reply, will there be a fix plan for this bug? Because for automation, we will rely on templates to flexibly change the subnet by passing parameters. If the nested definition in vnet lacks the corresponding flexibility, or do you have any suggestions here to declare subnet in vnet and pass the same Template loop to create subnet in same vnet.

I doubt Microsoft cares at this point. Here the GitHub issue I see the most when searching forums. https://github.com/Azure/azure-quickstart-templates/issues/2786 Also note I don't work for Pulumi or Microsoft. I just a cloud engineer that encountered this problem before. Thinking you could make an array outside of the vnet, save to a variable, and put that inside the vnet. Never tried but might work.