Exchange Server 2016–2019 to Microsoft 365
Public Folder Migration — Complete Administrator Runbook
TECHNICAL BULLETIN | TB-EXO-PF-2016-001 | Rev. 1.0 | November 16, 2026
Applies to: Exchange Server 2016–2019 modern public folders → Exchange Online public folders. Intended audience: Exchange administrators, Microsoft 365 administrators, and migration engineers.
SCOPE / STOP RULE This procedure is for modern public folders hosted in Exchange Server 2016 or 2019 public-folder mailboxes. If the source is actually Exchange 2010 legacy public-folder databases, or if a migration batch already exists, do not initialize a new migration; follow the matching Microsoft procedure or triage the existing batch first.
At a glance
| Phase |
Required outcome |
Principal system |
| 1. Discover and protect |
Confirm topology, backups, mail flow, scripts, RBAC, and migration window |
On-prem + Exchange Online |
| 2. Validate the source |
Clean migration-blocking folder, permissions, size, and mail-object inconsistencies |
On-prem Exchange 2016–2019 |
| 3. Provision the target |
Generate size/map CSV and create held-for-migration cloud PF mailboxes |
Both |
| 4. Synchronize and copy |
Sync mail-enabled PF directory objects; create and monitor single batch |
Both |
| 5. Cut over |
Lock on-prem public folders, perform final sync, release and route mail |
Both |
| 6. Prove completion |
Check folders, permissions, content, mail flow, Outlook, and post-cutover logs |
Both |
Non-negotiable safeguards
- Complete ordinary user-mailbox migration before public-folder cutover; confirm Outlook access is supported for intended users.
- Use one public-folder migration batch only. A completed batch cannot synchronize additional source changes.
- Back up databases and capture source hierarchy, message counts/sizes, permissions, and SMTP addresses before modification.
- Never delete existing Exchange Online public folders or cloud public-folder mailboxes without confirming they contain no independent production data.
- Allow a minimum 48-hour public-folder outage window for the final synchronization, as recommended by Microsoft.
- Preserve on-prem public-folder mailboxes for several weeks after successful migration; rollback can lose new cloud content.
Primary authority: Microsoft Learn, “Use batch migration to migrate Exchange Server public folders to Exchange Online” [R1]. The native tool uses up to 100 target public-folder mailboxes, 100 GB per mailbox, with a 5 TB recommended migration ceiling when planning at ~50% fill. Exchange 2016 reached end of support October 14, 2025 [R2].
1 If a migration is already failing: triage before retry
Run these READ-ONLY commands first in Exchange Online PowerShell. Save all output to a dated support folder. “Synced,” “SyncedWithErrors,” “Failed,” “Completing,” and “Completed” require different remedies.
Get-MigrationBatch | Where-Object { $_.MigrationType -like "*PublicFolder*" } |
Format-Table Identity,Status,MigrationType -Auto
Get-MigrationBatch -Identity "PublicFolderMigration" -IncludeReport |
Format-List Identity,Status,State,TotalCount,SyncedCount,FailedCount,Report
Get-MigrationUser -BatchId "PublicFolderMigration" |
Get-MigrationUserStatistics | Format-Table Identity,Status,Error -Auto
Get-PublicFolderMailboxMigrationRequest |
Get-PublicFolderMailboxMigrationRequestStatistics |
Format-Table TargetMailbox,Status,PercentComplete -Auto
If the batch name differs, substitute its actual identity. For a failed request, capture detailed reports before changing anything:
Get-PublicFolderMailboxMigrationRequest |
Get-PublicFolderMailboxMigrationRequestStatistics -IncludeReport |
Format-List Identity,TargetMailbox,Status,FailureType,Message,Report
DO NOT RESET ON FIRST FAILURE Do not rerun New-Mailbox, remove target mailboxes, delete cloud public folders, or create a second batch while investigating a current migration. Diagnose the exact error using Section 15 and Microsoft’s troubleshooting links [R10–R17].
2 Inventory and readiness decisions
2.1 Record the environment
| Item to record |
Example / administrative note |
| On-premises Exchange version/CU/SU |
Exchange Server 2016, server name(s), all installed updates |
| Source topology |
Modern PF mailboxes? Primary hierarchy mailbox GUID? Multiple AD domains? |
| Exchange Online tenant |
Tenant admin UPN, default routing domain (*.mail.onmicrosoft.com) |
| Migration topology |
Exchange hybrid configured? User mailboxes already moved? |
| Reachability |
Published EWS/MRSProxy hostname; public certificate; HTTPS/TCP 443 |
| Source folder footprint |
Folder count, size, largest folder, item count, recoverable items |
| Mail-enabled PFs |
SMTP aliases, primary SMTP, inbound connectors, Send As/Send on Behalf |
| Directory sync |
Microsoft Entra Connect in use? “Exchange Mail Public Folders” option? |
| Change controls |
Backup confirmed, rollback owner, outage approval, pilot users |
2.2 Minimum compatibility requirements
- Microsoft documents Exchange 2016 CU4 or later as the minimum source version for this batch migration, and recommends its latest applicable CU/SU before migration. Confirm AD preparation was performed for the installed CU; otherwise migration-specific Set-OrganizationConfig parameters may be missing [R1].
- Exchange Online administrator must hold the Organization Management role group; on-premises operator needs Organization Management or Server Management permissions [R1].
- MRS Proxy must be enabled on at least one Exchange server that hosts a source public-folder mailbox [R1, R5].
- One source folder over 25 GB directly (excluding children) should be reduced or divided, based on Microsoft’s migration guidance [R1].
- Use a maximum of 100 target PF mailboxes for native migration. Target mailbox quota is at most 100 GB, but plan around 50 GB per target to allow growth [R1].
- Exchange 2016 has passed its official support end date; prioritize security and validated migration rather than relying on ongoing vendor support [R2].
2.3 Verify modern public folders and Exchange versions (ON-PREM EMS)
Get-ExchangeServer | Select-Object Name,AdminDisplayVersion
Get-OrganizationConfig | Format-List PublicFoldersEnabled,
RootPublicFolderMailbox,PublicFolderMailboxesMigrationComplete,
PublicFolderMailboxesLockedForNewConnections
Get-Mailbox -PublicFolder | Format-Table Name,Database,ServerName -Auto
Get-PublicFolder -Recurse -ResultSize Unlimited | Measure-Object
Get-MailPublicFolder -ResultSize Unlimited |
Select-Object Name,PrimarySmtpAddress,Identity
If Get-Mailbox -PublicFolder returns none, do not assume this is a modern-folder source. Determine whether you have Exchange 2010-style legacy public-folder databases and use Microsoft’s legacy migration workflow instead [R1].
3 Prepare workspaces, tools, and connection
3.1 Separate the two shell contexts
- ON-PREM EMS = Exchange Management Shell launched on a source Exchange 2016 server with appropriate Exchange permissions.
- EXO PS = Windows PowerShell / PowerShell with ExchangeOnlineManagement module, connected to the target tenant; several commands must never be run against the wrong organization.
3.2 Create a protected change folder
New-Item -ItemType Directory -Path "C:\PFScripts" -Force
New-Item -ItemType Directory -Path "C:\PFMigration" -Force
New-Item -ItemType Directory -Path "C:\PFMigration\Evidence" -Force
Download the most recent Microsoft CSS-Exchange scripts [R3]. Store the migration scripts together in C:\PFScripts and review downloaded script provenance and execution requirements. Required scripts: SourceSideValidations.ps1; Sync-ModernMailPublicFolders.ps1; Export-ModernPublicFolderStatistics.ps1; ModernPublicFolderToMailboxMapGenerator.ps1; and SetMailPublicFolderExternalAddress.ps1.
Use current Microsoft instructions for module installation [R4]. EXO PS example:
Install-Module ExchangeOnlineManagement -Scope CurrentUser
Import-Module ExchangeOnlineManagement
Connect-ExchangeOnline -UserPrincipalName "<TENANT_ADMIN_UPN>"
Get-OrganizationConfig | Format-List Name,PublicFoldersEnabled,
RemotePublicFolderMailboxes
Run Exchange Management Shell on the on-premises server for source commands. Verify the current shell before every change. If organizational PowerShell policy blocks signed scripts, follow the organization’s approved script-execution policy; do not permanently weaken execution policy to make the migration work.
3.3 Confirm MRS Proxy (ON-PREM EMS)
Get-WebServicesVirtualDirectory |
Format-Table Identity,InternalUrl,ExternalUrl,MRSProxyEnabled -Auto
If MRSProxyEnabled is False on the appropriate published EWS virtual directory, enable it on the intended source host, then verify:
Set-WebServicesVirtualDirectory -Identity "<SERVER>\EWS (Default Web Site)" `
-MRSProxyEnabled $true
Get-WebServicesVirtualDirectory |
Format-Table Identity,MRSProxyEnabled -Auto
Verify that the chosen externally reachable hostname resolves publicly, its certificate is trusted, and the Exchange Online migration service can reach the published HTTPS/EWS endpoint. Review any reverse proxy, WAF, authentication policy, and hybrid configuration if an endpoint connection fails [R5].
4 Protect and snapshot the source (ON-PREM EMS)
Confirm current backups and restorability using the organization’s Exchange database backup product. Export baseline evidence into the protected evidence folder. Repeat snapshots immediately before final lock/cutover so incremental writes can be reconciled.
Set-Location "C:\PFMigration\Evidence"
Get-PublicFolder -Recurse -ResultSize Unlimited |
Export-Clixml ".\OnPrem_PFStructure.xml"
Get-PublicFolderStatistics -ResultSize Unlimited |
Export-Clixml ".\OnPrem_PFStatistics.xml"
Get-PublicFolder -Recurse -ResultSize Unlimited |
Get-PublicFolderClientPermission |
Select-Object Identity,User,AccessRights |
Export-Clixml ".\OnPrem_PFPerms.xml"
Get-MailPublicFolder -ResultSize Unlimited |
Export-Clixml ".\OnPrem_MEPF.xml"
Also record root-level and EFORMS REGISTRY permissions separately: these do not transfer automatically. Record Send As/Send on Behalf grants for mail-enabled public folders [R1].
Get-PublicFolderClientPermission -Identity "\"
Get-PublicFolderClientPermission -Identity "\NON_IPM_SUBTREE\EFORMS REGISTRY"
Get-MailPublicFolder | Get-ADPermission |
Where-Object { $_.ExtendedRights -like "*Send-As*" }
Get-MailPublicFolder | Where-Object { $_.GrantSendOnBehalfTo } |
Format-Table Name,GrantSendOnBehalfTo -Auto
RETENTION AND COMPLIANCE Review Get-OrganizationConfig | Format-List DefaultPublicFolderAgeLimit and any per-folder AgeLimit before migration. Do not change retention, delete old content, or purge recoverable items without records-management approval [R1].
5 Validate the source before building a batch
5.1 Run Microsoft’s source-side validation (ON-PREM EMS)
Set-Location "C:\PFScripts"
.\SourceSideValidations.ps1
Review the generated ValidationResults.csv in its output directory. It detects invalid permissions, broken dumpster mapping, oversized or deeply nested folders, large hierarchy counts, special characters, missing statistics, and orphaned/inconsistent mail-enabled objects [R6].
5.2 Classify each issue before changing data
| Validation result |
Administrator action |
| BadPermission |
Identify stale SIDs/users; back up permissions, then use validator-guided repair only after review. |
| MailEnabledWithNoADObject / OrphanedMPF |
Inspect PF and Active Directory recipient mapping; determine intended mail-enable state before removing or recreating objects. |
| SpecialCharacters |
Rename source folders using / or \ in names to supported paths, preserving a crosswalk of old→new names. |
| TotalItemSize > 25 GB |
Reduce or partition the individual folder; consider unsupported-fit risk before proceeding. |
| ChildCount > 10,000 / FolderPathDepth |
Redesign violating folder branches; 10,000 direct children and hierarchy-depth limitations apply. |
| BadDumpsterMapping / large DUMPSTER_ROOT |
Investigate before re-running a batch; certain dumpster conditions can block migration. |
| EmptyFolder |
Informational; do not bulk-delete simply because it is empty. |
5.3 Additional non-destructive spot checks
Get-PublicFolder -Recurse -ResultSize Unlimited |
Where-Object { $_.Name -like "*\*" -or $_.Name -like "*/*" } |
Format-Table Name,Identity,EntryId -Auto
(Get-PublicFolder -GetChildren "\NON_IPM_SUBTREE\DUMPSTER_ROOT").Count
Get-OrganizationConfig | Format-List DefaultPublicFolderAgeLimit
After approved remediation, rerun SourceSideValidations.ps1, retain the before/after CSVs, and require resolution of migration-blocking failures. Do not assume a validator’s example commands are appropriate without considering your data and directory identity [R6].
6 Confirm directory sync and email routing preconditions
6.1 Microsoft Entra Connect
If Microsoft Entra Connect is installed, review its optional feature “Exchange Mail Public Folders.” Microsoft’s migration runbook directs the administrator to deselect that feature for this workflow; that prevents synchronized on-prem MEPF objects from conflicting with cloud-created ones. Because doing so deletes those synced representations from Entra ID, evaluate impact and any 500-deletion safeguard before applying it [R1]. Do not toggle the setting on an unreviewed hybrid deployment.
6.2 Accepted relay domain for migrated mail-enabled folders (ON-PREM EMS)
Identify the tenant’s actual routing domain, usually company.mail.onmicrosoft.com, and verify that Hybrid Configuration Wizard send routing is established. Microsoft requires an accepted-domain object with the exact special name below to support post-cutover relay [R1]. Check first:
$targetRoutingDomain = "<TENANT>.mail.onmicrosoft.com"
Get-AcceptedDomain | Where-Object {
$_.DomainName -eq $targetRoutingDomain
} | Format-Table Name,DomainName,DomainType -Auto
If absent, create it as InternalRelay. If the domain exists with a different name, Microsoft directs renaming that existing accepted-domain object while preserving its other attributes; review other uses and the change impact first.
New-AcceptedDomain `
-Name "PublicFolderDestination_78c0b207_5ad2_4fee_8cb9_f373175b3f99" `
-DomainName $targetRoutingDomain -DomainType InternalRelay
Do not run New-AcceptedDomain if the domain already exists; use the exact official Microsoft rename procedure after verification [R1]. Check Directory-Based Edge Blocking (DBEB) requirements for inbound mail to mail-enabled folders [R18].
7 Inspect the Exchange Online destination (EXO PS)
Get-MigrationBatch | Where-Object { $_.MigrationType -like "*PublicFolder*" }
Get-Mailbox -PublicFolder | Format-Table Name,ExchangeGuid -Auto
Get-Mailbox -PublicFolder -SoftDeletedMailbox |
Format-Table Name,ExchangeGuid -Auto
Get-PublicFolder -Recurse -ResultSize Unlimited
Get-OrganizationConfig | Format-List PublicFoldersEnabled,
RemotePublicFolderMailboxes
A clean first migration normally needs no pre-existing Exchange Online public-folder hierarchy or public-folder mailbox. If objects exist, determine who created them, whether they hold production content, whether there is an earlier incomplete attempt, and whether soft-deleted/CNF object names collide. Do not execute Microsoft’s destructive cleanup sequence until data ownership and approved recovery are documented [R1, R14].
NO BLIND CLEANUP Microsoft documentation contains delete/purge commands for abandoned target public folders and soft-deleted PF mailboxes. These irreversibly remove tenant content; they are intentionally not included as a copy-and-run block here. Use [R1] and [R14] only after identifying precisely which objects are safe to delete.
8 Export source statistics and generate target mapping (ON-PREM EMS)
Run the two Microsoft scripts from C:\PFScripts, writing data files to the protected migration directory [R1, R3].
Set-Location "C:\PFScripts"
.\Export-ModernPublicFolderStatistics.ps1 "C:\PFMigration\stats.csv"
.\ModernPublicFolderToMailboxMapGenerator.ps1 `
-MailboxSize 50GB -MailboxRecoverableItemSize 1GB `
-ImportFile "C:\PFMigration\stats.csv" `
-ExportFile "C:\PFMigration\map.csv"
The mapping CSV describes where major branches/large folders should go; it does NOT necessarily list every folder. The script normally gives generic target names (Mailbox1, Mailbox2, etc.). For easier support, change TargetMailbox to unique names such as PF-EXO-001, preserving the root mapping and all child mapping relationships.
$mapping = Import-Csv "C:\PFMigration\map.csv"
$mapping | Format-Table -Auto
$mapping | Group-Object TargetMailbox |
Select-Object Name,Count | Format-Table -Auto
$mapping | Where-Object { $_.FolderPath -eq "\" }
Gate checks: exactly one mapping row for root “\”; no empty TargetMailbox values; no duplicate or misspelled target names; not more than 100 unique targets; enough space for source data including recoverable content and growth. In the unusual case of exactly 100 unique targets, check Microsoft’s mapping-file final-entry edge case [R15].
9 Create Exchange Online PF mailboxes (EXO PS)
Copy map.csv to a location accessible from the EXO PowerShell workstation. Do not re-run mailbox creation if a previous attempt already created the target mailboxes. The root-map target must be created first and marked HoldForMigration [R1].
$mapPath = "C:\PFMigration\map.csv"
$mapping = Import-Csv $mapPath
$rootRows = @($mapping | Where-Object { $_.FolderPath -eq "\" })
if ($rootRows.Count -ne 1) { throw "Expected exactly one root mapping." }
$primary = $rootRows[0].TargetMailbox
if ([string]::IsNullOrWhiteSpace($primary)) { throw "Root mailbox missing." }
New-Mailbox -HoldForMigration:$true -PublicFolder `
-IsExcludedFromServingHierarchy:$false $primary
$secondary = $mapping | Where-Object { $_.TargetMailbox -ne $primary } |
Select-Object -ExpandProperty TargetMailbox -Unique
$secondary | ForEach-Object {
New-Mailbox -PublicFolder -IsExcludedFromServingHierarchy:$false $_
}
Get-Mailbox -PublicFolder |
Format-Table Name,IsExcludedFromServingHierarchy -Auto
Wait for cloud directory replication before attempting New-MigrationEndpoint if a newly created PF mailbox cannot yet be resolved. Microsoft documents an approximately one-hour delay for this transient GUID lookup error [R16].
10 Sync mail-enabled PF directory objects (ON-PREM EMS)
The content migration does not by itself solve mail-enabled public-folder recipient synchronization. Use Microsoft’s current modern authentication script from the on-premises Exchange Management Shell, with ExchangeOnlineManagement available [R3, R7].
Set-Location "C:\PFScripts"
.\Sync-ModernMailPublicFolders.ps1 `
-CsvSummaryFile "C:\PFMigration\mepf-sync-initial.csv"
Review the CSV for each create/update/delete action and failure. The script prompts for cloud sign-in. Optional -WhatIf previews create/update/delete operations, but do NOT combine -WhatIf with -FixInconsistencies for a read-only run. Do not use -Force to bypass an empty-source warning without understanding the potential to remove cloud MEPF objects [R7].
MEPF FAILURE EXAMPLES Duplicate X500/proxy addresses and an existing cloud recipient with the same directory name are common reasons for mail-object sync failure. Investigate the named object and collision using [R11]; never remove a recipient solely to make the script complete.
11 Create and start the single migration batch (EXO PS)
11.1 Record primary source hierarchy mailbox GUID (ON-PREM EMS)
(Get-OrganizationConfig).RootPublicFolderMailbox.HierarchyMailboxGuid.Guid
This GUID must be collected ON PREMISES. Do not use the Exchange Online RootPublicFolderMailbox GUID; Microsoft states that using the cloud GUID causes a migration failure [R1].
11.2 Create the endpoint and batch (EXO PS)
Use real on-premises credentials, an Internet-reachable MRS Proxy hostname (not a localhost/private IP), the identical final map.csv used to provision the target, and a monitored notification address.
$sourceCredential = Get-Credential "<DOMAIN>\<PF_ADMIN>"
$sourceRemoteServer = "<PUBLIC_MRS_PROXY_FQDN>"
$sourcePfGuid = [guid]"<PASTE_ON_PREM_ROOT_PF_GUID>"
$mapBytes = [System.IO.File]::ReadAllBytes("C:\PFMigration\map.csv")
$endpoint = New-MigrationEndpoint -PublicFolder `
-Name "PublicFolderEndpoint" -RemoteServer $sourceRemoteServer `
-Credentials $sourceCredential
New-MigrationBatch -Name "PublicFolderMigration" `
-CSVData $mapBytes -SourceEndpoint $endpoint.Identity `
-SourcePfPrimaryMailboxGuid $sourcePfGuid `
-NotificationEmails "<ADMIN_EMAIL>"
If an endpoint named PublicFolderEndpoint already exists, inspect and validate it instead of blindly creating another. If creation fails, preserve the exact error and see the troubleshooting matrix. Do not use ad-hoc workarounds to bypass TLS or certificate trust [R1, R16].
11.3 Begin initial content sync (EXO PS)
Start-MigrationBatch "PublicFolderMigration"
Get-MigrationBatch -Identity "PublicFolderMigration" |
Format-List Identity,Status,TotalCount,SyncedCount,FailedCount
Wait for the batch to reach Synced with individual jobs free of Failed/Quarantined status. During the initial copy the source is still accessible; Microsoft states incremental sync runs approximately once every 24 hours [R1].
12 Monitor progress and approve the cutover gate (EXO PS)
Get-MigrationBatch -Identity "PublicFolderMigration" -IncludeReport |
Format-List Identity,Status,TotalCount,SyncedCount,FailedCount,
LastSyncedDate,Report
Get-MigrationUser -BatchId "PublicFolderMigration" |
Get-MigrationUserStatistics |
Format-Table Identity,Status,Error -Auto
Get-PublicFolderMailboxMigrationRequest |
Get-PublicFolderMailboxMigrationRequestStatistics |
Format-Table TargetMailbox,Status,PercentComplete,
LastSuccessfulSyncTimestamp -Auto
Microsoft advises that the batch LastSyncedDate and individual LastSuccessfulSyncTimestamp values be within seven days before cutover. Investigate failed or quarantined jobs, not just the overall percentage [R1].
Go / no-go checklist
- ☐ Batch and individual requests are synced; no unexplained errors or quarantines.
- ☐ SourceSideValidations results are clean of migration-blocking defects.
- ☐ All required user mailboxes are already in Exchange Online; pilot Outlook setup is ready.
- ☐ Updated snapshots of source data and permissions have been saved and reviewed.
- ☐ Mail-enabled PF sync script completed, its output was reviewed, and SMTP routing design was tested.
- ☐ Business owner approved public-folder outage and minimum 48-hour maintenance allowance.
- ☐ Rollback decision maker, downtime communications, and on-prem backup are ready.
13 Final cutover: LOCK → COMPLETE → TEST → RELEASE
MAINTENANCE OUTAGE BEGINS HERE Public folders must be inaccessible on-premises during final synchronization. Users and automated systems should stop writing to source folders. Mail sent to mail-enabled folders can queue until cutover completes [R1].
13.1 Perform a final pre-lock MEPF sync (ON-PREM EMS)
Set-Location "C:\PFScripts"
.\Sync-ModernMailPublicFolders.ps1 `
-CsvSummaryFile "C:\PFMigration\mepf-sync-precutover.csv"
13.2 Lock source PF mailboxes (ON-PREM EMS)
Set-OrganizationConfig `
-PublicFolderMailboxesLockedForNewConnections $true
Get-OrganizationConfig |
Format-List PublicFolderMailboxesLockedForNewConnections
Wait for AD replication and all source PF hosts to honor the lock. Microsoft documents that attempting Get-PublicFolder \ after the lock returns a “Couldn’t find the public folder mailbox” error [R1]. Do not proceed while new client writes are still entering the source.
13.3 Confirm no concurrent on-prem move operations (ON-PREM EMS)
Get-MoveRequest | Format-Table Identity,Status -Auto
Get-PublicFolderMoveRequest | Format-Table Identity,Status -Auto
Investigate unfinished or stale completed move requests. Microsoft instructs removal of such requests before finalizing; do so only after verifying their ownership and that they are no longer needed [R1].
13.4 Complete the batch (EXO PS)
Complete-MigrationBatch "PublicFolderMigration"
Get-MigrationBatch -Identity "PublicFolderMigration" |
Format-List Identity,Status,CompleteAfter,LastSyncedDate
The final sync can remain Synced for hours and potentially longer than 24 hours for larger migrations. Continue inspecting underlying requests. A Completed batch is one-way: no additional source content can be synchronized into this migration batch [R1].
13.5 Pilot test and unlock the cloud (EXO PS)
Get-Mailbox -PublicFolder | Format-Table Name,ExchangeGuid -Auto
Set-Mailbox -Identity "<PILOT_USER_UPN>" `
-DefaultPublicFolderMailbox "<CLOUD_PF_MAILBOX_NAME>"
In supported Outlook, verify complete hierarchy, sample message content/attachments, read/write permissions, ability to create/delete test folders if authorized, and mail-enabled public-folder functionality. Pilot visibility can take 15–30 minutes and Outlook may require restart [R1].
When pilot checks pass, switch the Exchange Online organization to local cloud public folders:
Set-OrganizationConfig -RemotePublicFolderMailboxes $null `
-PublicFoldersEnabled Local
Get-OrganizationConfig |
Format-List PublicFoldersEnabled,RemotePublicFolderMailboxes
13.6 Finalize mail routing and source state (ON-PREM EMS)
For mail-enabled PF environments, preserve messages queued for PF.InTransit before routing changes. Microsoft’s source documentation includes a transport-queue message export routine; use it only after preparing C:\ExportFolder and testing operator permissions and the impact of suspend/export/resume on the production transport queue [R1].
Get-TransportService | ForEach-Object {
Get-Message -Server $_.Name -ResultSize Unlimited |
Where-Object { $_.Recipients -like "*PF.InTransit*" } |
Select-Object Identity,InternetMessageId,Recipients
}
Run the Microsoft script that sets the on-premises MEPF ExternalEmailAddress to the cloud counterpart, then mark the source migration complete:
Set-Location "C:\PFScripts"
.\SetMailPublicFolderExternalAddress.ps1 `
-ExecutionSummaryFile "C:\PFMigration\mepf-routing-summary.csv"
Set-OrganizationConfig `
-PublicFolderMailboxesMigrationComplete:$true `
-PublicFoldersEnabled Remote
Confirm mail flow from internal and external senders to several mail-enabled PF SMTP addresses. If NDR 5.7.13 or 5.4.1 is observed, inspect anonymous CreateItems rights on the destination folder and Directory-Based Edge Blocking (DBEB) configuration [R1, R18]. Do not make a global DBEB change without reviewing recipient security implications.
14 Post-migration verification and acceptance
14.1 Export like-for-like cloud evidence (EXO PS)
Set-Location "C:\PFMigration\Evidence"
Get-PublicFolder -Recurse -ResultSize Unlimited |
Export-Clixml ".\Cloud_PFStructure.xml"
Get-PublicFolder -Recurse -ResultSize Unlimited |
Get-PublicFolderStatistics |
Export-Clixml ".\Cloud_PFStatistics.xml"
Get-PublicFolder -Recurse -ResultSize Unlimited |
Get-PublicFolderClientPermission |
Select-Object Identity,User,AccessRights |
Export-Clixml ".\Cloud_PFPerms.xml"
Get-MailPublicFolder -ResultSize Unlimited |
Export-Clixml ".\Cloud_MEPF.xml"
Compare source and target by normalized folder path, representative item counts and sizes, users’ effective rights, SMTP addresses, and functional mail delivery. Object GUIDs and some quota/statistical fields can differ between environments. Document every meaningful exception before customer signoff.
14.2 Known permission gaps (EXO PS)
Microsoft specifically identifies these gaps: root “\” and EFORMS REGISTRY permissions do not migrate automatically, and Send As / Send on Behalf permissions on mail-enabled public folders are not carried over. Recreate each entitlement from the recorded source ACL after verifying it is still appropriate [R1].
# Example ONLY: substitute validated identity and rights.
Add-PublicFolderClientPermission -Identity "\" `
-User "<USER_UPN>" -AccessRights "<RIGHTS>"
Add-RecipientPermission -Identity "<PF_SMTP_ADDRESS>" `
-Trustee "<USER_UPN>" -AccessRights SendAs
Set-MailPublicFolder -Identity "<PF_NAME>" `
-GrantSendOnBehalfTo "<USER_UPN>"
14.3 Acceptance test matrix
| Test |
Expected result / evidence |
| Hierarchy and structure |
Root and child folders match approved source inventory; no unexpected missing branches. |
| Messages and attachments |
Old and recent sample posts present; sizes/counts reconciled within explained variance. |
| Access control |
Pilot with Owner, Editor, Reviewer, and no-access identities has expected rights. |
| Mail-enabled addresses |
Primary/alias SMTP values correct, no unwanted duplicate recipient objects. |
| Inbound and internal mail |
Send test to PF; item appears; no 5.x NDR; trace/routing recorded. |
| Outbound/delegation |
Send As and Send on Behalf tests pass where configured. |
| Client compatibility |
Classic Outlook workflow tested; new Outlook has only partial public-folder support [R19]. |
| Operations |
Batch Completed; migration errors reviewed; logs/backup secured. |
15 Troubleshooting decision table
| Observed symptom |
Most likely seam / corrective action |
Reference |
| Batch already Failed or SyncedWithErrors |
Get detailed batch and PF request reports; fix specific reported error. Do not recreate whole tenant. |
R1, R9 |
| Endpoint connection/auth failure |
Verify MRSProxyEnabled, public EWS host/cert, HTTPS reachability, source credential/RBAC. |
R5 |
| Recipient mailbox GUID not found after PF mailbox creation |
Exchange Online directory replication delay; Microsoft says wait ~1 hour and retry endpoint. |
R16 |
| Migration batch cannot match source PF mailbox |
Root PF hierarchy GUID was taken from EXO rather than on-prem; recheck actual source GUID. |
R1 |
| MEPF sync: object already exists |
Name collision with cloud recipient; identify conflicting object and use supported renaming/repair. |
R11 |
| MEPF sync: duplicate X500/proxy |
Find conflicting recipient; repair duplicate address/object mapping after preserving needed recipients. |
R11 |
| Stuck at 95% / “could not be mail-enabled” |
Orphaned MailEnabled attribute without matching AD MEPF; run ValidateMailEnabledPublicFolders before remediation. |
R10 |
| “A subscription wasn’t found for this user” |
Missing/corrupt individual migration request; stop batch, wait for Stopped, then restart. |
R12 |
| “No active public folder mailboxes were found” during completion |
In multiple AD domains, associated AD user may be in different domain from PF mailbox/server; see Microsoft KB. |
R13 |
| More than 100 target PF mailbox error |
Count unique TargetMailbox names; special 100-row final-entry mapping issue documented. |
R15 |
| Duplicate “Mailbox1” or multiple matches |
Inspect active + soft-deleted PF mailbox names and CNF conflict objects; cleanup only exact confirmed targets. |
R14 |
| Stalled jobs / transient errors |
Check all requests; Microsoft suggests lowering endpoint concurrency e.g. 30/20 after evaluation. |
R1 |
| Quarantined: key not present in dictionary |
Likely corrupt source item; follow Microsoft stop/move affected folder to primary PF mailbox/restart sequence. |
R1 |
| Dumpster of the Dumpster folder |
Microsoft suggests stopping and restarting batch; inspect report first. |
R1 |
| DUMPSTER_ROOT > 10,000 immediate children |
Documented size/structure limit; investigate with Microsoft before unsupported repair. |
R1, R6 |
| Folders missing to Outlook user |
Check EXO PublicFoldersEnabled, pilot DefaultPublicFolderMailbox, hierarchy-serving mailboxes, permissions, client limitations. |
R1, R19 |
| External mail 5.7.13 or 5.4.1 |
Review anonymous CreateItems entitlement and DBEB rules for PF routing domain. |
R1, R18 |
15.1 Recommended troubleshooting evidence bundle
- Exact message and stage of failure (command, timestamp and which PowerShell context).
- Get-MigrationBatch -IncludeReport, per-request statistics -IncludeReport, and migration user statistics.
- SourceSideValidations ValidationResults.csv and before/after fixes.
- Original stats.csv, final map.csv, cloud PF mailbox list, source hierarchy mailbox GUID.
- Sync-ModernMailPublicFolders summary CSV and SetMailPublicFolderExternalAddress summary CSV.
- Redacted on-prem Get-OrganizationConfig and EXO Get-OrganizationConfig public folder states.
- MRS Proxy virtual-directory settings and network/certificate verification.
- Original and cloud XML snapshots, sample affected folder paths, NDR headers, accepted-domain records.
Exclude passwords, authentication tokens, customer mailbox content, and other sensitive data before handing diagnostic evidence to an external party.
16 Rollback, stabilization, and decommissioning
16.1 Backout criteria
Back out only with an approved incident owner and after weighing impact. Microsoft explicitly warns that rollback to on-premises public folders loses cloud content or inbound folder mail added after the migration, unless it is separately exported and preserved [R8]. Use the official rollback runbook for exact cleanup and rerouting actions.
For a pre-cloud-write rollback, the on-prem unlock/reset command documented by Microsoft is:
Set-OrganizationConfig `
-PublicFolderMailboxesLockedForNewConnections:$false `
-PublicFolderMailboxesMigrationComplete:$false `
-PublicFoldersEnabled Local
This command alone is NOT the complete rollback. The operator must also restore any ExternalEmailAddress modifications, coordinate mail delivery and tenant PF direction, and handle cloud public-folder data. See [R8] for the full Microsoft procedure. Cloud mailbox/folder deletion commands are excluded here to prevent irreversible unintended loss.
16.2 Stabilization
- For the first few business days, monitor migration exception reports, mail delivery, message queues, Outlook access, permissions, and user-reported missing folders.
- Preserve migration scripts, mapping CSV, validated baselines, admin change log, and email transport backup in restricted storage.
- Retain on-prem public-folder mailbox data for several weeks after confirmed success, consistent with Microsoft’s warning, before approving final removal.
- Plan the Exchange 2016 retirement/security remediation separately; moving public folders is not equivalent to decommissioning the Exchange organization or hybrid identity infrastructure.
17 Administrator execution checklist
| Phase |
Required signoff / artifact |
| PREP |
☐ Modern PF topology ☐ CU/AD ready ☐ Role memberships ☐ MRS Proxy ☐ source backup |
| CLEAN |
☐ SourceSideValidations passed ☐ mail objects reconciled ☐ size/limits reviewed |
| BASELINE |
☐ Source hierarchy/stats/permissions/MEPF XML saved ☐ routing aliases recorded |
| TARGET |
☐ Clean target confirmed ☐ stats.csv ☐ map.csv reviewed ☐ cloud PF mailboxes created |
| SYNC |
☐ MEPF sync reviewed ☐ source GUID verified ☐ one endpoint + one batch created |
| GO/NO GO |
☐ Batch Synced ☐ requests clean ☐ last successful sync recent ☐ outage approved |
| CUTOVER |
☐ Source locked ☐ final sync Completed ☐ pilot passed ☐ EXO enabled Local |
| MAIL |
☐ MEPF routing stamped ☐ on-prem Remote state ☐ internal/external messages verified |
| VERIFY |
☐ Cloud snapshots reconciled ☐ root/EFORMS ACLs restored ☐ delegates restored |
| CLOSE |
☐ Exceptions accepted ☐ support evidence archived ☐ post-migration observation period assigned |
18 Official Microsoft references and script downloads
All hyperlinks below point to Microsoft Learn, Microsoft Support, or Microsoft’s CSS-Exchange script documentation. Use the current versions when executing; Microsoft may update the procedure after publication of this bulletin.
[R1] Primary migration runbook — Exchange Server modern public folders to Exchange Online
[R2] Exchange Server 2016/2019 end-of-support roadmap
[R3] Microsoft CSS-Exchange public-folder migration scripts and downloads
[R4] Connect to Exchange Online PowerShell
[R5] Enable MRS Proxy endpoint on Exchange Server
[R6] SourceSideValidations — syntax, results, repairs
[R7] Sync-ModernMailPublicFolders — commands, parameters, precautions
[R8] Rollback of public-folder migration to Exchange Online
[R9] Get-PublicFolderMailboxMigrationRequestStatistics command
[R10] Migration stuck at 95% / orphaned mail-enabled PF state
[R11] MEPF synchronization duplicate/name/address conflicts
[R12] A subscription was not found for this user
[R13] No active public folder mailboxes during Complete-MigrationBatch
[R14] Duplicate PF mailbox name / soft-deleted and CNF errors
[R15] More than 100 target mailbox mapping error
[R16] Cannot find recipient mailbox GUID when creating endpoint
[R17] Microsoft 365 public-folder overview and functionality
[R18] Directory-Based Edge Blocking (DBEB)
[R19] New Outlook for Windows: feature limitations including public folders
[R20] Configure Exchange Server public folders for hybrid access
[R21] SetMailPublicFolderExternalAddress script documentation
[R22] Microsoft 365 public folder migration troubleshooting wizard (tenant login)
Publication note: Technical instructions are intended for authorized administrators using a documented change request. Validate the environment and Microsoft’s latest published instructions before execution. Do not apply destructive cleanup actions without an approved backup and data ownership review.