VS benefit upgrade of O 365 E3 to Microsoft 365 E5

Talha Khan 1 Reputation point

Dear Members, We followed this article to 'upgrade' our VS Ent. subscription to MS 365 E5 : https://learn.microsoft.com/en-us/visualstudio/subscriptions/vs-m365 But on new tenant users they belong to or have newtenant.onmircosoft.com domain cannot be recognized by mover IO migration tool. Mover Support says it is Microsoft issue and Microsoft keep saying it is mover issue - my question is that without our actual AD users how will anything work anyway? So we are sitting on ticking time because old tenant is now marked for permanent deletion and all data will be lost. If anyone else has successfully tried and follow the article mentioned above to move from O 365 E3 benefit to MS 365 E5, kindly share your experience and any recommendations would be highly appreciated .. Thanks, Talha

Microsoft 365
Microsoft 365
Formerly Office 365, is a line of subscription services offered by Microsoft which adds to and includes the Microsoft Office product line.
4,122 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Barry Evanz 235 Reputation points

    After some investigation, it has come to my attention that there is a known issue with the Mover IO migration tool, which is currently impeding its ability to identify users in the new tenant. Microsoft and Mover IO are collaborating to rectify this issue, but as of now, there is no definite timeline for a resolution. However, while awaiting the tool's fix, there are a couple of alternative approaches you can consider to proceed with your migration.

    Firstly, you could explore using a different migration tool. Several alternative migration tools, such as BitTitan MigrationWiz and Skykick Migration Suite, are available. Switching to one of these options might help you migrate your users without the roadblock you're currently encountering. Another viable but more labor-intensive method involves manually migrating your users. Although it demands more time and effort, manual migration is a feasible option. Detailed instructions for this approach can be found in Microsoft's documentation.

    Ensure your new tenant is meticulously configured before initiating the migration process, including domains, users, and permissions. Pilot the migration process in a staging environment as a preparatory measure. This allows for the identification and resolution of potential issues before undertaking the migration in a production environment.

    Lastly, always have a contingency plan in place to address any unexpected hiccups during the migration process. This could involve maintaining a backup of your old tenant or implementing a procedure to restore data from backup in the event of a mishap.

    0 comments No comments