none
"Error: MigrationMRSPermanentException: Error: Failed to resolve tenant name" during Remote Move migrations

    Question

  • For the past days we noticed random move requests failing within a migration batch with the error:

    Error: MigrationMRSPermanentException: Error: Failed to resolve tenant name *tentant name*

    Sometimes resuming the move request fixes the issue, this is the nth issue now with remote move mailbox migrations. Has anyone else also got this error?

    Monday, June 25, 2018 5:57 AM

All replies

  • We have had the below case open since Wednesday, which took the engineer two days to realize that there was a migration issue going on in O365. I have not heard anything back since Friday. We tried a new migration batch this morning and it will not even load the initial page.

    EX142435 - Exchange Online - Service Degradation Title: Mailbox migration error User Impact: Admins may receive an error when creating new mailbox migration batches. More info: The error received is: "MigrationProvisioningPermanentException: Method not found". Migration batches encountering this error will not be able to start. Note that this issue does not affect batches already in progress, only newly-created ones. Current status: We've determined that a standard update intended to improve service functionality caused unexpected impact to the ability to create new mailbox migration batches. We're working to develop and test a fix to remediate impact. Once we've confirmed that the fix is successful, we'll begin our deployment to the affected environment. Scope of impact: This issue may potentially affect any of your admins attempting to create new mailbox migration batches. Start time: Tuesday, June 19, 2018, at 12:00 PM UTC Preliminary root cause: A standard update intended to improve service functionality caused unexpected impact to the ability to create new mailbox migration batches. Next update by: Friday, June 22, 2018, at 6:30 PM UTC

    Monday, June 25, 2018 3:01 PM
  • Hi Najib,

    As the issue does not occur on every remote move migration batches, I recommend you refer to the following article, to follow the troubleshooting steps in this blog when the issue occurs again, then check if get any clues to help resolve the issue:

    Troubleshooting issues where the hybrid migration endpoint cannot be created 


    Best Regards,
    Niko Cheng


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, June 26, 2018 7:56 AM
    Moderator
  • Hi Najib,

    Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.


    Best Regards,
    Niko Cheng


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, July 04, 2018 9:25 AM
    Moderator