How to Import PST to Office 365 Online Archive (2026 Guide)

Legacy .pst files stored across local workstations and network shares present serious governance, security, and compliance risks. Administrators cannot perform centralized retention, audit logging, or legal eDiscovery on offline archives stored on individual endpoints.

Microsoft provides Online Archive (In-Place Archiving) within Exchange Online as a dedicated secondary cloud mailbox. Because the Online Archive exists alongside the user's primary mailbox without consuming primary mailbox storage limits, migrating legacy PST archives into Exchange Online centralizes data governance while preserving search capabilities for end users.

What is Microsoft 365 Online Archive & Why Use It?

An Exchange Online Online Archive operates as an independent storage container associated with a user's cloud account:

• Independent Quota: Standard Exchange Online Plan 1 archives offer 50 GB of storage; Plan 2 offers 100 GB (with auto-expanding archives scaling further where supported).
• Reduced Primary Mailbox Footprint: Offloading historical mail preserves performance in Classic Outlook and reduces the local cached .ost file footprint.
• Unified Governance: Purview retention policies, sensitivity labels, and eDiscovery searches scan both primary mailboxes and online archives simultaneously.
• Universal Accessibility: Users can search and read archived messages across Outlook for Windows, Mac, and Outlook on the Web (OWA) without downloading local database files.

Prerequisites: Enabling Online Archive Mailboxes

Before attempting any import workflow, ensure the destination account has an active Exchange Online license with archiving capabilities, and that the archive mailbox is provisioned.

An Exchange administrator can enable the archive via the Microsoft 365 admin center (Users > Active users > [User] > Mail > Manage email apps / Edit Exchange properties) or via Exchange Online PowerShell:

# Connect to Exchange Online PowerShell
Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com

# Enable the Online Archive for a specific user
Enable-Mailbox -Identity "john.doe@yourdomain.com" -Archive

# Verify that the archive is active
Get-Mailbox -Identity "john.doe@yourdomain.com" | Select-Object DisplayName, ArchiveStatus

If ArchiveStatus returns None, wait for Exchange Online provisioning to complete before initiating imports.

Method 1: Import PST to Online Archive via Classic Outlook Desktop

For individual mailboxes or small archives under 5 GB, Classic Outlook provides a direct client-side import method.

┌────────────────────────────────────────────────────────┐
│  CLASSIC OUTLOOK CLIENT ARCHIVE IMPORT                 │
├────────────────────────────────────────────────────────┤
│  1. Mount PST: File > Open & Export > Open Data File   │
│  2. Target Container: "Online Archive - User Name"     │
│  3. Import Wizard: Map items into matching subfolders  │
│  4. Background Sync: Outlook uploads data via MAPI/HTTP│
└────────────────────────────────────────────────────────┘

Step-by-Step Procedure

1. Open Microsoft Outlook (Classic) connected to the licensed Microsoft 365 profile.
2. Confirm that Online Archive - [User Name] appears in the folder navigation pane.
3. Click File > Open & Export > Import/Export.
4. Select Import from another program or file and click Next.
5. Select Outlook Data File (.pst) and click Next.
6. Click Browse, select your local .pst file, and specify duplicate-handling preferences.
7. Under Select the folder to import from, select the root folder and ensure Include subfolders is checked.
8. Choose Import items into the same folder in: and select Online Archive - [User Name] from the dropdown menu.
9. Click Finish. Outlook begins uploading messages to the Exchange Online archive.

Method 2: Enterprise Network Upload via Microsoft Purview & AzCopy

For tenant-wide migrations involving multiple users and substantial data volumes, Microsoft's official PST Import Service provides a centralized server-side ingestion path.

Step 1: Generate Azure Storage SAS URL

