Forum Discussion
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).
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.
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.
- Microsoft has released V2.3.1. Have you tested against that version?
- Tony -
The connect-microsoftteams with AadAccessToken doesn't let us access any SFBO CS-Online commands and this is same in 2.3.1 version as well. Today again, Microsoft started throwing a warning on the SFBO connector sessions that it is EOL for it. There seems to be no alternative for the backend integrated scripts to function without interactive login.
Does anyone have any workarounds for this issue?
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
- Yes it does 🙂 but apparently some arguments are still broken, but it's at least better than the previous release.
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 !
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.
- This is a serious problem for any one deploying new customers to Teams with Enterprise Voice.
The previous versions 2.0.0 and forward have some serious performance degradations.
I don't get how a refactoring of a well used connector can end up with such a serious degradation!
Does any one know if version 1.1.6 of the Teams module will continue to work after the retirement of Skype for Business Online connector ?- Same here: the 2.x versions are really slow and we decided to keep using 1.1.6, but we could not find any information if 1.1.6 will stop working after 5/15/2021 as the SfB module.
- And there are more issues https://office365itpros.com/2021/05/04/teams-updated-powershell-module/
but the set-csusers is under investigation #didMicrosoftKillDirectRouting 🙂 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.
- Thanks Paul_Wood I can confirm that downgrading to v2.0.0 of the MicrosoftTeams PowerShell module is a workaround and allows running of Set-CsUser -Identity xxx -OnPremLineURI which is needed for customers using Direct Routing.
The Skype Online Connector stopping working today was a surprise to us as our message center post says 15 May 2021 so it should still be working in my opinion.
I have logged with MS Support and urge others to do the same.- MS Support just yesterday got back to us and was unable to understand that the PowerShell Module was broken. They wanted to remote type the command and perform a step recording. At that point we closed the request as this was going nowhere.
Someone botched this transition / upgrade massively.
- did that and on uninstall I get this error
Uninstall-Module -Name MicrosoftTeams
PackageManagement\Uninstall-Package : Access to the cloud file is denied
The file it selves are: At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1:12733 char:21 - Thanks for the solution.
I confirm the command St-CsUser works again with version 2.0.0 of the MicrosoftTeams module.
- I have the same problem, have you found a way to deploy new phone anyway?
- Obviously not. GraphAPI is work in progress, SkypeOnlineConnector dosn't work either....
Microsoft just broke Teams Direct Routing - probably world wide.
Please Microsoft just re-enable SkypeOnlineConnector - we need to deploy new users to direct routing.- That's crap. So we wait for Microsoft to fix it.
I opened a ticket on Microsoft 365, I'm waiting for the return.
thank you for your information
