![]() ![]() However once you’ve fixed the rest of the errors and just need to change the SIPProxyAddress / ProxyAddresses fields, all you’ll need to do is remove the Microsoft Teams and supporting licenses/apps from the user account, wait half hour and then add them again. The error in the screenshot isn’t actually right, as the ProxyAddresses it’s referring to didn’t come from AD, but they were actually generated by Azure AD/Microsoft Teams. Secondly this will provide you with all of your attributes to help you find out at a glance where your errors are. This will provide you with two key insights, firstly you’ll get a list of any validation errors that Microsoft have with your account information, such as here, it doesn’t like the trailing space and is informing us the ProxyAddresses field is not in the correct format. You’ll then get an output similar to the below. There are two key steps that can help you resolve this issue promptly.įirstly try running the following command from a Microsoft Teams PowerShell session: Get-CsOnlineUser "User name" | fl userprincipalname, sipaddress, sipproxyaddress, email, proxyaddresses, windowsemailaddress, interpretedusertype, mcovalidationerror Working with Microsoft, they suggested many things, such as trying to change the proxy address attributes to include a record, or setting attributes via Exchange Online but nothing changes this SIP Address once it has been created. This is expected! If your users are being synchronized from Active Directory, Azure AD doesn’t want to create conflicts. This parameter is restricted within Remote Tenant PowerShell. Any attempts to make changes to this via the Microsoft Teams PowerShell cmdlet Set-CsUser would result in the following error. Microsoft’s initial instruction for this would be to amend the msRTCSIP-PrimaryUserAddress attribute within AD, however this customer had never used OCS/Lync/Skype for Business, so they didn’t have this within their AD schema. Whilst most of the attributes were automatically corrected once the account had been corrected and AD had synchronized, unfortunately Microsoft Teams kept this incorrect SIPProxyAddress. When the user had synchronised to AzureAD with this attribute and their Microsoft 365 licensing had deployed, this created a SIPProxyAddress with this trailing space. A customer of mine had created a user but accidentally left a trailing space after their UPN. I had an interesting issue over the past week that stumped Microsoft Support for a while. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |