A Microsoft application for managing email, calendars, contacts, and tasks across devices and platforms.
As it turns out, thanks to a helpful blog post from Tim McMichael on TechNet, there’s an easy solution. Look up the GUID of the user’s primary mailbox and then use this as the identity for the Managed Folder Assistant.
- get-mailboxLocation –user user@example.com | fl mailboxGuid,mailboxLocationType
If you have archiving enabled, then this returns two GUIDs, one for the Primary and one for the MainArchive mailboxes.
Grab the GUID for the Primary mailbox, and use it like so:
- Start-ManagedFolderAssistant aace1f4e-feed-ace0-babe-466f1deed1d1
When utilizing the GUID we can minimize the change that any initialization process does not cause the command to fail.
See for more information https://learn.microsoft.com/en-gb/archive/blogs/timmcmic/office-365-start-managedfolderassistant-in-office-365
Note: Using GUID will easily run the command but the issue does not resolve. The email movement will not start unless the user logs in to OWA once.
Please note that if a mailbox is too full, archiving may still not start. In that case, you must bring the size of the primary mailbox below 85% capacity, according to Microsoft, or below 95%, according to my actual experience. Then triggering Start-ManagedFolderAssistant actually gets it going.