Follow

MCO validation error upon provisioning teams user

When provisioning a user for VIA UC Microsoft Teams, Microsoft requires either SIP address for the user to already exist, or, due to a lookup when creating the SIP address, the DNS to be set to Microsoft 365. 

Often, it isn't possible to change the DNS to Microsoft 365 just yet, as your users will continue using VIA UC Skype for Business throughout the Teams setup process. This means we cannot rely upon the provisioning process creating the SIP address, and so must ensure it is in place already. 

Those using Azure AD may add the proxy address using the below steps. For instructions based on-premises AD (where Azure AD Connect / DirSync is in place), please skip to the relevant section. 

Adding SIP proxy address attribute in 365

  1. Browse to the Microsoft 365 admin portal and login with an admin account
  2. Enter the Exchange Admin Center
  3. Select 'Recipients'
  4. Double click the appropriate user
  5. Select 'Email Address'
  6. Note no entry of type SIP exists, then click the + icon to add a new entry
  7. Add the relevant SIP record by clicking the third radio button and typing SIP, then add the email address below
  8. Click Save
  9. Report back to VIA that this is complete and the username edited, in order that VIA can test and confirm positive outcomes
  10. This may need to be repeated for other users based on next actions determined by VIA

 

Adding SIP proxy address attribute in on-premises Active Directory

  1. Open Active Directory and find the appropriate user
  2. Double click the user to view the properties
  3. Select the 'Attributes' tab
  4. Scroll to find 'proxyAddresses'
  5. Select this and click Edit
  6. Note no entry of type sip exists, and then add sip:useremailaddress@yourdomain.com ensuring that the new entry displays in the bottom half of this window, and then click OK
  7. Click Apply, and OK
  8. Perform an Azure AD Connect / DirSync synchronisation. You can achieve this by performing a delta sync in powershell, or by waiting for the usual synchronisation interval. To perform a delta sync: 
    1. Ensure you are using a server running Azure AD Connect / DirSync and then load powershell (right click, run as administrator)
    2. Run     Import-Module ADSync
    3. Run Start-ADSyncSyncCycle -PolicyType Delta
    4. Check the recipient in Exchange Admin Center in 365 (recipient properties, email addresses) to ensure you see the SIP entry in 365. 
  9. Report back to VIA that this is complete and the username edited, in order that VIA can test and confirm positive outcomes
  10. This may need to be repeated for other users based on next actions determined by VIA

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request