Forum Discussion
evasse
Jun 04, 2021Former Employee
What is your experience with Start VM on connect. Share your voice!
Hi Community :)!
If you remember I announced a while ago public preview of start VM on connect. As you had some time to explore the feature, let me know what you think.
Please answer this...
evasse
Jul 14, 2021Former Employee
Christoph Distefano: You need to create the custom role: https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect#create-a-custom-role-for-start-vm-on-connect.
Christoph Distefano
Jul 14, 2021Copper Contributor
hello evasse , as mentioned in my initial post we had a similar role already in place (it has more permissions actually, but also read and start permission) and assigned it on Resource Group Level.
And, also as mentioned, the custom role works, since the user can see/start/stop the VMs via Azure Portal or PowerShell after we assign him with the role.
Any other information on this, maybe some insights from the troubleshooting within the last months?
- evasseJul 14, 2021Former EmployeeDid you pay attention that the service has the rights? Having similar role is not specific enough. The service needs the rights to start/stop VMs. Please review the doc carefully.
- Christoph DistefanoJul 14, 2021Copper Contributorah, awesome, thank you for the hint. I missed it and assigned the role to the user, not the service. My fault, documentation is pretty clear on this! 🙂
Works now. thank you for your fast replies.