Forum Discussion

Copper Contributor

Apr 30, 2021

Solved

Microsoft Teams PowerShell Module V2.3 - Set-CsUser broken!

As Microsoft discontinued SkypeOnlineConnector (finally) we moved to MicrosoftTeams PowerShell Module for user management - especially for Direct Routing phone number management (-OnPremLineURI). ...

powershell

Paul_Wood
Apr 30, 2021
Markus_Hupfauer

We had the same issue today and this is how we got round it:

Run a PS session as Admin
Uninstall-Module -Name MicrosoftTeams
Install-Module -Name MicrosoftTeams -RequiredVersion 2.0.0
Import-Module -Name MicrosfTeams
This then allowed us to progress and use the Set-CsUser command.

vrallapalli034

Copper Contributor

Apr 30, 2021

Hi Paul_Wood,

When we tried to go back to 2.0.0 - we are getting the following error message -

Exception calling "GetSteppablePipeline" with "1" argument(s): "Exception calling "GetRemoteNewCsOnlineSession" with "1" argument(s): "Run either Connect-MicrosoftTeams

or new-csonlinesession before running cmdlets.""

At C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\2.0.0\net472\SfBORemotePowershellModule.psm1:9474 char:13

+ $steppablePipeline = $scriptCmd.GetSteppablePipeline($myI ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException

+ FullyQualifiedErrorId : CmdletInvocationException

Can you provide any insights into what might be causing this? We are trying to do a 'connect-microsoftteams' with AADAccessToken and AccountID params.

Thanks,

--Venkata

MiroMD

Copper Contributor

Apr 30, 2021

I'm sure you already figured out that you will need to run Connect-MicrosoftTeams after importing the 2.0.0 module

vrallapalli034
Copper Contributor
May 01, 2021
Yes, we were trying to use the Connect-MicrosoftTeams -AadAccessToken $token -AccountId <upn>. The teams commands are working fine. The SFBO commands are failing.