We still not able to run CS commands even after connecting to Teams PowerShell using Connect-MicrosoftTeams with AadAccessToken Param.
On April 30th 2021 Microsoft has been released version 2.3.0 of Teams PowerShell Module while using that version we are receiving following issue :
Connect-MicrosoftTeams -AadAccessToken $token -AccountId 'suma@xxxx.com' -TenantId 'f9x-3xx-xx34-9xx85-5xxxxxxdcx'
After running above command we are able to connect . Then after running CS commands we are getting below issue:
**+ CategoryInfo : NotSpecified: (:) [Get-CsOnlineSession], UnauthorizedAccessException
+ FullyQualifiedErrorId : UnauthorizedAccessException,Microsoft.Teams.ConfigApi.Cmdlets.GetCsOnlineSession
Invoke-Command : Cannot validate argument on parameter 'Session'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.**
Can you please suggest.
Hi @JimmyYang-MSFT
Thank you for your response!
I did not see any error message after running the command “Connect-MicrosoftTeams -AadAccessToken $token -AccountId $acctName”.
After running the command “Connect-MicrosoftTeams -AadAccessToken $token -AccountId $acctName” i seen the response as below:
Account Environment Tenant TenantId
<Email ID> AzureCloud <Tenant Id> <Tenant Id>
And also i am able to run the commands like Get-Teams etc.. except the CS commands after running "Connect-MicrosoftTeams" command.
We already using SkypeOnlineConnector powershell module to open Ps Session & run CS commands but after July 31st Microsoft is going to terminate that module. So, we are working on migrating to Teams PowerShell Module.
Note:- CS commands is working fine if we connect using command "Connect-MicrosoftTeams" and give the credentials on the prompted Microsoft login page.