SOLVED

Direct Routing setup still not working or documented

Iron Contributor

I am currently unable to add new users to our Direct Routing setup in MS Teams.  This is broken since the S4B module was deprecated.

 

Some basics...

 

I am running Powershell v5.1

I have installed module Microsoft Teams v2.5.1

I am 'connected' to MicrosoftTeams module as a Global Admin who also has the S4B Admin role assigned (although it should need a separate role assignment).

I have 'imported' the Microsoft Teams module

 

I am trying to run:

Set-CsUser -Identity "xxxxx@yyyyy.org" -OnPremLineURI tel:+44000000000 -EnterpriseVoiceEnabled $true -HostedVoiceMail $true

 

I receive back:

Set-CsUser : The 'Set-CsUser' command was found in the module 'MicrosoftTeams', but the module could not be loaded. For more information, run 'Import-Module MicrosoftTeams'

 

 

If I try:

Set-CsOnlineVoiceUser -Identity "xxxx@yyyy.org" -TelephoneNumber tel:+440000000000

 

I receive back:

Set-CsOnlineVoiceUser : The 'Set-CsOnlineVoiceUser' command was found in the module 'MicrosoftTeams', but the module could not be loaded. For more information, run 'Import-Module MicrosoftTeams'

 

'Import-Module Microsoft Teams'  has already been run and running it again does not provide any additional information.

 

None of the cmdlet reference guides Microsoft have published even list the cmdlets from the S4B module that needed to be used for Enterprise Direct Routing so this leads me to ask...

 

1) When will Microsoft update the documentation for the new MicrosoftTeams module to include the full cmdlet list?

 

2) What commands 'should' I be using to add users to our Direct Routing and to grant OnlineVoiceRoutingPolicy (s)?

 

Many thanks in advance to anyone who has the answers.

 

 

3 Replies

@Technodude It sounds like there is a problem, maybe a corruption in the module code on your machine. Try finding and deleting it before import-module again.

Hi Steven. Already tried that I'm afraid. ..but thanks anyway :)
best response confirmed by Technodude (Iron Contributor)
Solution
Well... I logged a ticket with Microsoft at the same time as posting on here and they've been brilliant and got the issue resolved. So... for anyone reading this...

1) Microsoft are currently working on the documentation and hope to have it live soon.
2) The old CS- cmdlets are all included within the latest 2.5.1 module but... I had to do the following to resolve the issue....

Uninstall-Module MicrosoftTeams (to remove 2.5.1)
Install-Module MicrosoftTeams (without version number) ... this errored and came back telling me I had the MicrosoftTeams module v0.9.6 already installed and to use -force to sideload the 2.5.1 module.
Instead, I was asked to delete the v0.9.6 module from the location specified in the error message
Afterwards, re-ran Install-Module MicrosoftTeams and it installed without error.

Once installed I was able to run the CS- commands without issue. :)
1 best response

Accepted Solutions
best response confirmed by Technodude (Iron Contributor)
Solution
Well... I logged a ticket with Microsoft at the same time as posting on here and they've been brilliant and got the issue resolved. So... for anyone reading this...

1) Microsoft are currently working on the documentation and hope to have it live soon.
2) The old CS- cmdlets are all included within the latest 2.5.1 module but... I had to do the following to resolve the issue....

Uninstall-Module MicrosoftTeams (to remove 2.5.1)
Install-Module MicrosoftTeams (without version number) ... this errored and came back telling me I had the MicrosoftTeams module v0.9.6 already installed and to use -force to sideload the 2.5.1 module.
Instead, I was asked to delete the v0.9.6 module from the location specified in the error message
Afterwards, re-ran Install-Module MicrosoftTeams and it installed without error.

Once installed I was able to run the CS- commands without issue. :)

View solution in original post