Share via

Migration Error - The subscription for the migration user xxx couldn't be loaded

Anonymous
2015-10-05T19:58:48+00:00

Exchange 2013 - Exchange-RemoteMove Migration to and from a tenant synced with DirSync

Every user comes up with the error "The subscription for the migration user xxxx couldn't be loaded. The following error was encountered:The subscription that was found for this user did not match the user information."

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2015-10-10T20:51:54+00:00

    Hi GeoffNorthcott3087,

    Do you have any updates about the issue?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-10-08T02:45:38+00:00

    Hi GeoffNorthcott3087,

    After reviewing the whole post, do you mean the issue occurs after you move local users to cloud or vice versa? Regarding “most of the users were created in Office365 prior to establishing the hybrid Exchange integration”, we need to associate these users with on premise object after you deploy Hybrid. 

    To further check it, could you let me know if the migrated mailboxes are working fine, and just report the error message?

    Regards,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-10-07T19:21:47+00:00
    1. Yes - Exchange hybrid is deployed
    2. Synced with Active Directory - most of the users were created in Office365 prior to establishing the hybrid Exchange integration
    3. From the Office 365 section of the Hybrid Exchange Admin Center
    4. GUID values of the remote-mailbox and AD Exchange GUID are matched

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2015-10-05T21:53:20+00:00

    Hi GeoffNorthcott3087,

    Since the issue is not what we commonly see, to understand the issue more clearly, can you please provide the following information?

    1. Do you mean that you have deployed Exchange hybrid with Office 365?
    2. What’s the status of the users show in the Office 365 Admin Portal? Is it “In Cloud” or “Synced with Active Directory”? Do you mean the users are created in the on-premises and synced to Office 365? If so, have you enabled the Exchange Online mailboxes for these users before the hybrid is deployed?
    3. Where did you initial the mailbox move, from the on-premises Exchange server or from Exchange Online Admin Center?
    4. Can you please check the ExchangeGUID value for the problematic users from both on-premises and Exchange Online and see if they are the same? If not, please set the on-premises Exchange to the same value with Exchange Online. To check that, please follow the steps below:
    5. Open the Exchange Management Shell on the on-premises server, and then run the following command to check whether the ExchangeGUID property of the on-premises remote mailbox is set: Get-RemoteMailbox <alias of cloud mailbox to move> | Format-List ExchangeGUID. If the ExchangeGUID property returns all zeros, then it means the value isn't stamped on the on-premises remote mailbox.
    6. Open Windows PowerShell (don't use the Exchange Management Shell), and then connect to Exchange Online. For more info about how to do this, see Connect to Exchange Online Using Remote PowerShell.
    7. Run the following command to retrieve the value of ExchangeGUID property of the mailbox that you want to move: Get-Mailbox <MailboxName> | Format-List ExchangeGUID.
    8. Run the following command to set the value of the ExchangeGUID property on the on-premises remote mailbox to the value that you retrieved in step 3: Set-RemoteMailbox <MailboxName> -ExchangeGUID <GUID>
    9. Force directory synchronization. For more info about how to do this, see the "Force directory synchronization" section of Synchronize your directories.

    Please post back with the updates at your convenience and we will further check the issue for you.

    Was this answer helpful?

    0 comments No comments