Fix 'Cannot Move the Items / Cannot Copy This Folder Because It May Contain Private Items' in Outlook & Exchange Online

When users working inside a Shared Mailbox or Delegated User Mailbox in Microsoft Outlook attempt to move, drag-and-drop, or delete a folder (or batch of emails), they frequently hit one of two closely related errors:

  1. "Cannot move the items. Cannot copy this folder because it may contain private items."
  2. "Cannot move the items. The item cannot be moved. It was either already moved or deleted, or access was denied."

Even when an administrator has granted FullAccess permission on the Shared Mailbox (Add-MailboxPermission -AccessRights FullAccess), Outlook still blocks moving entire folders if either:

  • The user lacks explicit CanViewPrivateItems / folder-level Owner permissions on the subfolder tree, OR
  • The source/destination mailbox has hit its RecoverableItemsQuota (100 GB dumpster limit) while under Litigation Hold or Microsoft Purview Retention Policy (because moving a folder across mailboxes or deleting it performs a soft-delete into Recoverable Items).

Root Cause & Remediation Flowchart

Outlook "Cannot Move the Items / Cannot Copy Folder" Diagnostic Flow
Outlook Error
"Cannot Move the Items"
Triggered when moving or deleting folders in a Shared / Delegated Mailbox
Cause 1: Private Items Flag
Missing CanViewPrivateItems
  • FullAccess does not always expose MAPI Private flags during folder moves
  • Grant CanViewPrivateItems via PowerShell
Cause 2: Dumpster Full
Recoverable Items Quota (100 GB)
  • Mailbox on Litigation / Retention Hold
  • Enable AutoExpandingArchive & run Start-ManagedFolderAssistant

Cause 1: Fix "Because It May Contain Private Items" Using Exchange Online PowerShell

In older versions of Outlook, solving this required opening the Shared Mailbox in a dedicated Outlook profile, going to File → Account Settings → Delegate Access, and checking "Delegate can see my private items":

Outlook Delegate Private Items Checkbox

In Exchange Online (Microsoft 365), you do not need to create a separate Outlook profile. You can grant the CanViewPrivateItems flag and Owner folder permissions directly via PowerShell using Add-MailboxFolderPermission / Set-MailboxFolderPermission!

Step-by-Step PowerShell Fix

POWERSHELL
Connect-ExchangeOnline -ShowBanner:$false

$SharedMailbox = "[email protected]"
$DelegateUser  = "[email protected]"

# 1. Grant Delegate + CanViewPrivateItems on the Calendar (sets the mailbox-level Freebusy/Private flag in Exchange Online)
Add-MailboxFolderPermission -Identity "$($SharedMailbox):\Calendar" `
    -User $DelegateUser `
    -AccessRights Editor `
    -SharingPermissionFlags Delegate, CanViewPrivateItems -ErrorAction SilentlyContinue

# If the user already has Calendar permissions, update them with Set-MailboxFolderPermission:
Set-MailboxFolderPermission -Identity "$($SharedMailbox):\Calendar" `
    -User $DelegateUser `
    -AccessRights Editor `
    -SharingPermissionFlags Delegate, CanViewPrivateItems

# 2. Ensure the user has Owner rights on the Root (Top of Information Store) and Inbox folders
foreach ($Folder in @("", ":\Inbox")) {
    $Target = "$SharedMailbox$Folder"
    Set-MailboxFolderPermission -Identity $Target -User $DelegateUser -AccessRights Owner -ErrorAction SilentlyContinue
}

Cause 2: Shared Mailbox Added via Automapping vs. Full Account in Outlook

When Add-MailboxPermission -AccessRights FullAccess is granted with AutoMapping:$true (the default), Outlook mounts the Shared Mailbox as a secondary store under the user's primary account. Cross-mailbox folder moves from an automapped store frequently fail MAPI private-property checks.

Fix: Disable Automapping & Add Shared Mailbox as a Secondary Account

