A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
@Glenn Maxwell Thank you for your query!!!
First thing I would recommend you is to migrate from Classic which doesn't support Azure Resource Manager Windows Virtual Desktop objects and will as well retire in coming time. More info here.Final call is all yours though :)
To add users to the WVD App Group Classic as mentioned here below command is recommended:
Add-RdsAppGroupUser <tenantname> <hostpoolname> <appgroupname> -UserPrincipalName <userupn>
So the above syntax is correct which you have mentioned.
Similarly for removing user from Group as mentioned here:
Remove-RdsAppGroup
[-TenantName] <String>
[-HostPoolName] <String>
[-Name] <String>
[<CommonParameters>]
So above syntax is correct.
You can use below command for getting wvd session hostname for a user:
Get-RdsSessionHost
[-TenantName] <String>
[-HostPoolName] <String>
[-Name <String>]
[<CommonParameters>]
The Get-RdsSessionHost cmdlet gets the properties of the specified session host. If you do not specify a session host, this cmdlet returns all session hosts in the host pool.
So this one is correct as well as mentioned here.
Again the last one is correct as well. As mentioned here
The Get-RdsAppGroupUser cmdlet lists the users that have access to the specified app group. If you specify a user principal name, this cmdlet either returns the specified user principal name who has access to the app group or an error indicating that they do not have access.
Get-RdsAppGroupUser
[-TenantName] <String>
[-HostPoolName] <String>
[-AppGroupName] <String>
[-UserPrincipalName <String>]
[<CommonParameters>]
Overall syntax are correct and with needed access you are good to go.
Hope it help!!!
Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.