Looks like there was some issue at Microsoft backend. The Gsuite term was changed to Google Workspace. I have created a new migration end point with new JSON file and that have fixed the issue.
Office 365 Migration issue due to subscription
Hi Team,
I am in process of migrating 200+ user mailbox to Office 365. Where most of all user mailbox got migrated except 2. One is in synced state and another one is still in migration (due to huge size). For these 2 mailbox all of the sudden i noticed that the EAC gives the error message as "
The subscription for the migration user ****@keyman .com couldn't be loaded. The following error was encountered: A subscription wasn't found for this user.." For the synced mailbox the license was unassigned (not sure how) and so I have assigned it and resumed the migration but still the same.
Please help
Exchange Online
Exchange | Exchange Server | Management
Microsoft Security | Microsoft Entra | Microsoft Entra ID
1 additional answer
Sort by: Most helpful
-
Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator
2021-02-01T23:52:01.553+00:00 Hi @Sabarish Natarajan ,
Based on the Troubleshooting guide it looks like you may need to stop and restart the migration batch again to get this resolved.
Resolution
- Stop the migration batch.
- Make sure that the migration batch has reached the “Stopped” state.
- Restart the migration batch. This will re-create the missing public folder migration request
Another solution you can try if that does not work is this suggestion in this blog post by Tech Trainer.
- Run the following command: Get-RemoteMailbox UserB | Format-List ExchangeGUID
- Run this command on Exchange Online: Get-Mailbox UserB | Format-list ExchangeGuid
If the GUIDS are not matching, that would be the problem.
The resolution is to run the command below and rerun “Complete-Migrationbatch” cmdlet:
Set-RemoteMailbox UserB -ExchangeGUID 4a502e5e-5064-4f60-b691-845bdaf94113 #Online MailboxGUID
If the “Get-RemoteMailbox” does not return anything for the user it means that it wasn’t migrated successfully.
In that case, you have to remove the online mailbox for the user as described in the post.
I would recommend checking this post as well.