POWERSHELL
# 1. Remove existing FullAccess permission
Remove-MailboxPermission -Identity "[email protected]" -User "[email protected]" -AccessRights FullAccess -Confirm:$false

# 2. Re-add FullAccess with AutoMapping disabled
Add-MailboxPermission -Identity "[email protected]" -User "[email protected]" -AccessRights FullAccess -AutoMapping:$false

Then in Outlook Desktop:

  1. Go to File → Account Settings → Account Settings → More Settings → Advanced (or click Add Account in newer Outlook builds).
  2. Add [email protected] as an explicit account (entering the delegate's own credentials when prompted).

Cause 3: RecoverableItems Folder Is Full (100 GB Quota Reached on Hold)

When a user moves an item or folder out of a mailbox—or deletes it—Exchange Online first copies the item into the Recoverable Items\Deletions (or SubstrateHolds) folder if the mailbox is subject to Litigation Hold, eDiscovery Hold, or a Microsoft Purview Retention Policy.

If RecoverableItems hits its 100 GB quota (RecoverableItemsQuota), Outlook throws "Cannot move the items" and refuses to delete or move anything.

Diagnostic & Remediation PowerShell Script

Run this script to check both Folder Permissions and RecoverableItems storage utilization on the affected mailbox:

POWERSHELL
function Test-ExoMailboxMoveItemsIssue {
    [CmdletBinding()]
    param (
        [Parameter(Mandatory = $true)]
        [string]$MailboxIdentity,

        [Parameter(Mandatory = $false)]
        [string]$DelegateUser
    )

    $Mbx = Get-EXOMailbox -Identity $MailboxIdentity -Properties `
        LitigationHoldEnabled, RetentionHoldEnabled, InPlaceHolds, RecoverableItemsQuota, RecoverableItemsWarningQuota, ArchiveStatus, AutoExpandingArchiveEnabled

    $Stats = Get-EXOMailboxStatistics -Identity $MailboxIdentity -Properties TotalDeletedItemSize

    Write-Host "`n=== 1. Mailbox Hold & Recoverable Items Quota Status ===" -ForegroundColor Cyan
    [PSCustomObject]@{
        Mailbox                      = $Mbx.UserPrincipalName
        LitigationHoldEnabled        = $Mbx.LitigationHoldEnabled
        InPlaceHoldsCount            = ($Mbx.InPlaceHolds | Measure-Object).Count
        TotalDeletedItemSize         = $Stats.TotalDeletedItemSize
        RecoverableItemsQuota        = $Mbx.RecoverableItemsQuota
        RecoverableItemsWarningQuota = $Mbx.RecoverableItemsWarningQuota
        ArchiveStatus                = $Mbx.ArchiveStatus
        AutoExpandingArchiveEnabled  = $Mbx.AutoExpandingArchiveEnabled
    } | Format-List

    if ($DelegateUser) {
        Write-Host "=== 2. Delegate Private Items & Folder Permissions ===" -ForegroundColor Cyan
        Get-MailboxFolderPermission -Identity "$($MailboxIdentity):\Calendar" -User $DelegateUser -ErrorAction SilentlyContinue |
            Select-Object FolderName, User, AccessRights, SharingPermissionFlags | Format-Table -AutoSize
    }
}

# Example Usage:
# Test-ExoMailboxMoveItemsIssue -MailboxIdentity "[email protected]" -DelegateUser "[email protected]"

If TotalDeletedItemSize is approaching 100 GB:

  1. Enable the Archive Mailbox (Enable-Mailbox -Identity $MailboxIdentity -Archive) and Auto-Expanding Archiving (Enable-Mailbox -Identity $MailboxIdentity -AutoExpandingArchive).
  2. Trigger the Managed Folder Assistant immediately to drain Recoverable Items into the Archive mailbox:
POWERSHELL
Start-ManagedFolderAssistant -Identity "[email protected]" -HoldCleanup