The Archive Shuttle Office 365 module ingests data into Office 365 mailboxes or Personal Archives using the Advanced Ingestion Protocol (AIP) and optionally Exchange Web Service (EWS), utilizing Office 365 ‘service accounts’.

Configure the Office 365 Module

The Office 365 module needs credentials supplying to it in order to be able to connect to Office 365. To provide these credentials, follow the steps below:

  1. Log in to the server or workstation where the Office 365 Module is currently deployed using the account that is used to run the Archive Shuttle Office 365 Service.
  1. Click Start and locate the Credentials Editor, and then click it to launch the editor.
  1. In the small application that launches, click Add and enter the account UPN and password for the account described in the prerequisites section.
  1. Click OK on the UPN/Password dialog.
  1. Click Save in the Credential Editor, and close the application

These credentials will be used by the module when it connects to Office 365.
The final step in configuring the module is to start the Office 365 Module Service using the Windows Service Control Manager.
Note: Additional configuration may be necessary in order to obtain good ingest performance, and/or to work in environments where web/HTTP proxies are used. These are described in the Installation Overview.
Note: Alternatively, you can use Modern Authentication (OAuth) instead of service account credentials. To do this, add the Modern Authentication (OAuth) credentials using the Credential Editor, and also select the Use modern authentication (OAuth) option on the Office 365 Module settings.

Configure Application Impersonation

In order for the accounts specified above to be used to ingest data into Office 365 mailboxes of Personal Archives, the Application Impersonation role needs to be assigned to the user. This can be done in the Office 365 Portal or via PowerShell. To do the required steps using PowerShell, follow the steps below:

  1. Log in to a server that has Windows PowerShell installed
  1. Issue the following commands in PowerShell, comments and responses are noted below each command:

$User-Credential = Get-Credential

Supply values for the following parameters:

Credential

A pop-up will appear asking for a username and password. The Global Administrator that needs to have Application Impersonation granted to them should be input

$Session = New-PSSession –ConfiguratioName Microsoft.Exchange –ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential –Authentication Basic –AllowRedirection

This connects a PowerShell session to Office 365 using the credentials that were just entered.

Import-PSSession $Session

This activates the above session. It may take a few seconds for this to return to the command prompt.

New-ManagementRoleAssignment –Name:VaultAdminImpersonation –Role:ApplicationImpersonation –User:<upn>

This grants the user specified the Application Impersonation role.

Note: Customers may have a standard system for naming role assignments. That naming convention can be used, but the required role is fixed by Office 365 – Application Impersonation.

Configure Office 365 Connection Rather Than Autodiscover

Normally the Office 365 Module will use the default configuration and be able to contact Office 365. In some situations it might be necessary to configure a specific URL to access Office 365. This can be done on the System Configuration page as follows:

  1. Go to the System Configuration page in Archive Shuttle.
  1. Click on Office 365 Module
  1. Locate the Connection URL entry near the bottom, and update it to show the required value.
  1. Click on Save to commit the changes.

Configure Access to Office 365 Through a Proxy Server

If the migration environment needs to use a web proxy to access HTTP or HTTPS sites on the internet, then the Office 365 module needs to be configured to also route traffic that way.

  1. Log in to the server or workstation where the Office 365 Module is currently deployed using the account that is used to run the Archive ShuttleOffice 365 Service.
  1. Browse to the folder where the module is installed, and locate the file ‘ArchiveShuttle.Module.Office365.exe.config’ and open it in a text edit.
  1. Remove the <!—and –> from the line containing the ‘defaultProxy’ and set the value to be one of:

IEConfig

AutoDetect

WinHttpConfig

NoProxyServer

  1. Save and close the file.

 

Restart the Office 365 Module service using Windows Service Control Manager.

Configuring Modules to use HOTS

HOTS is a feature with Archive Shuttle which allows for less bandwidth usage for migrations to Office 365 by combining a highly-optimised transfer system with storage of extracted data taking place in Microsoft Azure. The following diagram presents an overview of HOTS:

Requirements

For migrations from legacy archives to Office 365 using HOTS the following needs to be considered:

  • Using HOTS is supported for all currently supported sources, when migrating to Office 365 mailboxes or Personal Archives.
  • More CPU uses might be needed on the source environment in order to create the HOTS-format data
  • An Azure Storage Account must be configured and used for storing the extracted data
  • All export and import modules must have been configured with the connection string to the Azure Storage Account
  • A bridgehead server running the ingest and shortcut processing module should be deployed in Azure to facilitate the ingestion of the data from the Azure Storage Account.

Bridgehead Server

The bridgehead server in Azure should consist of a virtual machine with the following specification:

Component Configuration
Processors (cores) Minimum 4, Recommended 8
CPU Speed 2 GHz
Memory Minimum 16 GB, Recommended 32 GB
Hard disk Minimum 2 GB of free space

Note: Microsoft Azure machine classes change frequently so a specific machine class is not specified here.

PowerShell Execution Module

This module is responsible for executing PowerShell commands in the Stage 2 Workflow for a mapping. It is recommended to have one of these installed in the environment.
It is not necessary to associate this module with a particular link, that process is done automatically, and is controlled by the Core.
Note: This module requires .Net Framework 4.5.2

Print Friendly, PDF & Email