Give the virtual machine contributor role all rights needed to create a functional virtual machine
The Virtual Machine Contributor role currently lacks rights to create a new network interface on a virtual network for a new VM to be able to actually be used.
It seems that is a key permission that would be required for someone to be able to contribute new virtual machines.
Network contributor is too broad if you need operations engineers to be able to add new VMs but not be able to change any other vNET settings.
So currently you need to set up a custom role for someone to be able to fully deploy new virtual machines.
It would be beneficial to have a built in RBAC role that has all permissions needed to deploy new virtual machines.
MikeN
shared this idea
Thanks for the valid suggestion. Your feedback is now open for the user community to up-vote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
1 comment
-
Asif Ahmad
commented
I want to also suggest Microsoft.Compute/disks/* be part of the built-in Virtual Machine Contributor role as this is needed to create a functional virtual machine.