When migrating using the same email domain for two Office 365 tenants.

Hello,

We need to migrate 300 users about, from O365 Tenant (Source) to O365 Tenant (Target).
The first question is, can I share between the two Tenant the same e-mail domain during the coexistence phase?
To explain better, the goal is that during the migration time all users (migrated or not migrated) are able to send messages with the same e-mail domain, the original one.


I am thinking of migrating Source to the current domain and Target to xxx.onmicrosoft.com for the initial migration,
and then doing a differential migration just before the final domain MX switchover.
In that case, the source and target UPNs will be different for the initial and differential migration when using UPNs to Discover.
(Example.)
At initial migration: aaa@maindomain.com  to  aaa@target.onmicrosoft.com
For differential migration: aaa@source.onmicrosoft.com   to  aaa@maindomain.com

Are ODM licenses recognized and consumed by UPN?
If this is the case, do I need double the 600 licenses?

If I Discover&Match with ObjectID, will 300 licenses be enough?

Translated with www.DeepL.com/Translator (free version)


Thanks in advance for your answer.
Regards

Parents
  • The first question is, can I share between the two Tenant the same e-mail domain during the coexistence phase?

    Quest On Demand Migration (ODM)has an optional licensed service, Domain Coexistence, that can handle Address Rewriting between tenants. This will allow either a target user sending as the source email address or a source user sending as the target email address during a phased migration. This meets your technical requirement. 

    Quest on Demand also supports the migration of additional workloads other than mail. It can handle the Azure AD accounts and groups, OneDrive for Business, Public Folders, SharePoint Online, and Teams.

    Quest On Demand for Email (ODME) only handles email related content. (This is the ODME forum)

    Microsoft does not allow the same domain to be registered in two tenants at the same time. So to directly answer your question, no you can not "share" the domain at the between two tenants directly . You have to use an Address Rewrite system to address this short coming. 

    I am thinking of migrating Source to the current domain and Target to xxx.onmicrosoft.com for the initial migration,
    and then doing a differential migration just before the final domain MX switchover.
    In that case, the source and target UPNs will be different for the initial and differential migration when using UPNs to Discover.
    (Example.)
    At initial migration: aaa@maindomain.com  to  aaa@target.onmicrosoft.com
    For differential migration: aaa@source.onmicrosoft.com   to  aaa@maindomain.com

    When using ODM and it's Domain Coexistence function. It is recommended not to change the tenant membership for the domain until After the users has switched using the Desktop Update Agent (DUA). If tenant the domain is registered to prior to the switch, the DUA will not work. DUA does not support domain more prior to switch. If domain move prior to switch is required, the Client Update Agent supports this function and can be coupled with DUA to handle the ODB and Teams switches as well. There are other considerations required and steps that need to be executed to support this. 

    Are ODM licenses recognized and consumed by UPN?

    ODM consumes licenses when you match the source and target user objects. ODM matches on the ObjectID. So you would only require/consume 300 licenses. 

    If I Discover&Match with ObjectID, will 300 licenses be enough?

    Yes, 300 is licenses enough for this migration. 

Reply
  • The first question is, can I share between the two Tenant the same e-mail domain during the coexistence phase?

    Quest On Demand Migration (ODM)has an optional licensed service, Domain Coexistence, that can handle Address Rewriting between tenants. This will allow either a target user sending as the source email address or a source user sending as the target email address during a phased migration. This meets your technical requirement. 

    Quest on Demand also supports the migration of additional workloads other than mail. It can handle the Azure AD accounts and groups, OneDrive for Business, Public Folders, SharePoint Online, and Teams.

    Quest On Demand for Email (ODME) only handles email related content. (This is the ODME forum)

    Microsoft does not allow the same domain to be registered in two tenants at the same time. So to directly answer your question, no you can not "share" the domain at the between two tenants directly . You have to use an Address Rewrite system to address this short coming. 

    I am thinking of migrating Source to the current domain and Target to xxx.onmicrosoft.com for the initial migration,
    and then doing a differential migration just before the final domain MX switchover.
    In that case, the source and target UPNs will be different for the initial and differential migration when using UPNs to Discover.
    (Example.)
    At initial migration: aaa@maindomain.com  to  aaa@target.onmicrosoft.com
    For differential migration: aaa@source.onmicrosoft.com   to  aaa@maindomain.com

    When using ODM and it's Domain Coexistence function. It is recommended not to change the tenant membership for the domain until After the users has switched using the Desktop Update Agent (DUA). If tenant the domain is registered to prior to the switch, the DUA will not work. DUA does not support domain more prior to switch. If domain move prior to switch is required, the Client Update Agent supports this function and can be coupled with DUA to handle the ODB and Teams switches as well. There are other considerations required and steps that need to be executed to support this. 

    Are ODM licenses recognized and consumed by UPN?

    ODM consumes licenses when you match the source and target user objects. ODM matches on the ObjectID. So you would only require/consume 300 licenses. 

    If I Discover&Match with ObjectID, will 300 licenses be enough?

    Yes, 300 is licenses enough for this migration. 

Children
No Data