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)
Editing my own response:
This deprecation message occurs on server side.
You can confirm that by last line of error message:
+ FullyQualifiedErrorId : InternalServerError,Microsoft.Teams.ConfigApi.Cmdlets.SetCsUserIt's an InternalServerError.
You must update your server side to avoid this errors.
- Hi, no i had confirmation from Microsoft that they have been deprecating that specific cmdlet over their tenants, they dont do it globally in one hit, but spread it out over a few weeks\months. Our tenant was obviously affected recently.
So it was as intended, it would just be nice if they told you when your specific tenant is affected...