This describes mail routing during a Dell Quest Migration Manager Migration from On-Prem Exchange to Microsoft Office 365
Co-existence routing during the migration.
Step 1, add the user to the Dell Active directory Migration tool (DMA).
This step creates the GAL and sets initial mail routing.
When a user is added to the Dell Active directory Migration tool (DMA). A mailuser (similar to a contact) is added to Office 365 and the ExternalEmailAddress attribute set. This tells Office 365 to send the mail externally (back to on-prem) through a connector in O365 scoped to on-prem.
Step 2 Add the user to a Quest Mail or Calendar Sync
In office 365
Once the user is put into a Dell Migration Manager mail or calendar sync, they become licensed in O365 (licensing creates a mailbox).The Exchange Migration Manager (EMM) then adds an address using the users GUID to the ForwardingSmtpAddress in office 365. This forwards all mail back to on-prem from users in Office 365. (No outside mail is arriving in O365 yet)
The DeliverToMailboxAndForward attribute is left at “False” (default).
On-prem the Exchange Migration Manager (EMM) adds a proxy address using the users GUID on-prem (same address that is stamped in the ForwardingSmtpAddress attribute in Office 365)
Note: if routing is not working for a user, verify these addresses match. This is mail from Office 365 to on-prem.
This can be set by running the following command in an Office 365 shell.
Mail from on-prem to office 365 is handled by the Dell Exchange Migration Manager. This allows for more than just mail forwarding, but also deletes, moves etc and keeps the mailbox in sync.
Step 3 Flip the user
In Office 365
When a user is “flipped” or switched as it is referred to in the tool, Dell Exchange Migration Manager removes the forwarding address in Office 365. All mail now remains in Office 365.
Once a user is flipped EMM sets the targetAddress attribute to the USI user account. This can be the GUID@mydomain.onmicrosoft.com or the firstname.lastname@example.org, but the address in the targetAddress must be in the proxy list in O365. If routing for this user is an issue, make sure the addresses match. Check this with adsiedit.msc in USI.
Get-QADUser username -IncludeAllProperties | select name,targetaddress