Forum Discussion
Solved
Set-CsUser Deprecated in the last 24 hours??
I have gone to enable anew user for enterprise voice, a DDI and voicemail this morning and run: Set-CsUser -Identity "email address removed for privacy reasons" -EnterpriseVoiceEnabled $true -Hos...
Managed to fix it yes, for anyone else coming here the new\correct syntax for enabling someone with a DDI is:
Set-CsPhoneNumberAssignment -Identity "email address removed for privacy reasons" -PhoneNumber +4412345678 -PhoneNumberType DirectRouting
(if its direct routing, you may require a different vaue)
Can you provide an example of your usage for the `Set-CsPhoneNumberAsssignment` and the error you got?
As for the deprecation of the old Teams modules, Microsoft announced the deprecation of the earlier modules, and move to the newer 4.x code https://docs.microsoft.com/en-us/MicrosoftTeams/teams-powershell-supported-versions
As for the deprecation of the old Teams modules, Microsoft announced the deprecation of the earlier modules, and move to the newer 4.x code https://docs.microsoft.com/en-us/MicrosoftTeams/teams-powershell-supported-versions
Managed to fix it yes, for anyone else coming here the new\correct syntax for enabling someone with a DDI is:
Set-CsPhoneNumberAssignment -Identity "email address removed for privacy reasons" -PhoneNumber +4412345678 -PhoneNumberType DirectRouting
(if its direct routing, you may require a different vaue)