1. Sign in to the Microsoft Purview portal (purview.microsoft.com) or compliance portal (compliance.microsoft.com) as a Global Administrator or with the Mailbox Import Export role assigned.
2. Navigate to Data lifecycle management > Microsoft 365 > Import.
3. On the Import tab, click New import job.
4. Name the job, select Next, and choose Upload your data.
5. Click Show network upload SAS URL and copy the generated SAS token and endpoint URL.

Step 2: Upload PST Files via AzCopy

Download the official Microsoft AzCopy CLI utility and run the following command from the directory containing your PST files:

azcopy.exe copy "C:\PSTUploadFolder\*" "<SAS_URL>" --recursive=true

AzCopy streams the local files directly into the temporary Azure blob storage container.

Step 3: Create the PST Import Mapping CSV

Create a mapping file (e.g., PstImportMapping.csv) that correlates uploaded file names to destination mailboxes and marks the target container as the archive:

WorksheetName,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,ContentCodePage,SPFileContainer,SPManifestContainer,SPSiteUrl
PSTMapping,,user1.pst,john.doe@yourdomain.com,TRUE,/,1252,,,,
PSTMapping,,user2.pst,jane.smith@yourdomain.com,TRUE,/,1252,,,,

Step 4: Validate CSV and Start Ingestion

1. Return to the Purview Import wizard.
2. Check the boxes confirming you have uploaded files and prepared the mapping file, then click Next.
3. Upload your PstImportMapping.csv and click Validate.
4. After validation passes, save the job. Microsoft 365 queues the background import into the respective Online Archive containers.

Method 3: Archive Staging via Prism PST Converter Tool

When legacy PST archives have corrupted headers, non-standard folder structures, or unknown passwords, uploading them directly via AzCopy can trigger validation errors and halted import jobs.

Using Prism PST Converter Tool allows administrators to inspect and prepare legacy archives prior to cloud ingestion:

1. Launch Prism PST Converter Tool on your administrative workstation.
2. Click Add File or Add Folder to inspect candidate .pst files.
3. Review message integrity, folder hierarchies, and attachments in the built-in viewer.
4. Export clean, standardized PST archives or filter specific date ranges to fit tenant archiving policies.
5. Upload the sanitized PST files to Microsoft Purview via AzCopy without encountering malformed container errors.

Comparison Matrix: Ingestion Methods Compared

Frequently Asked Questions (FAQs)

What is the difference between a Primary Mailbox and an Online Archive Mailbox?

A primary mailbox stores active day-to-day correspondence. An Online Archive functions as a secondary cloud repository for older messages, helping keep primary mailbox OST cache files manageable while maintaining search visibility across all folders.

How long does it take for imported PST data to appear in the Online Archive?

When imported through Outlook Desktop, messages appear as soon as the client finishes uploading. With Purview Network Upload, Microsoft 365 processes files through the Mailbox Replication Service (MRS) in the cloud, which typically takes between 24 and 72 hours depending on tenant queue depth.

Can I import PST files into an Online Archive without Microsoft Outlook installed?

Yes. Both the Microsoft Purview Network Upload process and Prism PST Converter Tool operate independently without requiring a local installation of Microsoft Outlook.

Can I import a password-protected PST file into an Online Archive?

Microsoft's Purview Import Service cannot decrypt password-protected PST files; such files will fail ingestion. You must remove the password using Classic Outlook or process the file with Prism PST Converter Tool before uploading to the Azure staging container.

Summary

Importing historical PST archives into Microsoft 365 Online Archives centralizes corporate email governance and safeguards data against local endpoint failures. For single mailboxes under 5 GB, Classic Outlook's native import wizard provides a convenient desktop route. For multi-user departmental archives, the Microsoft Purview Network Upload service using AzCopy and CSV mapping ensures scalable ingestion. When dealing with damaged or legacy archives, staging data through Prism PST Converter Tool ensures smooth cloud migration.

Related Guides:

• How to Import PST to Office 365 Shared Mailbox
• How to Export Office 365 Mailboxes to PST via PowerShell