You are on page 1of 7

Uploading PST to Azure and mapping to user mailboxes:

The process below does not need to be done all at once and can be broken up into several different
upload/import jobs.
Average speed is around 4mb per second or roughly 1GB every 4 minutes.
 Create a share on a file server and share it out, this will be used to store all of the user PST files
 Log into O365 as admin and open the admin console, preferably an admin account that is not
the default onmicrosoft.com account. The user you log in with will need global admin rights in
O365 to perform the migration.
 Open the Exchange management console
 Click on “Permissions” on the left, then admin roles at the top center, Organizational
Managemnt
 Now click the plus symbol under “Roles

 Select the “Mailbox Import Export and click “Add” then “OK”

 Under the “Members” section click the plus symbol and add a member. The user can’t be the
default admin@onmicrosoft.com account and must be a global administrator.

 Go back to the Office 365 admin center. If you logged in with the default O365 administrative
account you will now need to log out and log back in with the account you just setup as a
member in the new role.
 Once in the admin center on left expand setup, then click “Data Migration”
 Click on “Upload PST files

 On a machine you will be using to upload the PST files, preferable the file share where they
reside or the Exchange server, download the Azure file copy PowerSHell commands
http://aka.ms/downloadazcopy
 Click the “Import New Job” button. If you do not see these buttons, then replication has not
occurred and you do not have the mailbox import export role yet.

 Give the job a name and click next. The name cannot contain any capitol letter, spaces or
hyphens.
 Select the “Upload your data” and click “Next”
 Retrieve the SAS URL and copy it to the clipboard. Then paste it into a notepad on the machine
you will be running the Azure upload PowerShell.
 Open an elevated PowerShell window and change directories to the directory where you
installed the AzCopy.exe tool in Step 1. If you installed the tool in the default location, go to
%ProgramFiles(x86)%\Microsoft SDKs\Azure\AzCopy
 Make sure your data is as you want it prior to proceeding to the next step, as MS warns the
following,
Important: You can't use the Azure Storage Explorer to delete PST files that you've uploaded to
the Azure blob. If you try to delete a PST file, you'll receive an error about not having the
required permissions. Note that all PST files are automatically deleted from your Azure storage
area. If there are no import jobs in progress, then all PST files in the ingestiondata container are
deleted 30 days after the most recent import job was created.
 Enter the following in the PowerShell window changing the source and destination locations.
.\AzCopy.exe /Source:<Location of PST files> /Dest:<SAS URL> /V:<Log file location>
Enclose the source location and the URL in quotes. Example below
AzCopy.exe /Source:"\\vstorage\storage\PSTMigrationfiles"
/Dest:"https://f95d8cb311174eb89f48a51.blob.core.windows.net/ingestiondata?sv=2012-02-
12&se=2018-01-18T21%3A27%3A59Z&sr=c&si=IngestionSasForAzCopy2017121921274399"
/V:\\server\share\PSTMigrationfiles\uploadlog.txt
NOTE: If you have any sort of policy on the machine you are going to run this command from
that will log you out after inactivity, exclude the machine from the policy or use a different
machine as logging out will kill the upload process and will need to be started again.

You should see progress similar to the below


See link below for a list of the switches that can be used with the upload process
https://support.office.com/en-us/article/Use-network-upload-to-import-your-organization-s-
PST-files-to-Office-365-103f940c-0468-4e1a-b527-cc8ad13a5ea6?ui=en-US&rs=en-
US&ad=US#step2

 Download the Azure storage explorer tool from the following line and install it on the same
machine you are uploading the PST files.
https://azure.microsoft.com/en-us/features/storage-explorer/
 On the wizard that comes up on startup choose, “Use a connection string or shared access
signature URI’ and click “Next”

If you closed the wizard, simply right click the “Storage Accounts” on the left pane and chose
“Connect to Azure Storage”.
 Select the, Use a SAS URI and copy and paste the same URI you used in the upload string and
click “Next” and then “Connect”.
 You should now be able to see the uploaded PST files. Verify that the data is what is expected
