locked
Move-CsUser : HostedMigration fault: Error=(201), Description=(Cannot find user in Active Directory with the following SIP URI: "<sip address>") RRS feed

  • Question

  • I upgraded Lync Server 2013 to Skype for Business Server 2019. It went perfectly OK. Now I'm trying to configure hybrid to Office 365. I've followed all the steps, but when I move an OnPrem user to Teams, I get the following error message: 

    Move-CsUser : HostedMigration fault: Error=(201), Description=(Cannot find user in Active Directory with the following SIP URI: "<sip address>"

    We have Azure AD Connect set up many years ago. It works well and we run the Exchange Hybrid. It is not set up with application filter or attribute filter. Therefore, I expect all attributes to be synced to Azure. Also msrtcsip-primaryuseraddress. What could be wrong?
    Wednesday, July 1, 2020 8:31 AM

Answers

  • After some more digging, I found out that I was using wrong HostedMigrationOverrideUrl when migration. After fiksing that, I could move the users.
    • Marked as answer by mdahling Thursday, July 2, 2020 10:25 AM
    Thursday, July 2, 2020 10:25 AM

All replies

  • Hi mdahling!

    According to your error message, it seems you’re trying to move a user by referencing a SIP address that doesn’t exist in your AD.

    We recommend you try to check the problem user in the control panel and confirm the SIP address matches the address your using in your move command.

    Also please check if you’ve assigned the problem users different SIP domain suffixes like a.local instead of the routable domain.

    Besides, try to force replication from Azure AD Connect with command: Start-ADSyncCycle -PolicyType Initial and wait for some time, then test if this issue can be fixed.

    For more details about how to move user on-premise to online, you can refer to:

    https://docs.microsoft.com/en-us/SkypeForBusiness/hybrid/move-users-between-on-premises-and-cloud?toc=/SkypeForBusiness/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json&redirectedfrom=MSDN

    Best Regards,
    Jimmy Yang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
    Thursday, July 2, 2020 3:09 AM
  • After some more digging, I found out that I was using wrong HostedMigrationOverrideUrl when migration. After fiksing that, I could move the users.
    • Marked as answer by mdahling Thursday, July 2, 2020 10:25 AM
    Thursday, July 2, 2020 10:25 AM
  • Hi mdahling!

    Thanks for sharing your solution about this issue!

    I will provide a brief summary of this issue later.

    Best Regards,
    Jimmy Yang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, July 3, 2020 6:35 AM