Cross-Tenant Migration with AD Connect

[chrisjako]

We are moving a school away from the LA to their own private Office365 tenant using microsoft's guide to a cross-tenant online only migration, I have successfully setup the source and target servers

 

I am stuck on configuring the users exchangeguid and emailaddress for the legacyDN entry needed for the endpoint migration to continue

 

All users are in Office365 via AD connect, i need to set each users -exchangeGUID and -emailaddress via powershell, however AD connect sets users up as a 'mailbox' rather then 'mailuser', of which set-mailbox -exchangeguid does not work within powershell (unrecognised command)

 

Has anyone come across this issue before and how did you resolve?

[HPlum78]

You should hopefully be using the v2 Exchange online module and have run the connect-ExchangeOnline command to connect up a session to EXO?

[chrisjako]

You should hopefully be using the v2 Exchange online module and have run the connect-ExchangeOnline command to connect up a session to EXO?

 

ExchangeOnlineManagement module? yes version 2.0.5 is installed

[chaplic]

Users are created as mailboxes if they are licensed for EXO and they don’t have attributes in certain fields, think it’s msexchmailboxguid off top of my head. So don’t give the users and exo license and and look at the -permanentlyclearmailboxinfo switch to delete the empty mailbox