Step-by-Step Process to Upload PST Files to Office 365 (Network Upload)

-

Step-by-Step Process to Upload PST Files to Office 365 (Network Upload)


Uploading PST files to Office 365 (now Microsoft 365) is a common task, especially during migrations, data recovery, or restoring old emails. The Network Upload method allows IT administrators to upload PST files to Microsoft 365 mailboxes using Azure Storage. The data is then imported into users' mailboxes.

This guide will walk you through the Network Upload process step by step. It’s designed for IT professionals who are new to this task.

1. Prerequisites

Before you begin, make sure you have the following:

  • Microsoft 365 Admin Access: Ensure you have admin credentials to access the Microsoft 365 Admin Center and Exchange Admin Center (EAC).
  • Mailbox Import Export Role: You need to assign the Mailbox Import Export role to your admin account to perform the import operations.
  • AzCopy Tool: A command-line tool provided by Microsoft to upload PST files to Azure Storage.
  • PST Files: The PST files you wish to upload should be stored in a network location that is accessible for uploading.

2. Assign Mailbox Import Export Role

Before importing PST files, you need to assign the Mailbox Import Export role to your admin account.

Step 1: Access the Exchange Admin Center

  1. Go to Microsoft 365 Admin Center and sign in with your admin credentials.
  2. In the Admin Center, expand the Admin centers section and click on Exchange.

Step 2: Assign the Role

  1. In the Exchange Admin Center, click on Permissions in the left sidebar.
  2. Under Admin Roles, click on Organization Management.
  3. Select Edit (pencil icon).
  4. Under the Roles tab, click + Add and select the Mailbox Import Export role.
  5. Click Save to apply the role.

Note: It may take up to 1 hour for the role to take effect.

3. Download and Install AzCopy Tool

AzCopy is the command-line tool used for transferring PST files to Azure Storage. You need to download and install AzCopy on your system.

Step 1: Download AzCopy

Step 2: Install AzCopy

  • Follow the installation instructions for your operating system to complete the installation.
  • After installation, you can check that AzCopy is working by opening Command Prompt or PowerShell and typing:
azcopy

This will display the AzCopy help information if the tool is installed correctly.

4. Prepare the PST Files for Upload

Before uploading, ensure that your PST files are organized and ready for the upload process. They should be stored in a network-accessible location (e.g., on a shared drive or server) so you can easily upload them using AzCopy.

5. Upload PST Files to Azure Storage

You will upload PST files using the AzCopy tool to a temporary Azure Storage location created by Microsoft.

Step 1: Create a New Import Job

  1. Go to the Microsoft 365 Compliance Center.
  2. In the left pane, click on Information Governance > Import.
  3. Click on + New Import Job to create a new import job.
  4. Enter a name and description for the import job, then click Next.
  5. After creating the job, you'll be provided with a Secure Storage Key. This key is needed to upload the PST files to Azure Storage.

Step 2: Upload PST Files with AzCopy

  1. Open Command Prompt or PowerShell on your system where AzCopy is installed.
  2. Use the following AzCopy command to upload your PST files:
azcopy copy "C:\path\to\your\pst\files\*.pst" "https://<your_storage_account>.blob.core.windows.net/ingestiondata?<SAS_token>" --recursive
  • Replace C:\path\to\your\pst\files\*.pst with the local path to your PST files.
  • Replace <your_storage_account> with the name of your Azure storage account.
  • Replace <SAS_token> with the Secure Storage Key you received when creating the import job in the Compliance Center.
  1. Once the command is entered, AzCopy will begin uploading the PST files to Azure Storage. The --recursive flag will ensure all PST files in the specified directory are uploaded.

Note: Depending on your network speed and the size of the PST files, this process might take some time.

6. Prepare the Import Mapping File

An import mapping file is a CSV file that associates PST files with specific user mailboxes. This file is necessary to ensure the PST data is uploaded to the correct users.

Step 1: Create the CSV Mapping File

  1. Open Notepad or your preferred text editor.
  2. Create a CSV file with the following columns:
    • PSTFilePath: Full path to the PST file in Azure Storage.
    • Mailbox: The email address of the target user’s mailbox where the PST data should be imported.
    • TargetRootFolder (optional): The folder within the mailbox to import the data (e.g., "Inbox").

Example of a Mapping File:

PSTFilePath,Mailbox,TargetRootFolder
https://<your_storage_account>.blob.core.windows.net/ingestiondata/pstfile1.pst, user1@example.com, Inbox
https://<your_storage_account>.blob.core.windows.net/ingestiondata/pstfile2.pst, user2@example.com, Archive
  • Replace <your_storage_account> with your Azure storage account name.
  • Ensure the PSTFilePath matches the location of the PST file in Azure Storage.

