If your business has legal, regulatory, and technical standards to meet for content security and data use, you’re in the right place. You can also use Office 365 security and compliance features if your business has specific security requirements for controlling sensitive information. In this section, you can also find out how Office 365 uses encryption and other security technologies to protect your data.
To enable a remote mailbox and still be able to migrate it between onpremises and office 365 you have to do the following steps :
Open a remote PowerShell connection to Office 365:
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
And run the following command :
Get-Mailbox UPN | fl ExchangeGuid
You should now get the ExchangeGuid copy this because you are going to need this later.
Open the Exchange Management Shell on-premises Exchange Server and run the following cmdlets:
Enable-RemoteMailbox UPN -RemoteRoutingAddress Username@domain.mail.onmicrosoft.com
Set-RemoteMailbox UPN -ExchangeGuid ExchangeGuid
Source : http://blogs.technet.com/b/exchange/archive/2014/03/24/mailbox-migration-performance-analysis.aspx
When you’re migrating on-premises mailboxes to Office365, there are a lot of factors that can impact overall mailbox migration speed and performance. This post will help you investigate and correct the possible causes by using the AnalyzeMoveRequestStats.ps1 script to analyze the performance of a batch of move requests to identify reasons for slower performance.
The AnalyzeMoveRequestStatsscript provides important performance statistics from a given set of move request statistics. It also generates two files – one for the failure list, and one for individual move statistics.