Email Migration

Fix Exchange Online Public Folder PST Import Quota Errors

Steve KSteve K Nov 14, 2026 868 views

Question details

Resolve quota errors that interrupt a PST import into Exchange Online public folders.

Fix Exchange Online Public Folder PST Import Quota Errors
Product
Microsoft Exchange Online public folders
Device & OS
not provided
Scenario
A large PST is being imported into public folders in an organization with multiple public folder mailboxes.
Observed behavior
The import fails when the destination folder or its public folder mailbox reaches a quota, even though other public folder mailboxes exist.
Before you start

Identify the destination public folder, its hosting mailbox, and the exact quota error from the import logs. Connect to Exchange Online PowerShell with an account authorized to view and change the relevant settings.

Solution 1Recommended

Check and adjust public folder quotas

Use this approach when a public folder quota is blocking the import and a supported increase is appropriate.

A warning quota signals approaching capacity; a prohibit-post quota can block new content. Organization defaults, individual folder quotas, and public folder mailbox capacity are separate checks.

1
Connect to Exchange Online

In Exchange Online PowerShell, run Connect-ExchangeOnline and sign in with an authorized administrator account.

2
Inspect organization defaults

Run Get-OrganizationConfig | Format-List DefaultPublicFolderIssueWarningQuota,DefaultPublicFolderProhibitPostQuota to view the default warning and posting quotas.

3
Check the affected folder and mailbox

Run Get-PublicFolder -Identity "\FolderPath" | Format-List Name,*Quota*,ContentMailbox, replacing the path with the affected folder. Run Get-Mailbox -PublicFolder and Get-MailboxStatistics -Identity "MailboxName" to inspect the hosting mailbox and its size.

4
Adjust applicable defaults

If the organization defaults are the limiting quotas, use Set-OrganizationConfig with -DefaultPublicFolderIssueWarningQuota and -DefaultPublicFolderProhibitPostQuota. Choose supported values appropriate for the tenant, with the warning quota below the posting quota; verify current Microsoft service limits before applying them.

5
Resume the import

Allow time for the settings to apply, then use your import tool to resume or restart the job. Check its logs and existing imported content before restarting to avoid unintended duplicates.

Check which quota applies: Changing organization defaults may not resolve an explicit folder quota or a full public folder mailbox. Increasing a quota also cannot exceed Exchange Online service limits.
Free Microsoft Office alternative

Work with Office files in WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easy to transition your document work. It does not manage Exchange Online public folders or fix PST import quotas.

Open and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for everyday document, spreadsheet, and presentation workAccess a free, lightweight alternative for Office file workflowsKeep document editing separate from Exchange public folder migration administration
QA img-9

Frequently Asked Questions

Why did the import fail when other public folder mailboxes have space?

The destination folder is hosted in a particular public folder mailbox. Other mailboxes having space does not automatically remove a quota or capacity limit affecting that destination.

Does a warning quota stop a PST import?

A warning quota alerts administrators that usage is approaching a limit. A prohibit-post quota or a full hosting mailbox can prevent additional content from being added.

How can I see which mailbox hosts a public folder?

In Exchange Online PowerShell, run Get-PublicFolder -Identity "\FolderPath" | Format-List Name,ContentMailbox, replacing the path with the affected folder.

Will creating another public folder mailbox move my existing folder?

No. Creating a mailbox or a new folder in it does not move existing folders or their content. Use a supported move procedure if you need to relocate an existing folder.

Why didn't public folder auto-splitting prevent the error?

Auto-splitting may take time and may not respond quickly enough to the sudden growth caused by a large PST import. Check the destination mailbox capacity and plan where to place remaining new folders.