Office 365 Import Service – Import PST into Office 365 user mailbox | Part 2#2 No ratings yet. 10 min read

The current article is the continuation of the former article in which we review the steps that are involved in the process of using the Office 365 option – Office 365 Import Service.

Office 365 Import Service | The article series

The article series include the following articles:

Step 5/09 – Download and install the: Microsoft Azure AZCopy Tool.

The PST import process is implemented by using a command base utility named – Microsoft Azure AZCopy Tool

We will need to download and install the Microsoft Azure AZCopy Tool

The download link to the Microsoft Azure AZCopy Tool appears in the top part of the window of the Import files to Office 365upload file over a network.

Click on the Download tool link and install the tool.

Download and install the Microsoft Azure AZCopy Tool -01

Note – The Microsoft Azure AZCopy Tool will be installed in the following path -C:\Program Files (x86)\Microsoft SDKs\Azure\

In the following screenshot, we can see that the Microsoft Azure AZCopy Tool appears in the start menu under – Microsoft Azure.

Download and install the Microsoft Azure AZCopy Tool -02

Step 6/09 – Create the required command syntax for the Microsoft Azure AZCopy Tool.

In this phase, we will “build” the required command syntax that will be used by the Microsoft Azure AZCopy Tool for “uploading” the PST file\s into the Office 365 storage.

At first look, the syntax of the command seems a little bit scary!

The best practice is to copy the command example to a text editor such as notepad and, edit the required parameters that will be suite to our scenario.

An example of the required command syntax appears in the article – Office 365 Import Service

AzCopy.exe /Source:\\SERVER01\PSTshare1
/Dest:https://d1717df0c99e4157xyz520a.blob.core.windows.net/ingestiondata/SERVER01/PSTshareR1
/Destkey:bVqiKup0j7Bxik39vSN/zV3UveKHWs
vmYb+NsvyoJs2Dhb8kOYIqmE2IPuC7uA7h3dTKJ1EmA0fWF3lPtBYtqA== /S /V: C:\PSTUpload\Uploadlog.log

In the following section, we will demonstrate the way to “build” the complete command based on my specific environment.

In my environment I use the following parameter:

  • The server name is –SRV1
  • The shared folder name is – PSTshare1

We will need to update the existing command example, using four parameters:

1. The Source parameter

We will need to add the UNC path of the folder that we shared in the previous step (Step 1/09 – Create a network share for storing the PST files).

In our scenario, the UNC path is:

AzCopy.exe /Source:\\SRV1\PSTshare1

2. The DST (destination parameter)

We will need to use a “combination” of the value that we got from the former step (Step 4/09 – Copy the value of the SECURE KEY and the SECURE URL and save it) of the SECURE URL + add the path to the folder that stores the PST file.

Pay attention that now we will not use the UNC naming convention, but instead, add the shared folder path using the “URL address” naming convention.

In our specific scenario, the value of the SECURE URL is – https://d1717df0c99e4157xyz522b.blob.core.windows.net/ingestiondata

The value of the shared folder is – /SRV1/PSTshare1

The combination of these two values is:

/Dest:https://d1717df0D99e4156xyz522b.blob.core.windows.net/ingestiondata/SRV1/PSTshareR1

3. The Destkey value

The value of the key is the value that we save in the preceding step (Step 4/09 – Copy the value of the SECURE KEY and the SECURE URL and save it).

In our specific scenario, the value of the SECURE KEY is-

bVqiKup0j7Bxik39vSN/zV3UveKHWsvmYb+NsvyoJs2Dhb8kOYIqmE2IPuC7uA7h3dTKJ1EmA0fWF3lPtBYtzB==

The parameter that will include the secure key is – Destkey

/Destkey:bVqiKup0j7Bxik39vSN/zV3UveKHWsvmYb+NsvyoJs2Dhb8kOYIqmE2IPuC7uA7h3dTKJ1EmA0fWF3lPtBYtzB==

4. The log files path

The last parameter is the folder which will be used to contain the log file of the PST migration process.

In our specific scenario, we will save the log file in the Temp folder in C: drive and name the log file – Uploadlog.log.

