Start-ManagedFolderAssistant not available in Exchange Online PowerShell – how can admins confirm or trigger Online Archive processing?

Question

We are configuring Online Archive in Exchange Online using MRM retention policies with retention tags set to MoveToArchive.

According to Microsoft documentation, the Managed Folder Assistant (MFA) applies these policies and can be manually triggered using:

Start-ManagedFolderAssistant -Identity ******@domain.com

However, in our tenant:

• We are connected using the ExchangeOnlineManagement PowerShell module (v3.x, REST-based)
• Standard Exchange Online cmdlets (Get‑Mailbox, Set‑Mailbox, etc.) work correctly
• The cmdlet Start‑ManagedFolderAssistant is not available at all

is it possible to force a retention policy?

Answer 1

Two things. First, you need permissions to run Start-ManagedFolderAssistant, if it's not available for the user you are currently logged in, make sure he's a member of the Records management role group. Second, the Start-ManagedFolderAssistant cmdlet doesn't trigger anything, it only signals the backend service to process the mailbox when possible. But in Exchange Online, this is still working on a 7-day workcycle, so you might not see immediate effect after running the cmdlet. TL;DR - give it a try, but be prepared to wait a bit.

Answer 2

The Managed Folder Assistant (MFA) is still the component that processes MRM retention policies (including MoveToArchive tags), but in Exchange Online it runs automatically and processes each mailbox at least once every 7 days. This means Online Archive processing will occur without manual intervention, even if the Start-ManagedFolderAssistant cmdlet is not exposed in the current REST-based ExchangeOnlineManagement module.

What MFA does when it runs:

• Inspects items in the mailbox that have a retention policy applied.
• Determines whether items are subject to retention.
• Stamps items with the appropriate retention tags.
• Executes the configured retention action (for example, MoveToArchive) on items whose retention age is reached.

To confirm/force processing with the tools that are documented:

1. Ensure the mailbox has the correct retention policy assigned (using standard cmdlets such as Set-Mailbox).
2. Allow time for the Managed Folder Assistant to run (up to 7 days in Exchange Online).
3. Verify behavior by signing into the mailbox via Outlook or Outlook on the web and checking that items are moved to the archive according to the policy.

Where Start-ManagedFolderAssistant is available (for example, in environments or modules where it is still exposed), it can be used to manually trigger MFA for:

• A single mailbox:

    Start-ManagedFolderAssistant -Identity "<Mailbox Identity>"
  

• All user mailboxes:

    $Mailboxes = Get-Mailbox -ResultSize Unlimited -Filter {RecipientTypeDetails -eq "UserMailbox"}
    $Mailboxes.Identity | Start-ManagedFolderAssistant
  

If the cmdlet is not available in the current module/tenant, there is no alternative documented cmdlet to “force” MRM processing; administrators must rely on the built-in MFA schedule. In that case, confirmation is done by observing that items are eventually moved or deleted in line with the configured retention tags.

Note: MRM will not move items larger than the MaxSendSize/MaxReceiveSize configured on the mailbox, and disabled tags or ElcProcessingDisabled settings can prevent MFA from acting on items.

---

References:

• Retention tags and retention policies in Exchange Online
• Create a retention policy for Exchange Online
• Customize an archive and deletion policy for mailboxes in your organization
• Recoverable Items folder not emptied for mailbox on litigation or retention hold

AI-generated content may be incorrect. Read our transparency notes for more information.