How retention age is calculated in Exchange 2013
Applies to: Exchange Server 2013
The Managed Folder Assistant (MFA) is one of many mailbox assistant processes that runs on mailbox servers. Its job is to process mailboxes that have a Retention Policy applied, add the Retention Tags included in the policy to the mailbox, and process items in the mailbox. If the items have a retention tag, the assistant tests the age of those items. If an item has exceeded its retention age, it takes the specified retention action. Retention actions include moving an item to the user's archive, deleting the item and allowing recovery, or deleting the item permanently.
See Retention tags and retention policies for more information.
Determining the age of different types of items
The retention age of mailbox items is calculated from the date of delivery or in the case of items like drafts that aren't delivered but created by the user, the date an item was created. When the Managed Folder Assistant processes items in a mailbox, it stamps a start date and an expiration date for all items that have retention tags with the Delete and Allow Recovery or Permanently Delete retention action. Items that have an archive tag are also stamped with a move date.
Items in the Deleted Items folder and items that may have a start and end date, such as calendar items (meetings and appointments) and tasks, are handled differently as shown in this table.
| If the item type is... | And the item is... | The retention age is calculated based on... |
|---|---|---|
| Email message Document Fax Journal item Meeting request, response, or cancellation Missed call |
Not in the Deleted Items folder | Delivery date or date of creation |
| Email message Document Fax Journal item Meeting request, response, or cancellation Missed call |
In the Deleted Items folder | Date of delivery or creation unless the item was deleted from a folder that doesn't have an inherited or implicit retention tag. If an item is in a folder that doesn't have an inherited or implicit retention tag applied, the item isn't processed by the MFA and therefore doesn't have a start date stamped by it. When the user deletes such an item, and the MFA processes it for the first time in the Deleted Items folder, it stamps the current date as the start date. |
| Calendar | Not in the Deleted Items folder | Non-recurring calendar items expire according to their end date. Recurring calendar items expire according to the end date of their last occurrence. Recurring calendar items with no end date don't expire. |
| Calendar | In the Deleted Items folder | A calendar item expires according to its message-received date, if one exists. If a calendar item doesn't have a message-received date, it expires according to its message-creation date. If a calendar item has neither a message-received date nor a message-creation date, it doesn't expire. |
| Task | Not in the Deleted Items folder | Non-recurring tasks: <uiLmessage-received date, if one exists.message-received date, it expires according to its message-creation date.message-received date nor a message-creation date, it doesn't expire. A recurring task expires according to the A regenerating task (which is a recurring task that regenerates a specified time after the preceding instance of the task is completed) doesn't expire. |
| Task | In the Deleted Items folder | A task expires according to its message-received date, if one exists. If a task doesn't have a message-received date, it expires according to its message-creation date. If a task has neither a message-received date nor a message-creation date, it doesn't expire. |
| Contact | In any folder | Contacts aren't stamped with a start date or an expiration date, so they're skipped by the Managed Folder Assistant and don't expire. |
| Corrupted | In any folder | Corrupted items are skipped by the Managed Folder Assistant and don't expire. |
Examples
| If the user... | The retention tags on folder... | The Managed Folder Assistant... |
|---|---|---|
| Receives a message in the Inbox on 01/26/2013. Deletes the message on 2/27/2013. |
Inbox: Delete in 365 days Deleted Items: Delete in 30 days |
Processes the message in the Inbox on 1/26/2013, stamps it with a start date of 01/26/2013 and an expiration date of 01/26/2014. Processes the message again in the Deleted Items folder on 2/27/2013. It recalculates the expiration date based on the same start date (01/26/2013). Because the item is older than 30 days, it's expired immediately. |
| Receives a message in the Inbox on 01/26/2013. Deletes the message on 2/27/2013. |
Inbox: None (inherited or implicit) Deleted Items: Delete in 30 days |
Processes the message in the Deleted Items folder on 02/27/2013 and determines the item doesn't have a start date. It stamps the current date as the start date, and 03/27/2013 as the expiration date. The item is expired on 3/27/2013, which is 30 days after the user deleted or moved it to the Deleted Items folder. |
More Info
Items in mailboxes placed on Retention Hold aren't processed by the Managed Folder Assistant until the Retention Hold is removed.
If a mailbox is placed on In-Place Hold or Litigation Hold, expiring items are removed from the Inbox but preserved in the Recoverable Items folder until the mailbox is removed from In-Place Hold and Litigation Hold.
In hybrid deployments, the same retention tags and retention policies must exist in your on-premises and Exchange Online organizations in order to consistently move and expire items across both organizations. See Export and import retention tags for more information.
In Exchange Online, the Managed Folder Assistant processes a mailbox once in seven days. This might result in items being expired up to seven days after the expiration date stamped on the item.