Skip to content

Commit 66c3dbb

Browse files
committed
Made Heidi's edits
1 parent 3625cfe commit 66c3dbb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-desktop/start-virtual-machine-connect.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ To use the Azure portal to create a custom role for Start VM on Connect:
6161
- Microsoft.Compute/virtualMachines/start/action
6262
- Microsoft.Compute/virtualMachines/*/read
6363

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.
6565

6666
After that, you'll need to assign the role to the Azure Virtual Desktop service principal.
6767

@@ -74,7 +74,7 @@ To assign the custom role:
7474
3. On the **Members** tab, enter and select **Windows Virtual Desktop** in the search bar.
7575

7676
>[!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.
7878
>
7979
> [!div class="mx-imgBorder"]
8080
> ![A screenshot of the Access control (IAM) tab. In the search bar, both Azure Virtual Desktop and Azure Virtual Desktop (classic) are highlighted in red.](media/add-role-assignment.png)

0 commit comments

Comments
 (0)