/S /V:C:\TEMP\Uploadlog.log

The final result

This is an example of the complete command syntax. In the following screenshot, we can see a presentation for each of the different parameters that we will need to update.

Create the required command syntax for the Microsoft Azure AZCopy Tool -00-A

Step 7/09 – Start the import process by using the Microsoft Azure AZCopy Tool.

In this phase, we will use the Microsoft Azure AZCopy Tool for “uploading” the PST file\s into the Office 365 storage, using the command syntax that we have prepared in the former step.

Technically, we can copy the command from the notepad and paste it into PowerShell console of the Microsoft Azure AZCopy Tool.

From my experience, we can experience a problem because – the command is very long and when we paste the command into the PowerShell console, the execution of the command can fail because of “issues” such as – spaces in the command syntax, etc.

In case that you experience problems when using the copy and paste option, we can bypass this issue by executing the command by using a batch file.

To use a batch file, we will need to save the information in the notepad and save the file using a *.BAT file extension.

To activate the batch file, we will call the batch file from the Microsoft Azure AZCopy Tool PowerShell console.

In the following example, we run the command by using Batch file.

In our scenario, I have saved the text file as PST01.BAT in C:\TEMP folder.

Create the required command syntax for the Microsoft Azure AZCopy Tool -002

Running the required import command in Microsoft Azure AZCopy Tool PowerShell console

Access the Microsoft Azure AZCopy Tool PowerShell console by using the start menu and access the Microsoft Azure folder.

Download and install the Microsoft Azure AZCopy Tool -02
The following PowerShell console appears.

Create the required command syntax for the Microsoft Azure AZCopy Tool -003
To execute the batch file, we will type the batch file name.

In our example, we will call the batch file that stored in the C:\TEMP folder.

Create the required command syntax for the Microsoft Azure AZCopy Tool -004
In the following screenshot, we can see the results:

The command completes successfully.

1 file (PST file) was “transfer” to the Office 365 store (the PST file that as exported from Outlook in phase – Step 2/10 – Export outlook data to PST file).

Create the required command syntax for the Microsoft Azure AZCopy Tool -005
The information about the PST import process saved in a log file. In the following screenshot, we can see we can see the information that saved in the Log file.

Create the required command syntax for the Microsoft Azure AZCopy Tool -006

Step 8/09 – Prepare the required CSV file (PST user mapping file).

Until now, we have to finish to “send” the PST file\s to the Office 365 storage.

In the next phase, we will need to use the Office 365 portal to complete the process by accessing a particular PST file that was saved in the Office 365 store and then, import the PST file\s into the Office 365 user mailbox.

To be able to “inform” the Office 365 portal about which of the PST files will import to the Office 365 user mailbox, we will need to use a CSV file.

In the following part, we will demonstrate a simple scenario in which we configure the CSV file to map a particular PST file to s specific user mailbox.

Note – there is an option to implement a more complicated scenario in which we import a couple of PST files into a particular Office 365 user, mailbox or a scene in which we import the bulk of PST file into different Office 365 user mailboxes.

The CSV file structure includes the following parameters:

  • Workload – Office 365 service into which data will be imported. For email, use “Exchange”.
  • FilePath – the path of the folder that stores the PST file\s. In our scenario, the path is SRV1/PSTshare1
  • Name – the PST file name. In our scenario, the file name is –pst10.pst
  • Mailbox – the Exchange Online “destination mailbox”. In our scenario, the destination mailbox name is – admin@o365info.com
  • IsArchive – Whether or not to place the PST in the Online Archive:
    • If you want the PST to get imported into the primary mailbox, you can specify IsArchive as FALSE.
    • If you want the PST to get imported into the online archive, you can specify IsArchive as TRUE. This is the default value.
  • TargetRootFolder – this is the name of the folder that will be created in the user mailbox that will

In the following screenshot, we can see an example of the content of the CSV file.

In our scenario, we use the following parameters:

  • The file path is: srv1/PSTshare1
  • Name – the name of the PST file is – pst10.pst
  • Mailbox – the PST file will be imported into the admin mailbox
  • Target root folder – the folder name that will be created and serve as a container for the PST file is – pst10

