New Outlook vs Classic Outlook Files on Network Shares: What to Use Instead

Many organizations store Outlook data files like PSTs and offline OST files on network shares to centralize user data and simplify backups. However, both the new Outlook for Windows and classic Outlook have strict rules about where these files can reside. Storing Outlook files on a network drive often leads to corruption, performance degradation, or outright failure to open the application. This article explains the technical limitations of each Outlook version regarding network shares and provides supported alternatives for shared mailbox access and data portability.

Why Outlook Refuses to Work with Files on Network Shares

Both new Outlook and classic Outlook enforce strict storage rules because their data files require low-latency, high-integrity read/write access. PST files use the Microsoft Personal Folders format, which relies on direct file locking and immediate write operations. Network shares, especially those using SMB protocol, introduce latency, packet loss, and potential file-locking conflicts when multiple users or processes access the same file. Classic Outlook will display a warning or simply fail to open a PST located on a mapped network drive, while new Outlook does not support PST files at all, making the question moot for that version.

OST files used with Cached Exchange Mode also cannot be placed on network shares. Outlook requires exclusive write access to the OST file, which network shares cannot guarantee reliably. Attempting to store an OST on a network path will cause sync errors, frequent crashes, and eventual corruption. The only officially supported locations are local drives formatted with NTFS. External drives formatted with NTFS are also supported, but only when the drive is directly connected via USB or eSATA, not over a network.

Technical Root Cause: File Locking and Latency

PST and OST files use a proprietary on-disk structure that relies on low-level file locking mechanisms. When a network share is involved, the SMB protocol translates these locks into network-level locks, which are slower and less reliable. If the network connection drops even briefly, Outlook may lose its lock and mark the file as corrupted. Microsoft has never supported PST or OST files on network shares for this reason, and the documentation explicitly warns against it.

New Outlook vs Classic Outlook: Network Share Behavior Compared

The new Outlook for Windows is a Universal Windows Platform app that connects exclusively to Exchange Online mailboxes through REST APIs. It does not create or use PST files at all. This eliminates the network share problem entirely, but it also means you cannot export data to a PST file or import data from one. All data stays in the cloud. Classic Outlook, on the other hand, still supports PST files for archiving and offline use, but those files must always be stored on a local NTFS drive. Neither version supports opening a PST or OST from a UNC path or a mapped network drive.

Supported Alternatives to Network Share Storage

If you need multiple users to access the same mailbox or data, network shares are the wrong approach. The following methods are fully supported and recommended by Microsoft.

Use Microsoft 365 Shared Mailboxes

1. Create a Shared Mailbox in Exchange Admin Center
   Go to Exchange Admin Center, select Recipients > Shared mailboxes, and create a new shared mailbox. Assign it a display name and email address.
2. Grant Access to Users
   In the shared mailbox properties, add users under Mailbox delegation. Assign Full Access and Send As permissions as needed.
3. Add the Shared Mailbox in Outlook
   In classic Outlook, go to File > Account Settings > Account Settings > double-click your Exchange account > More Settings > Advanced > Add the shared mailbox. In new Outlook, the shared mailbox appears automatically after you are granted access.
4. Configure Auto-Mapping
   By default, Exchange Online auto-maps shared mailboxes to Outlook. If auto-mapping is disabled, use the manual add method above.

Use Public Folders

Public folders are a legacy feature that still works in both Outlook versions, though new Outlook has limited support. Public folders replicate to each user’s mailbox and do not rely on network file shares. They are useful for shared calendars, contacts, and email archives. To set up public folders, use the Exchange Admin Center or Exchange Management Shell.

Export Data to a Local PST File

1. Open Classic Outlook
   This method works only in classic Outlook because new Outlook cannot export to PST.
2. Go to File > Open & Export > Import/Export
   Select Export to a file, then choose Outlook Data File (.pst).
3. Select the Folder to Export
   Choose the mailbox folder you want to export. Check Include subfolders if needed.
4. Save to a Local NTFS Drive
   Browse to a local folder such as C:\Users\YourName\Documents. Do not save to a network path. Click Finish.

Use Microsoft 365 Groups

Microsoft 365 Groups provide a shared mailbox, calendar, and document library without any PST files. Each group has its own Exchange mailbox and SharePoint document library. Users access group content directly from Outlook without needing local file storage. Create a group from the Outlook desktop app by selecting File > New > Microsoft 365 Group, or from the web at groups.microsoft.com.

Common Mistakes and Limitations

Attempting to Use a PST on a Network Drive in Classic Outlook

If you try to open a PST file from a network share, classic Outlook will display an error message stating that the file cannot be opened. The only workaround is to copy the PST file to a local NTFS drive and open it there. Do not use a sync tool like OneDrive to sync a PST file, because OneDrive does not support the file-locking mechanism required by Outlook.

New Outlook Cannot Import PST Files

If you switch from classic Outlook to new Outlook, you cannot import your archived PST files. Any data you need must be migrated to your Exchange Online mailbox before switching. Use classic Outlook to drag items from the PST into your Exchange mailbox, or use the Import/Export wizard to import the PST into the Exchange mailbox.

External Drives Are Not Network Shares

An external USB drive formatted with NTFS is considered a local drive and is supported for PST and OST storage. However, if the external drive is connected to a network router and accessed over Wi-Fi, it becomes a network share and is not supported. Always connect external drives directly to the computer.

New Outlook vs Classic Outlook: Network Storage Comparison

Item	New Outlook (UWP)	Classic Outlook (Win32)
PST file support	None	Supported, local NTFS only
OST file location	Not applicable	Local NTFS only
Network share PST/OST	Not applicable	Not supported
Shared mailbox support	Full via REST API	Full via MAPI/RPC
Data portability	No export to PST	Export/import PST

Both Outlook versions reject network share storage for PST and OST files. The only supported way to share mailbox access is through Microsoft 365 shared mailboxes, public folders, or Microsoft 365 Groups. For local archiving, classic Outlook can export to a PST file on a local NTFS drive, while new Outlook requires all data to remain in the cloud.

If you currently store PST files on a network share, move them to a local drive immediately to avoid corruption. For shared access, set up a shared mailbox in Exchange Online and grant permissions to the users. This approach eliminates the need for network file storage entirely and improves reliability.

An advanced tip: use Group Policy to redirect the default PST location to a local folder such as C:\OutlookData. This prevents users from accidentally saving PST files to network drives. The policy setting is located under User Configuration > Administrative Templates > Microsoft Outlook 2016 > Miscellaneous > PST Settings.