PST may cause a headache for the users outside the Exchange Server environment. From the eDiscovery point of view, PST files are not considered as the secure option for data security. When it comes to data migration, it is common to find that users have accumulated the large amount of data in gigabytes or possibly, terabytes. Hence, it is required to transport the emails from the mail server and store in the PST file format. For these problems, Microsoft offers a tool named as PST Capture Tool.
Microsoft allows the users to import PST to shared mailboxes in Office 365 with the help of Import Service.
But, there are some prerequisites before the transfer process starts:
Learn Method to Move Outlook email to Office 365 Easily Quick Easy Method!
This feature is built on the Azure storage established by Microsoft. It is used to store the PST file before importing them into the mailboxes.
For the PST file to be imported first, storage account will be generated. It will take a few minutes and there are chances that a user wishes to give it two attempts before it is created. For that, it is required to click on the option “Show network upload SAS URL.” This URL will comprise of the following things:
Let’s Take an Instance:
- Storage Account Name: dd092cec1d084ab8b190526
- Container Name: ingestiondata
- Shared Access Signature: ?sv=2012-02-12&se=2017-02-05T13%3A33%3A07Z&sr=c&si=IngestionSasForAzCopy201611212055520769&sig=aeBq
The shared access signature consist of the following parts:
Once a user has done the storage provisioned, the upload procedure can be started.
To import pst to shared mailbox Office 365 PowerShell is an alternative for the tool. Suppose, AzCopy can be used. It is the command line tool to import PST to shared mailbox Office 365 PowerShell. Azure Storage Explorer, it is the graphical tool. They both are good at one’s place and any of them can be used.
Note: It is needed to use AzCopy version 5.2 or higher. Otherwise, a user will get some 404 errors:
“Failed to validate destination: One or more errors occurred. The remote server returned an error: (404) Not Found. The specified resource does not exist.”
#AZURE STORAGE EXPLORER
And now, the software can also be used to upload the PST file.
Note: A user can also identify the list of files located on Azure with its PowerShell line (require Azure.Storage module): “New-AzureStorageContext -SasToken ($SharedAccessSignatureURL -split ‘\?’ | Select-Object -Last 1) -StorageAccountName ($SharedAccessSignatureURL -split ‘\.’ -split ‘//’) | Get-AzureStorageBlob -Container ($SharedAccessSignatureURL -split ‘\?’ -split ‘/’) | Select-Object -ExpandProperty Name”
Once the PST file is uploaded to the Azure storage, it is needed to build a CSV file that will map Outlook PST files to destination folder and mailboxes. For instance,
It is really needed to maintain the structure of PST file, the case is kind of delicate for the “TRUE” or “FALSE”, and for the name of Outlook PST file.
It is the final step, it is needed to import PST mapping file and execute the import option so import pst to shared mailbox Office 365 Powershell would going to complete.
Click on “finish” and the process is complete. The import process will continue on the Microsoft side. A user can also examine the progress with the help of details of the batch job.
When the feature was released initially, it was of great importance. Additional functionalities are expected to be added in future. Other than that, this option is great for the PST files accumulated after the migration process. Also, the drive shipping option is considered helpful when the organizations have the PST file in terabytes. The size of the mailbox allotted to the user is 50GB and there is unlimited file archived in Office 365, it is not possible to store all the data on the server. That is when the need to import PST to shared mailbox Office 365 PowerShell emerges.