Merge pull request #245293 from dknappettmsft/patch-1

AVD SVMONC clarify service principal

Author: prmerger-automator[bot]

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

@@ -40,7 +40,7 @@ To use Start VM on Connect, make sure you follow these guidelines:
 
 ## Assign the Desktop Virtualization Power On Contributor role with the Azure portal
 
-Before you can configure Start VM on Connect, you'll need to assign the *Desktop Virtualization Power On Contributor* role-based access control (RBAC) role with your Azure subscription as the assignable scope. Assigning this role at any level lower than your subscription, such as the resource group, host pool, or VM, will prevent Start VM on Connect from working properly.
+Before you can configure Start VM on Connect, you'll need to assign the *Desktop Virtualization Power On Contributor* role-based access control (RBAC) role to the Azure Virtual Desktop service principal with your Azure subscription as the assignable scope. Assigning this role at any level lower than your subscription, such as the resource group, host pool, or VM, will prevent Start VM on Connect from working properly.
 
 You'll need to add each Azure subscription as an assignable scope that contains host pools and session host VMs you want to use with Start VM on Connect. This role and assignment will allow Azure Virtual Desktop to power on VMs, check their status, and report diagnostic information in those subscriptions.