before moving on.
 When you are done exploring the data to verify it, right click the “ingestdata” on the left and
then “Detach” to be disconnected from the Azure storage.

 You will now create the mapping file that will map which PST are to go into which mailbox.
 Create a CSV file with the following headers. All headers must be in the file.
Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,ContentCodePage,SPFileContai
ner,SPManifestContainer,SPSiteUrlc
 In the first column, since we are uploading PST files, we will use “Exchange” with a capitol “E”.
 If you left the default upload spot without supplying a sub folder name, you will leave the
“FilePath” empty
 Under the “Name” Column, enter in the name of the PST file.
 Under the “Mailbox” column, enter in the users full email address where the PST will be
importing
 Under the “IsArchive” column, enter either “FALSE” or “TRUE” in all caps to specify if this is an
archive or not.
 Under the “TargetRootFolder” column, enter in the root where you want the PST to be dropped.
If left blank, the PST will be imported into their existing inbox. If you enter “/”, the PST will be
imported in the root of the inbox in a new folder named “Imported”. I tend to copy the name of
the .PST and place it in the TargetRootFolder column with a “/” in front.
 Leave the last columns blank as they are not used but are needed to remain for the mapping.
 Example below and the following link explains each column in detail.
https://support.office.com/en-us/article/Use-network-upload-to-import-your-organization-s-
PST-files-to-Office-365-103f940c-0468-4e1a-b527-cc8ad13a5ea6?ui=en-US&rs=en-
US&ad=US#step4

 Go to https://protection.office.com and sign in using the credentials for an administrator


account in your Office 365 organization.
 In the left pane of the Security & Compliance Center, click Data governance and then click
Import.
 On the Import page, click New import job.
 Type a name for the PST import job, and then click Next. Use lowercase letters, numbers,
hyphens, and underscores. You can't use uppercase letters or include spaces in the name.
 On the Do you want to upload or ship data? page, click Upload your data and then click Next.
 Click the I'm done uploading my files and I have access to the mapping file check boxes, and
then click Next.
 On the Select the mapping file page, click Select mapping file to submit the PST Import mapping
file
 After the name of the CSV file appears under Mapping file name, click Validate to check your
CSV file for errors

The CSV file has to be successfully validated to create a PST Import job. Note the file name is
changed to green after it's successfully validated. If the validation fails, click the View log link. A
validation error report is opened, with a error message for each row in the file that failed.
 After the PST mapping file is successfully validated, read the terms and conditions document,
and then click the checkbox.
 Click Save to submit the job, and then click Close after the job is successfully created.
 A status flyout page is displayed, with a status of Analysis in progress and the new import job is
displayed in the list on the Import page.
 Click Refresh Refresh icon to update the status information that's displayed in the Status
column. When the analysis is complete and the data is ready to be imported, the status is
changed to Analysis completed.
 You can click the import job to display the status flyout page, which contains more detailed
information about the import job such as the status of each PST file listed in the mapping file.
 After you create the import job Office 365 analyzes the data in the PST files (in a safe and secure
manner) by identifying the age of the items and the different message types included in the PST
files. When the analysis is completed and the data is ready to import, you have the option to
import all the data contained in the PST files or you can trim the data that's imported by setting
filters that control what data gets imported.
 On the Import page in the Security & Compliance Center, click Ready to import to Office 365 for
the import job that you created in
 On the flyout page, click Import to Office 365.
 The Filter your data page is displayed. It contains the data insights resulting from the analysis
performed on the PST files by Office 365, including information about the age of the data. At this
point, you have the option to filter the data that will be imported or import all the data as is.
 Do one of the following:
 To trim the data that you import, click Yes, I want to filter it before importing.
 For detailed step-by-step instructions about filtering the data in the PST files and then starting
the import job, see Filter data when importing PST files to Office 365.
 Or
 To import all data in the PST files, click No, I want to import everything, and click Next.
 If you chose to import all the data, click Import data to start the import job.
 The status of the import job is display on the Import page. Click Refresh to update the status
information that's displayed in the Status column. Click the import job to display the status
flyout page, which displays status information about each PST file being imported.

You might also like