Script: Get-AZCopyGUI.ps1 – AZCopy GUI for PST Import

Microsoft recently announced the new Office 365 Import Service which is currently in preview. The new service allows organizations to import legacy PST data using one of two methods:

  • Drive shipping – you send Microsoft a hard drive with your data.
  • Network Upload – you make use of Azure storage to upload your data to Office 365.

The network upload option makes use of the Microsoft Azure AZCopy tool which uploads your data to an Azure storage blob. Brian Reid has a great post on his blog about using the service.

Get-AZCopyGUI.ps1 is a GUI wrapper for the Microsoft Azure AZCopy tool (AZCopy.exe) to simplify the process of importing .PSTs into Exchange Online. To use the script, you need to locate your storage account key and upload URL. You can do this by accessing the “Import” menu item in the Office 365 Admin Center. To access this option, you need to be assigned the Mailbox Import Export role in Exchange Online.


For more information on the Office 365 Import Service, see the following TechNet documentation.


  • The script will work natively in PowerShell 2.0+
  • The script requires the Microsoft Azure AZCopy Tool with default installation path – get it here

There are no parameters or switches, simply execute the script:


When using the Verbose option, a log file is named AzCopyVerbose.log will be created in %LocalAppData%\Microsoft\Azure\AzCopy if no “Log Location” is specified.

Execution Policy:
The script has been digitally signed and will run just fine under a “RemoteSigned” execution policy.



I have published it to the TechNet Gallery, it can be downloaded by clicking here…

Post navigation


  • Scott


    Thanks for a great tool. I am really not sure why Microsoft makes importing PST files difficult. I should be able to get a simple tool click and upload.

    Do you have something for the next step?
    Create the PST to user mapping file to upload


  • Chris

    Hi Scott,

    Thanks for the feedback. I don’t have any way of automating the user mapping file at the moment, perhaps this is something I might work on in future.



  • Rikin

    Hi Chris,

    I have been working on O365 migration as well PST ingestion projects, wanted to say thanks for the script, I am going to try this out and let you know


  • Chris

    Thanks Rikin, good luck with your migration!

  • Don

    out dated do you have the updated info

  • Chris

    Hi Don,

    Could you be a little more specific? Is the script not working for you?



  • vijay

    Hi Chris,

    I could get only SAS Url for PST Import, no storage key. GUI shows Destination url and storage keys. Can this be modified. Also script to create the mapping file which help me.

    Vijay SR

  • Chris

    Hi Vijay.

    Thanks for the feedback. It appears this has changed to use the new SAS Url format. I’ll work on updating the GUI to reflect that change – it may take a week or two but will post/tweet about it when it is done. As far as a mapping file generator is concerned, I have definitely thought about it, but it isn’t something I’m actively working on at the moment.



  • mandy

    Is their an updated script? supporting new SAS url format?

  • Chris

    Hi Mandy,

    I am currently working on an update for that script. It should be available soon.



Leave a Reply

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

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>