Closed JimMoyle closed 2 months ago
Thank you for your feedback. This has been routed to the support team for assistance.
This should be resolved in latest stable with Identity being correctly handling to allow piping. Please upgrade to latest stable API.
Description
You should be able to do this
Get-AzWvdUserSession -ResourceGroupName $ResourceGroupName -HostPoolName $HostPoolName -SessionHostName $SessionHostName | Where-Object {$_.UserPrincipalName -eq $UserName } | Disconnect-AzWvdUserSession
Pipeling could work in 2 ways neither of them work
Also the session number is going to be an int, whereas the help for the parameter says the following:
Which is clearly denoted as a string and says the name of the user session rather than the number, this not only gives the wrong instruction, but also the wrong eror in code when pipelining is associated with the parameter
Issue script & Debug output
Environment data
Module versions
Error output