Question 110
A deployment identity holds Virtual Machine Contributor on an existing VM but a redeployment fails when it tries to create a new NIC and attach it to a subnet. What should you inspect or change?
Explanation
Correct Answer
Virtual Machine Contributor focuses on compute management and does not automatically provide full network management rights for creating NICs or joining subnets. A deployment that creates dependent networking resources requires permissions for those resources at their own scopes, often through a network-specific role or narrowly defined custom actions. The correct fix is to inspect the failed Microsoft.Network operation and assign only the missing dependency rights, not to assume the VM role covers every resource in the template.
Incorrect Answers
Reader on the VM allows inspection of its management properties but supplies no NIC creation or subnet-join write operations. The authorization failure occurs against the network resources needed by redeployment, not the VM's read visibility. The identity must receive the appropriate Microsoft.Network permissions at the NIC and subnet locations.
Blob Data Contributor authorizes operations on blob objects, not creation of Azure network interfaces or subnet attachment. The failing deployment operation is on the Microsoft.Network resource provider. A data-plane storage role would leave that failure unchanged and expose unrelated blob data permissions across the subscription.
Duplicating the existing compute role on the same VM does not add the missing network permission set. Azure RBAC permissions depend on both the role definition's allowed actions and the operation's resource scope. The deployment needs appropriate NIC and subnet rights, so adding the same VM role again cannot resolve this separate dependency.