Dec 03 2021 02:41 AM
Hi everyone,
When using multithreading for Teams PowerShell sessions, there is an error saying that "The session SfBPowerShellSessionViaTeamsModule_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, api.interfaces.records.teams.microsoft.com is not available to run commands. The session availability is Busy"
When trying the exact same commands using 2 PowerShell windows it's working perfectly.
Does anyone know how the Teams Powershell module is managing the sessions (where the context is stored and how to parallelize sessions)?
The same kind of issues seems to appear with AzureAD Powershell module.
Thanks!
Regards,
Stephen
Dec 03 2021 04:29 AM
Dec 03 2021 05:33 AM
Dec 03 2021 06:22 AM
2.3.1 is a little old, I recommend updating to the latest GA which is 3.0.0, you can find more about versions here
I do know that in the latest versions some work has been done to the way it handles sessions so maybe you want to give it a try with 3.0.0 and return here to share feedback