Migration control center, migration workstation and Azure AD Domain (4328803)

Migration control center, migration workstation and Azure AD Domain

We are migrating emails from Domino server to Microsoft 365. The Documentation is not clear about the requirement: should Migration control center, migration workstations join Azure AD Domain? or we only need accounts with Global Administrator role on Microsoft 365 to configure Lotus Notes client, outlook and NotesMigrator.nsf? The existing Domino server, Migration control center, migration workstations are in the same subnet. They are NOT in the same Microsoft 365 that is going to migrate to.

The machine for the migration worker does not need to be domain joined to the tenant. The migration account must have access to the target tenant per our product documentation. The migration worker will prompt a request for the account used for migrations. This account must have full access to the target mailboxes per the following Migration Account Permission Requirements.
• There are two accounts used on the migration workstations for the actual migration of data: Exchange migration account and the Lotus Notes ID.
Exchange Migration Account:

o Must be a mailbox enabled user object
o Password should be set to never expire
o Must be used to log into each of the migration worker machines
o Is set to have Full Access to Exchange mailboxes during the Provisioning process

Note: When multiple migration workstations are configured, several Migration accounts can be used and configured individually for migration workstations. This can be used to minimize the impact of Exchange or Office 365 throttling policies.

For the person(s) performing the migration process there are two accounts to consider when performing migrations: The Active Directory account (or Office 365 Administration account) that is logged into the machine being used and the Notes ID that is being used to access the Notes Migrator Domino application.
Active Directory Migration Operator Requirements:
(PS represents PowerShell and ADO represents direct calls to Active Directory):

o Ability to run Exchange PowerShell scripts (either remote or local to the workstation), generally the Exchange roles Organization and Recipient Management (PS)
o Ability to manipulate user objects, specifically modify the targetAddress, proxyaddresses, mail and msExchPoliciesExcluded attributes (ADO)
o Ability to delete contact objects created by the directory synchronization process (ADO)
o Ability to update Distribution List member lists (ADO)
o Ability to create and modify Distribution List objects (ADO/PS)
o Ability to create and modify Mail Contact objects (PS)