Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The Exchange Managed Folder Assistant (MFA) is the mailbox process that turns Messaging Records Management (MRM) policy into action. It evaluates retention tags, calculates each item’s retention age, and then archives or deletes content when the applicable rule is satisfied. In current Exchange Server releases it is a throttled, continuously running assistant—not a guaranteed once-a-day batch job—although the default work-cycle target is one day. You can request immediate processing with Start-ManagedFolderAssistant, but eligibility, holds, tag precedence, and workload still determine what actually changes.
How the pieces fit together
MRM has four layers:
Retention tag → Retention policy → Mailbox assignment → Managed Folder Assistant → Action- Retention tags define an action and an age, such as “move to archive after 180 days.”
- Retention policies collect tags.
- Mailbox assignment gives a mailbox one retention policy.
- The MFA visits the mailbox, stamps or evaluates tags, and enforces eligible actions.
MRM is an Exchange mailbox-lifecycle feature. It is not the same as Microsoft Purview records management, litigation hold, eDiscovery, or backup. Microsoft recommends Purview retention policies and labels for broader Microsoft 365 governance; MRM remains important for Exchange-specific archive and mailbox-item behavior.
The three kinds of retention tag
| Tag | What it covers | Important limit |
|---|---|---|
| Default policy tag (DPT) | Otherwise untagged content across the mailbox; can archive or delete. | A policy can have one archive DPT and one deletion DPT (plus a supported voicemail-deletion DPT). |
| Retention policy tag (RPT) | A supported default folder such as Inbox, Sent Items, or Deleted Items. | Only one RPT for a given default folder can be in a policy. |
| Personal tag | A user-applied exception on an item or folder. | Keep choices manageable; Microsoft suggests roughly ten or fewer personal tags. |
A mailbox can have only one assigned retention policy. Removing a tag from that policy is different from deleting the tag definition, and neither operation should be treated as an instant rewrite of every already-stamped item.
What happens during a mailbox run
- The assistant selects a mailbox from its workload.
- It reads the mailbox’s assigned retention policy and available tag definitions.
- It evaluates folder tags, inherited tags, and explicit item tags.
- It stamps or updates applicable metadata, including retention-start and expiration information where supported.
- It compares the calculated age with the tag’s threshold and checks holds, item type, folder, and destination requirements.
- For eligible items it performs the configured action: archive, delete with recovery, or permanent delete.
- It records success and processing information. Exact queueing, threading, and internal sub-assistants are implementation details Microsoft does not fully document and can change between versions.
Which tag wins?
Think from most specific to least specific:
- An explicitly tagged item normally wins.
- A tag applied to its folder is inherited by items and subfolders unless overridden.
- If no specific folder or item tag applies, the mailbox’s DPT supplies the default.
Moving a message can therefore change its effective tag: it may inherit the destination folder’s tag, or fall back to the DPT when the destination has no specific tag. A personal tag can override an inherited folder or default tag. This is why an apparently identical message can receive a different result after being moved.
#1 Best Overall
Retention age is not simply “days since it entered this folder”
For ordinary delivered messages, age generally derives from the delivery date; other created items use an appropriate creation or start date. Deleted Items needs special care:
- If an item already has a retention-start date, its original date can continue to control expiration after the move.
- If it has no start date, the MFA may stamp the move or processing date as the start date.
- Calendar items, tasks, and other special types have distinct handling.
- Contacts are not stamped with normal retention-start or expiration dates and do not expire through the ordinary MFA process.
- Corrupted items are skipped.
Example: a two-year-old message moved to Deleted Items can become immediately eligible under a 30-day deletion tag if its original start date is retained. A message with no prior start date may instead receive a new start date when processed, giving it a fresh 30-day interval. See Microsoft’s retention-age rules before predicting a date.
Actions and what “deleted” means
- Move to archive: transfers the item to the user’s archive mailbox. The archive must be provisioned and usable.
- Delete and allow recovery: removes the item from the visible folder while retaining a recovery path governed by mailbox Recoverable Items settings.
- Permanently delete: removes it without the same normal recovery path.
Archive and deletion tags may coexist. Microsoft recommends an earlier archive age and a later deletion age when both actions are intended for the same content. Holds can preserve data even when an item reaches its MRM age, so “deleted” does not always mean immediately unrecoverable.
Rank #2
Why a policy change appears late
Separate four events:
- Policy application: the mailbox is assigned a policy.
- MFA processing: the assistant actually visits it.
- Eligibility: an item has reached the tag’s age and passes other checks.
- Action completion: the item is moved or deleted.
Exchange Server 2016, 2019, and Subscription Edition describe MFA as always running under throttling, with a default one-day work-cycle target. That is a capacity goal, not an exact appointment. Exchange Online is also workload- and service-throttled. Replication, mailbox moves, large mailboxes, and competing workloads can add delay.
Force processing, then verify
In Exchange Management Shell or Exchange Online PowerShell, use:
Start-ManagedFolderAssistant -Identity [email protected]You need the appropriate messaging-records-management permissions and the correct Exchange PowerShell session. A successful command requests processing; it does not override a hold, an explicit personal tag, an unexpired age, an unsupported item type, or service throttling.
Validate in this order:
- Confirm the mailbox’s assigned retention policy.
- Confirm the intended tags are linked and enabled.
- Check each tag’s action and retention age.
- Inspect the item or folder for an explicit personal or folder tag.
- Run the command above and allow time for processing.
- Check Outlook or Outlook on the web, the archive mailbox, Deleted Items, and Recoverable Items.
On legacy Exchange deployments, administrators may also encounter:
Export-MailboxDiagnosticLogs -Identity [email protected] -ExtendedPropertiesHistorical Elc* properties include ElcLastRunSuccessTimeStamp, ElcLastRunUpdatedItemCount, ElcLastRunTaggedWithArchiveItemCount, ElcLastRunTaggedWithExpiryItemCount, ElcLastRunArchivedFromRootItemCount, and ElcLastRunDeletedFromRootItemCount. Availability and meaning are version- and environment-dependent; do not assume every Exchange Online tenant exposes them.
Common “nothing happened” diagnoses
| Symptom | Likely cause | What to check |
|---|---|---|
| Policy is assigned, but no item moved | MFA has not reached the mailbox or items are not old enough. | Run MFA manually, then allow processing time; verify age. |
| One message is treated differently | Explicit personal tag or folder inheritance. | Inspect the item and destination folder’s tags. |
| Deletion stopped after a policy edit | Tag was removed from the policy, disabled, or still stamped on items. | Distinguish removing, disabling, and deleting a tag. |
| Items remain visible under a hold | Retention hold, Litigation Hold, or In-Place Hold. | Identify the exact hold and inspect Recoverable Items. |
| Archive action has no result | No provisioned or usable archive mailbox. | Verify archive status and licensing/configuration. |
| Different results on-premises and online | Hybrid tag or policy definitions are inconsistent. | Compare definitions in both organizations. |
| Some objects never expire | Contacts, corrupted items, or other special item handling. | Check item type and the documented retention-age exceptions. |
High-risk configuration changes
Removing a tag from a policy prevents that policy from newly associating the tag, but existing items carrying the tag may continue to follow its settings. Deleting the tag is more disruptive: removing a widely stamped definition can trigger substantial restamping work across mailboxes. Plan and monitor such changes.
Disabling a tag pauses MFA action on items carrying it; those items remain tagged, and re-enabling the tag can resume archive or deletion behavior. It is not equivalent to assigning “Never Delete.”
Version and product context
- Exchange 2010: older documentation often describes scheduled processing windows. Treat that language as historical.
- Exchange 2013: retains MRM concepts but implementation details differ from current releases.
- Exchange Server 2016, 2019, and Subscription Edition: throttle-based, continuously running MFA with a configurable work-cycle target.
- Exchange Online: supports legacy MRM and the MFA, but service-side throttling and Microsoft 365 governance features also apply.
- Microsoft Purview: use retention policies and labels when the requirement spans Exchange, SharePoint, OneDrive, Teams, or organization-wide records governance.
Operational checklist
- Verify the mailbox’s assigned policy.
- Verify tag membership, state, action, and age.
- Check explicit item and folder tags.
- Check retention, Litigation, and In-Place Hold status.
- Confirm archive availability for archive actions.
- Run
Start-ManagedFolderAssistant. - Allow for throttling, replication, and mailbox workload.
- Verify the destination, Deleted Items, archive, and Recoverable Items.
- In hybrid deployments, compare policy and tag definitions on both sides.
For authoritative behavior and syntax, consult Microsoft’s retention-tag guide, MFA configuration guide, and retention-policy procedures.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
