Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)
SOLVED

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

%3CLINGO-SUB%20id%3D%22lingo-sub-2310236%22%20slang%3D%22de-DE%22%3EMicrosoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310236%22%20slang%3D%22de-DE%22%3E%3CP%3EAs%20Microsoft%20discontinued%20SkypeOnlineConnector%20(finally)%20we%20moved%20to%20MicrosoftTeams%20PowerShell%20Module%20for%20user%20management%20-%20especially%20for%20Direct%20Routing%20phone%20number%20management%20(-OnPremLineURI).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20the%20current%20version%20of%20MicrosoftTeams%20PowerShell%20Module%20no%20longer%20supports%20-OnPremLineURI%20neither%20does%20it%20work%20for%20-EnterpriseVoiceEnabled%3A%24true%20and%20or%20-HostedVoiceMail%3A%24true%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20currently%20inable%20to%20deploy%20new%20phone%20system%20users%20as%20the%20%22legacy%22%20SkypeOnlineConnector%20no%20longer%20functions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2310236%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310394%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310394%22%20slang%3D%22en-US%22%3EI%20have%20the%20same%20problem%2C%20have%20you%20found%20a%20way%20to%20deploy%20new%20phone%20anyway%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310427%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310427%22%20slang%3D%22en-US%22%3EObviously%20not.%20GraphAPI%20is%20work%20in%20progress%2C%20SkypeOnlineConnector%20dosn't%20work%20either....%3CBR%20%2F%3EMicrosoft%20just%20broke%20Teams%20Direct%20Routing%20-%20probably%20world%20wide.%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20Microsoft%20just%20re-enable%20SkypeOnlineConnector%20-%20we%20need%20to%20deploy%20new%20users%20to%20direct%20routing.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310550%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310550%22%20slang%3D%22en-US%22%3EThat's%20crap.%20So%20we%20wait%20for%20Microsoft%20to%20fix%20it.%3CBR%20%2F%3EI%20opened%20a%20ticket%20on%20Microsoft%20365%2C%20I'm%20waiting%20for%20the%20return.%3CBR%20%2F%3E%3CBR%20%2F%3Ethank%20you%20for%20your%20information%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310607%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041688%22%20target%3D%22_blank%22%3E%40Markus_Hupfauer%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20had%20the%20same%20issue%20today%20and%20this%20is%20how%20we%20got%20round%20it%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3ERun%20a%20PS%20session%20as%20Admin%3C%2FLI%3E%3CLI%3EUninstall-Module%20-Name%20MicrosoftTeams%3C%2FLI%3E%3CLI%3EInstall-Module%20-Name%20MicrosoftTeams%20-RequiredVersion%202.0.0%3C%2FLI%3E%3CLI%3EImport-Module%20-Name%20MicrosfTeams%3C%2FLI%3E%3C%2FOL%3E%3CP%3EThis%20then%20allowed%20us%20to%20progress%20and%20use%20the%20Set-CsUser%20command.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310629%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310629%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041772%22%20target%3D%22_blank%22%3E%40Paul_Wood%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20we%20tried%20to%20go%20back%20to%202.0.0%20-%20we%20are%20getting%20the%20following%20error%20message%20-%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22s1%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3EException%20calling%20%22GetSteppablePipeline%22%20with%20%221%22%20argument(s)%3A%20%22Exception%20calling%20%22GetRemoteNewCsOnlineSession%22%20with%20%221%22%20argument(s)%3A%20%22Run%20either%20Connect-MicrosoftTeams%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p1%22%3Eor%20new-csonlinesession%20before%20running%20cmdlets.%22%22%3C%2FP%3E%3CP%20class%3D%22p1%22%3EAt%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CMicrosoftTeams%5C2.0.0%5Cnet472%5CSfBORemotePowershellModule.psm1%3A9474%20char%3A13%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%2B%20%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%24steppablePipeline%20%3D%20%24scriptCmd.GetSteppablePipeline(%24myI%20...%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%2B%20%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%2B%20CategoryInfo%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%3A%20NotSpecified%3A%20(%3A)%20%5B%5D%2C%20ParentContainsErrorRecordException%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%20%26nbsp%3B%20%3C%2FSPAN%3E%2B%20FullyQualifiedErrorId%20%3A%20CmdletInvocationException%3C%2FP%3E%3CP%20class%3D%22p2%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p2%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3ECan%20you%20provide%20any%20insights%20into%20what%20might%20be%20causing%20this%3F%26nbsp%3B%20We%20are%20trying%20to%20do%20a%20'connect-microsoftteams'%20with%20AADAccessToken%20and%20AccountID%20params.%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p2%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22p2%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p2%22%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E--Venkata%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310721%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310721%22%20slang%3D%22en-US%22%3Edid%20that%20and%20on%20uninstall%20I%20get%20this%20error%3CBR%20%2F%3EUninstall-Module%20-Name%20MicrosoftTeams%3CBR%20%2F%3EPackageManagement%5CUninstall-Package%20%3A%20Access%20to%20the%20cloud%20file%20is%20denied%3CBR%20%2F%3EThe%20file%20it%20selves%20are%3A%20At%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CPowerShellGet%5C2.2.5%5CPSModule.psm1%3A12733%20char%3A21%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310896%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310896%22%20slang%3D%22en-US%22%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041772%22%20target%3D%22_blank%22%3E%40Paul_Wood%3C%2FA%3E%20I%20can%20confirm%20that%20downgrading%20to%20v2.0.0%20of%20the%20MicrosoftTeams%20PowerShell%20module%20is%20a%20workaround%20and%20allows%20running%20of%20Set-CsUser%20-Identity%20xxx%20-OnPremLineURI%20which%20is%20needed%20for%20customers%20using%20Direct%20Routing.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20Skype%20Online%20Connector%20stopping%20working%20today%20was%20a%20surprise%20to%20us%20as%20our%20message%20center%20post%20says%2015%20May%202021%20so%20it%20should%20still%20be%20working%20in%20my%20opinion.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20logged%20with%20MS%20Support%20and%20urge%20others%20to%20do%20the%20same.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2311106%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2311106%22%20slang%3D%22en-US%22%3EMessage%20Center%20clearly%20states%2015%20May%202021%20for%20us%20too!%3CBR%20%2F%3EThanks%20a%20lot%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041772%22%20target%3D%22_blank%22%3E%40Paul_Wood%3C%2FA%3E!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2311166%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2311166%22%20slang%3D%22en-US%22%3EI'm%20sure%20you%20already%20figured%20out%20that%20you%20will%20need%20to%20run%20Connect-MicrosoftTeams%20after%20importing%20the%202.0.0%20module%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2312870%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2312870%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20we%20were%20trying%20to%20use%20the%20Connect-MicrosoftTeams%20-AadAccessToken%20%24token%20-AccountId%20%3CUPN%3E.%26nbsp%3B%20The%20teams%20commands%20are%20working%20fine.%26nbsp%3B%20The%20SFBO%20commands%20are%20failing.%3C%2FUPN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2320802%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2320802%22%20slang%3D%22en-US%22%3EAnd%20there%20are%20more%20issues%20%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2021%2F05%2F04%2Fteams-updated-powershell-module%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2021%2F05%2F04%2Fteams-updated-powershell-module%2F%3C%2FA%3E%3CBR%20%2F%3Ebut%20the%20set-csusers%20is%20under%20investigation%20%23didMicrosoftKillDirectRouting%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2321231%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2321231%22%20slang%3D%22en-US%22%3EMS%20Support%20just%20yesterday%20got%20back%20to%20us%20and%20was%20unable%20to%20understand%20that%20the%20PowerShell%20Module%20was%20broken.%20They%20wanted%20to%20remote%20type%20the%20command%20and%20perform%20a%20step%20recording.%20At%20that%20point%20we%20closed%20the%20request%20as%20this%20was%20going%20nowhere.%3CBR%20%2F%3E%3CBR%20%2F%3ESomeone%20botched%20this%20transition%20%2F%20upgrade%20massively.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2330941%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2330941%22%20slang%3D%22en-US%22%3EThis%20is%20a%20serious%20problem%20for%20any%20one%20deploying%20new%20customers%20to%20Teams%20with%20Enterprise%20Voice.%3CBR%20%2F%3EThe%20previous%20versions%202.0.0%20and%20forward%20have%20some%20serious%20performance%20degradations.%3CBR%20%2F%3EI%20don't%20get%20how%20a%20refactoring%20of%20a%20well%20used%20connector%20can%20end%20up%20with%20such%20a%20serious%20degradation!%3CBR%20%2F%3EDoes%20any%20one%20know%20if%20version%201.1.6%20of%20the%20Teams%20module%20will%20continue%20to%20work%20after%20the%20retirement%20of%20Skype%20for%20Business%20Online%20connector%20%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2331840%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2331840%22%20slang%3D%22en-US%22%3ESame%20here%3A%20the%202.x%20versions%20are%20really%20slow%20and%20we%20decided%20to%20keep%20using%201.1.6%2C%20but%20we%20could%20not%20find%20any%20information%20if%201.1.6%20will%20stop%20working%20after%205%2F15%2F2021%20as%20the%20SfB%20module.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2338863%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2338863%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041688%22%20target%3D%22_blank%22%3E%40Markus_Hupfauer%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebig%20issue.%3C%2FP%3E%3CP%3Echeck%20my%20post%20-%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fpulse%2Fmicrosoft-releases-v230-teams-powershell-module-elazar-ohayon%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.linkedin.com%2Fpulse%2Fmicrosoft-releases-v230-teams-powershell-module-elazar-ohayon%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20wait%20for%20Microsoft%20to%20fix%20it.%3C%2FP%3E%3CP%3EHopefully%2C%20this%20will%20happen%20quickly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2340609%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2340609%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041688%22%20target%3D%22_blank%22%3E%40Markus_Hupfauer%3C%2FA%3E%26nbsp%3BIt%20seems%20to%20be%20fixed%20in%20v2.3.1%20that%20has%20just%20been%20released.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.powershellgallery.com%2Fpackages%2FMicrosoftTeams%2F2.3.1%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.powershellgallery.com%2Fpackages%2FMicrosoftTeams%2F2.3.1%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2340612%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2340612%22%20slang%3D%22en-US%22%3EYes%20it%20does%20%3A)%3C%2Fimg%3E%20but%20apparently%20some%20arguments%20are%20still%20broken%2C%20but%20it's%20at%20least%20better%20than%20the%20previous%20release.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2340651%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2340651%22%20slang%3D%22en-US%22%3E%3CP%3EOh%20dear.%20Any%20ideas%20which%20ones%3F%3C%2FP%3E%3CP%3EThis%20seemed%20to%20execute%20ok%2C%20without%20any%20errors%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3ESet-CsUser%20-Identity%20user%40doamin.com%20-EnterpriseVoiceEnabled%20%24true%20-HostedVoiceMail%20%24true%20-OnPremLineURI%20%22tel%3A%2B1234567890%22%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3ENote%20they've%20gone%20back%20to%20using%20-Identity%20!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2341189%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2341189%22%20slang%3D%22en-US%22%3ENew-CsOnlineAudioFile%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineBulkAssignmentInput%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineDateTimeRange%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineLisCivicAddress%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineLisLocation%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineNumberPortInOrder%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlinePSTNGateway%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineSchedule%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineTimeRange%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineVoicemailPolicy%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineVoiceRoute%202.3.1%20MicrosoftTeams%3CBR%20%2F%3EFunction%20New-CsOnlineVoiceRoutingPolicy%202.3.1%20MicrosoftTeams%3CBR%20%2F%3E%3CBR%20%2F%3ENew-CsOnlineSession%20not%20in%20the%20list.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2350575%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2350575%22%20slang%3D%22en-US%22%3EMicrosoft%20has%20released%20V2.3.1.%20Have%20you%20tested%20against%20that%20version%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2367191%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2367191%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F77089%22%20target%3D%22_blank%22%3E%40Tony%3C%2FA%3E%20-%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20connect-microsoftteams%20with%20AadAccessToken%20doesn't%20let%20us%20access%20any%20SFBO%20CS-Online%20commands%20and%20this%20is%20same%20in%202.3.1%20version%20as%20well.%20Today%20again%2C%20Microsoft%20started%20throwing%20a%20warning%20on%20the%20SFBO%20connector%20sessions%20that%20it%20is%20EOL%20for%20it.%20There%20seems%20to%20be%20no%20alternative%20for%20the%20backend%20integrated%20scripts%20to%20function%20without%20interactive%20login.%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20anyone%20have%20any%20workarounds%20for%20this%20issue%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2340672%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2340672%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20the%20New-CsOnlineSession%20makes%20a%20comeback!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20CS%20commands%20are%20now%20executing%20successfully.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20guys%20for%20fixing%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310633%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20V2.3%20-%20Set-CsUser%20broken!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310633%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20solution.%3CBR%20%2F%3EI%20confirm%20the%20command%20St-CsUser%20works%20again%20with%20version%202.0.0%20of%20the%20MicrosoftTeams%20module.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

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.

23 Replies
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
best response confirmed by Markus_Hupfauer (Occasional Contributor)
Solution

@Markus_Hupfauer 

 

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

 

  1. Run a PS session as Admin
  2. Uninstall-Module -Name MicrosoftTeams
  3. Install-Module -Name MicrosoftTeams -RequiredVersion 2.0.0
  4. Import-Module -Name MicrosfTeams

This then allowed us to progress and use the Set-CsUser command.

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

Thanks for the solution.
I confirm the command St-CsUser works again with version 2.0.0 of the MicrosoftTeams module.
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 @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.
Message Center clearly states 15 May 2021 for us too!
Thanks a lot @Paul_Wood!
I'm sure you already figured out that you will need to run Connect-MicrosoftTeams after importing the 2.0.0 module

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

 

 

And there are more issues https://office365itpros.com/2021/05/04/teams-updated-powershell-module/
but the set-csusers is under investigation #didMicrosoftKillDirectRouting :)
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.
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.

@Markus_Hupfauer 

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.

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 !