Jason Oldershaw
asked on
Migrating mailbox over Exchange Hybrid deployment failing - "not an accepted domain"
I'm having problems moving a mailbox from an on premise Exchange 2013 server to Exchange Online. Here are the steps I go through -
It takes 7 minutes to go from "synching" to "failed". The report is below -
"Error: MigrationPermanentExceptio n: You can't use the domain because it's not an accepted domain for your organization. --> You can't use the domain because it's not an accepted domain for your organization."
Has anyone experienced this error?
- Sign in to Exchange Online admin
- Recipients > Migration
- Add > Migrate to Exchange Online
- Select Remote move migration
- Select a test user
- Select a migration endpoint
- Confirm endpoint, which is showing mail.domainname.com
- Give it a batch name,
- a target deliver domain, which is companyname.mail.onmicroso
ft.com - Automatically start
It takes 7 minutes to go from "synching" to "failed". The report is below -
"Error: MigrationPermanentExceptio
Has anyone experienced this error?
Check the email addresses for each of your mailboxes to see what the Default (or Reply To) email address is set for. If that email address's domain is not added to Office 365, the migration will fail. If it is set to by domain.local or something similar, you'll need to change the default email addresses to match the domains you have added to Office 365.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
UPN was the ticket, thanks.
Also, it's worth waiting for AD sync to have completed a sync before attempting a new migration after sorting UPN.
Also, it's worth waiting for AD sync to have completed a sync before attempting a new migration after sorting UPN.