asked on 9/21/2021

Exchange 2010 Hybrid migration to Microsoft 365 - Domain not an accepted domain for your organization

We are trying to set up a new Hybrid migration between Exchange 2010 SP3 and Exchange 365.

Migration detailsType : ExchangeRemoteMove
Direction : Onboarding
Status : Completed with errors
View details

Mailbox statusSynced mailbox: 0 of 1
Finalized mailbox : 0 of 1
Failed mailboxes : 1

StatisticsCreated by : Admin
Created time : 9/21/2021, 2:12:47 PM
Start time : 9/21/2021, 2:12:46 PM
Complete after : 9/21/2021, 2:12:45 PM
Last synced time :

Associated endpointHybrid Migration Endpoint - EWS (Default Web Site)

Migration fails with - Domain not accepted.

- have removed the company.local domain from the Default policy

- delete the .local entry on the one mailbox that is being tested.

- check and can see that the company.com is authoritative in the Exchange admin center.

Any help on this would be much appreciated

Update Note: Using Exchange 2010 to create a "remote move request" works

Exchange Microsoft Microsoft 365

Last Comment

M A

9/23/2021

ASKER CERTIFIED SOLUTION

M A

9/21/2021

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

Simon Walton

9/21/2021

ASKER

Used the above and get the following

Get-mailbox Helpdesk | select -ExpandProperty helpdesk@company.com
The operation couldn't be performed because object 'Helpdesk' couldn't be found on 'LO4P268A08DC007.GBRP265A009.PROD.OUTLOOK.COM'.

Any ideas

M A

9/21/2021

Run the second command in onprem server

Simon Walton

9/21/2021

ASKER

That would be the same result as we can already achieve using Exchange 2010 EMC "remote move request"

Is it not possible to do the same from within exchange.microsoft.com? that is where we see the error.

M A

9/22/2021

HI Simon.
Please try to remove the move-request initiate a new request from O365

Simon Walton

9/23/2021

ASKER

Get-AcceptedDomain | select company.com

Created new migration batch with one mailbox

Unfortunately, we get the same error as mentioned in 1st statement.

Conclusion - On-premises EMC "remote move request" is working
Microsoft365 ECA "Domain, not an accepted"

We are no further forward with this, and can only feel that there is a connection issue inbound to the on-premises exchange

Simon Walton

9/23/2021

ASKER

Update: We have been successful with an ECA remote move

Not sure if it was a timing issue after running Get-AcceptedDomain | select company.com

M A

9/23/2021

Glad to know you migrated.

Cheers