Step 2: Save the File

Save the CSV file and make sure it is accessible for the import process.

7. Create the Import Job in Microsoft 365

Now that the PST files are uploaded to Azure Storage and the mapping file is ready, you need to create the import job and link the mapping file.

Step 1: Create the Import Job in the Compliance Center

  1. In the Microsoft 365 Compliance Center, go to Information governance > Import.
  2. Click + New import job.
  3. Enter a name and description for the import job and click Next.
  4. Under Select the PST files to import, click Upload PST files from the network.
  5. Upload the previously created CSV mapping file that links the PST files to the user mailboxes.
  6. Review your settings and click Create Import Job.

Step 2: Monitor the Import Job

  • After the import job is created, you can track the status of the import in the Import section of the Compliance Center.
  • The import job will process the PST files and import the data into the corresponding user mailboxes.

8. Post-Import Actions

After the import is complete:

  • Verify Data: Check the target mailboxes in Outlook or Microsoft 365 to ensure that the data from the PST file has been successfully imported.
  • Manage Imported Data: You may need to apply retention policies or organize the imported data into folders.

Conclusion

Uploading PST files to Office 365 (Microsoft 365) using the Network Upload method is a straightforward process that involves preparing your PST files, uploading them to Azure Storage, and mapping them to user mailboxes. By following the above steps, IT professionals can migrate or restore email data into users' Office 365 mailboxes. Always ensure that you have the necessary roles assigned and that the import job is properly configured for a smooth process.

Comments

Post a Comment

Thank You for Sharing your feedback, We hope article was helpful in some way to you.

Popular posts from this blog

Everything You Need to Know About Online Archive in Office 365

-
Image
Everything You Need to Know About Online Archive in Office 365 Office 365 (O365), now referred to as Microsoft 365 , is a cloud-based suite that offers a range of applications designed to boost productivity and collaboration. One key feature of Microsoft 365 is the Online Archive , a service designed to help users manage large email mailboxes by offloading older items to a secondary storage. This blog post will dive into what Online Archive in Office 365 is, how it works, the different licensing requirements, and why it's an essential feature for users managing vast amounts of emails. What is Online Archive in Office 365? 🔍 What is Online Archive in Office 365? (Detailed Step-by-Step Explanation) Microsoft 365 Online Archive, also known as In-Place Archive, is a mailbox feature in Microsoft Exchange Online (part of Office 365) that provides users with an additional mailbox storage space when their primary mailbox gets full. This is especially useful for organizations with stri...
Read more

How to Add a Custom Domain in Office 365 and Set Up Users with Business Standard License

-
Image
How to Add a Custom Domain in Office 365 and Set Up Users with Business Standard License Introduction Microsoft 365 (formerly Office 365) allows businesses to use their own domain for email and collaboration services. In this guide, we will walk through adding a custom domain in Office 365, creating users, assigning licenses, logging into webmail, and configuring Outlook for desktop and laptop. Step 1: Adding a Custom Domain in Office 365 Sign in to Microsoft 365 Admin Center Go to Microsoft 365 Admin Center Log in with your administrator credentials. Add Your Domain Navigate to Settings > Domains Click Add Domain and enter your custom domain (e.g., yourcompany.com). Verify Domain Ownership Microsoft will provide TXT, MX, and CNAME records. Add these records to your domain registrar's DNS settings. Click Verify after adding the records. Update DNS Records Configure MX records for email and CNAME records for Autodiscover. Save changes and wait for pr...
Read more

Migrating from an on-premise system to Office 365 over view

-
Image
Migrating from an on-premise system to Office 365 requires careful planning and execution to ensure minimal disruption and to maximize the benefits of the cloud environment. Below is a step-by-step guide to help your team through the migration process: Step 1: Assessment and Planning Understand the Current Environment Assess the existing on-premise system. Identify which services are in use (email, file storage, collaboration tools, etc.). Analyze the size of the data, number of users, and system configurations. Define Migration Goals Set clear objectives for migration. Are you moving all services to Office 365, or just specific ones (e.g., Exchange Online, SharePoint Online)? Determine the timeline for migration. Evaluate Office 365 Licensing Needs Determine which Office 365 plans (e.g., Business Basic, Business Standard, Enterprise E3, E5) meet the organization’s needs. Ensure the appropriate licenses are purchased for all users. Create a Migration Strategy ...
Read more