Apr 30 2021 04:00 AM
As Microsoft discontinued SkypeOnlineConnector (finally) we moved to MicrosoftTeams PowerShell Module for user management - especially for Direct Routing phone number management (-OnPremLineURI).
However, the current version of MicrosoftTeams PowerShell Module no longer supports -OnPremLineURI neither does it work for -EnterpriseVoiceEnabled:$true and or -HostedVoiceMail:$true
We are currently inable to deploy new phone system users as the "legacy" SkypeOnlineConnector no longer functions.
Apr 30 2021 05:04 AM
Apr 30 2021 05:09 AM
Apr 30 2021 05:27 AM
Apr 30 2021 05:47 AM
Solution
We had the same issue today and this is how we got round it:
This then allowed us to progress and use the Set-CsUser command.
Apr 30 2021 06:03 AM
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
Apr 30 2021 06:08 AM
Apr 30 2021 06:36 AM
Apr 30 2021 07:10 AM
Apr 30 2021 07:58 AM
Apr 30 2021 08:08 AM
Apr 30 2021 05:03 PM
Yes, we were trying to use the Connect-MicrosoftTeams -AadAccessToken $token -AccountId <upn>. The teams commands are working fine. The SFBO commands are failing.
May 04 2021 01:49 AM
May 04 2021 04:01 AM
May 06 2021 04:21 AM
May 06 2021 08:35 AM
May 09 2021 04:46 AM
big issue.
check my post -
https://www.linkedin.com/pulse/microsoft-releases-v230-teams-powershell-module-elazar-ohayon/
So we wait for Microsoft to fix it.
Hopefully, this will happen quickly.
May 10 2021 05:08 AM
@Markus_Hupfauer It seems to be fixed in v2.3.1 that has just been released.
https://www.powershellgallery.com/packages/MicrosoftTeams/2.3.1
May 10 2021 05:10 AM
May 10 2021 05:26 AM
Oh dear. Any ideas which ones?
This seemed to execute ok, without any errors:
Set-CsUser -Identity user@doamin.com -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI "tel:+1234567890"
Note they've gone back to using -Identity !
Apr 30 2021 05:47 AM
Solution
We had the same issue today and this is how we got round it:
This then allowed us to progress and use the Set-CsUser command.