Prepare the required CSV file (PST user mapping file -01

Note – you can download an example of the CSV file from the following link – CSV file
Note – regarding the naming convention of the different parameters such as PST file name or the Target root folder, there is no specific instruction regarding the naming convention, but my recommendation is to “make it simple”. Don’t use the name with space, try to avoid the complicated name or non-standard characters and so on.
Note – the CSV file will be saved on the local desktop
Phase 03#03

The compilation of the importing PST task will be implemented by using the Office 365 admin portal.

Step 9/09 – Start the import PST process (Import job).

Login to the Office 365 portal and click on the Admin option

Copy the value of the SECURE KEY and the SECURE URL -01

On the left, menu bar looks for the IMPORT menu.

Click on the plus icon and choose the option – Upload data over the network.

Start the import PST process -Import job -01

Choose the option boxes:

  • II’m done uploading my files
  • I have access to the mapping file

Start the import PST process -Import job -02

We will need to name the PST import job. In our specific scenario, we will name it as – admin-10

Start the import PST process -Import job -03

To add the CSV file, click on the plus sign and select the CSV file that was created in the former step (Step 8/09 – Prepare the required CSV file (PST user mapping file)).

In our specific scenario, the CSV file name is 01.csv

Check the option box – by checking this box you agree to the terms and the condition of the service

Start the import PST process -Import job -04
In the following screenshot, we can see the last screen which informs us that the “task job” is running.

Start the import PST process -Import job -05

In the following screenshot, we can see that the import job is running (import in progress).

Start the import PST process -Import job -06

When the import job complete, we can use the View detail’s option to get additional information about the job. For example, verify if the job completes successfully or a scenario in which the job didn’t complete successfully (complete with errors).

Start the import PST process -Import job -07

In the following screenshot, we can see the results: a new folder was created in the user mailbox named – pst10, which includes the content of the PST file.

Start the import PST process -Import job -08

 

Now it’s Your Turn!
It is important for us to know your opinion on this article

Print Friendly

Related Post

Please rate this

Eyal Doron on EmailEyal Doron on FacebookEyal Doron on GoogleEyal Doron on LinkedinEyal Doron on PinterestEyal Doron on RssEyal Doron on TwitterEyal Doron on WordpressEyal Doron on Youtube
Eyal Doron
Share your knowledge.
It’s a way to achieve immortality.
Dalai Lama

7 Responses to “Office 365 Import Service – Import PST into Office 365 user mailbox | Part 2#2”

  1. Hi there.
    I have some problems with azcopy script running.
    In my secure network upload SAS key I have “&” symbols, and when I run this script have problem

    my SASkey with some severeal editions:
    ?sv=2012-02-12&se=9149-12-31T23%3A59%3B59Z&sr=c&si=IngestionSasForAzCopy201604092146162011&sig=wkf7AEkBXFeQTd%2F8i5PUjhZxDJtAN3FGqiRMzjVm3Wk%3D

    Errors:
    [2016/01/01 02:20:47][ERROR] The syntax of the command is incorrect. The supplied storage key (DestKey) is not a valid Base64 string.
    ‘se’ is not recognized as an internal or external command,
    operable program or batch file.
    ‘sr’ is not recognized as an internal or external command,
    operable program or batch file.
    ‘si’ is not recognized as an internal or external command,
    operable program or batch file.
    ‘sig’ is not recognized as an internal or external command,
    operable program or batch file.

  2. and … I will change parametr Dest to DestSAS and I have new error:

    [ERROR] The syntax of the command is incorrect. Invalid SAS token in parameter “DestSAS”. Value of “se” is invalid in SAS token.

  3. Hi.
    I would like knowHi, first at all thank you for this great article.
    I’m working on Hybrid environment and I need move users to Office 365.
    What happen with the cross permissions in this type of scenario?
    I need import all the users that are sharing permissions between them?
    For example: if I have a user A on premise and User B on premise, and A has FullAccess permissions on B mailbox.
    Do I will need import both users in the same batch equal than a typical Hybrid migration?
    Also, do I have any size restriction for the pst file?
    Thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *