The general process for doing this is:
In the background what will happen is:
How to set this up is described below.
The normal Office 365 migration requirements are necessary (see the earlier section). In addition, note that Azure management tools are required. These can be downloaded from: https://msdn.microsoft.com/en-us/library/azure/jj151815.aspx
If these components are not installed, the normal Office 365 migrations will still be successful, but processing of leavers will not be successful. They can be added at any time during the migration; it is not necessary to reinstall or modify the Office 365 module following their installation.
This determines how mailboxes and accounts will be created, using a token system. The following tokens can be used:
Note: PST ID and PST Number are applicable if PSTs are the source environment.
In addition to those, alphanumeric characters can be appended or prepended to the name of the mailbox in Office 365.
This is the location related to license allocation and is required to be chosen from the drop-down list. For a list of license restrictions by region, click here.
This should be a valid email domain that will be used to create mailboxes. Ex. @something.onmicrosoft.com
If enabled, the mailbox/user will be hidden from the Global Address List.
Prevent account for being used for interactive authentication.
Permits a selection of the type of hold being used by the leaver process. Currently only “Litigation Hold” is available to new installs.
Licenses can be loaded by clicking the Load Licenses button on the Archive Shuttle ribbon. These will also be loaded after adding a new Office 365 link.
A specific number of licenses can be used to process leavers. That number should be configured by clicking Set Rolling License Count. Licenses will be consumed up to that limit to migrate users, and will be freed up when Stage 2 completes on those users. When mailboxes are created, personal archives are also created.
The migration of the archive/container can then be performed. The process of mapping the users is the same as with a normal Office 365 migration, however, there is an additional option in the Mapping Wizard where you can select to use Leavers, and you should select an Office 365 Leavers Workflow.
A container can be processed as a leaver if one or more of the following is satisfied:
Note: Archives will be exported, but only the configured number of rolling licensed users will ingest data into the target.
The Stage 2 workflow (EnterpriseVault to Office 365 Leavers)?functions in a similar manner to the normal Office 365 workflows. There is an additional step in the workflow (Office365RemoveUser) that handles the removal of the user, resulting in an “inactive mailbox” appropriate for a naturally occurring leaver. . Once the license has been reclaimed from the removed user, additional users that require migration via the leavers process will begin.
During a migration, if Archive Shuttle detects that a mailbox is no longer present, the user is marked IsDeleted.
Then, you can select the user and select the Enable to Recreate button on the Bulk Mapping page. This enables the leaver mailbox to be created. The user’s data then gets ingested into the leaver mailbox, as described?above.
Or, you can automate the process by selecting the option to?Enable auto-recreate deleted O365 Users as Leavers?located on the Office 365 Module page within System Configuration under the Configuration section of the UI.