You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/start-virtual-machine-connect.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ To use the Azure portal to create a custom role for Start VM on Connect:
61
61
- Microsoft.Compute/virtualMachines/start/action
62
62
- Microsoft.Compute/virtualMachines/*/read
63
63
64
-
6. When you're finished, select **Review + create**. It may take a few minutes for the custom role to get created.
64
+
6. When you're finished, select **Review + create**. It may take a few minutes for the RBAC service to create the custom role.
65
65
66
66
After that, you'll need to assign the role to the Azure Virtual Desktop service principal.
67
67
@@ -74,7 +74,7 @@ To assign the custom role:
74
74
3. On the **Members** tab, enter and select **Windows Virtual Desktop** in the search bar.
75
75
76
76
>[!NOTE]
77
-
>You might see both the Windows Virtual Desktop and Windows Virtual Desktop ARM Provider first party applications if you have deployed Azure Virtual Desktop (classic). Assign the role to both apps.
77
+
>You might see both the Windows Virtual Desktop and Windows Virtual Desktop Azure Resource Manager Provider first party applications appear if you've deployed Azure Virtual Desktop (classic). Assign the role to both apps.
78
78
>
79
79
> [!div class="mx-imgBorder"]
80
80
> 
0 commit comments