Fix Exchange Online Retention Policy Not Deleting Sent Items
Question details
Find out why a shared mailbox retention policy is not deleting Sent Items after 90 days.

- Product
- Exchange Online in Microsoft 365
- Device & OS
- not provided
- Scenario
- A 90-day retention policy is assigned to the Sent Items folder of a shared mailbox.
- Observed behavior
- Running the Managed Folder Assistant does not reduce the message count, and an affected message shows a later expiration date than expected.
Identify the shared mailbox address and an affected Sent Items message, including its sent and displayed expiration dates. You need Exchange administrator permissions and a connection to Exchange Online PowerShell to inspect the mailbox and policy.
Verify the mailbox policy and Sent Items retention tag
Use this approach first to check whether the assigned policy contains the intended 90-day deletion tag.
Open PowerShell with the Exchange Online PowerShell module installed, then run Connect-ExchangeOnline and sign in with an authorized administrator account.
Run Get-Mailbox "SharedMailbox" | Format-List RetentionPolicy,RetentionHoldEnabled,LitigationHoldEnabled,InPlaceHolds,SingleItemRecoveryEnabled, replacing SharedMailbox with the mailbox address.
Run $p = Get-RetentionPolicy (Get-Mailbox "SharedMailbox").RetentionPolicy; $p.RetentionPolicyTagLinks | ForEach-Object { Get-RetentionPolicyTag $_ | Format-List Name,Type,RetentionEnabled,AgeLimitForRetention,RetentionAction }. Check for an enabled SentItems tag with a 90-day age limit and the intended deletion action. Also review any applicable default or personal tags.
In classic Outlook, open an affected Sent Items message and check File > Properties for retention policy information if available. Compare the applied policy and expiration date with the expected 90-day period.
After correcting any policy or tag assignment, run Start-ManagedFolderAssistant -Identity "SharedMailbox". Allow time for processing, then recheck the affected messages and folder count.

Check retention holds and preservation settings
Use this check when the correct tag is assigned but mailbox processing or deletion still appears to be suspended.
Work with Office files while managing Exchange Online separately
WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation work. Its familiar interface and Microsoft Office format support make it easy to migrate files, while Exchange Online retention policies remain managed in Microsoft 365.

Frequently Asked Questions
Why did running the Managed Folder Assistant not delete the messages?
The messages may not have reached their calculated expiration dates, the wrong tag may apply, or a retention hold may suspend processing. Check the mailbox policy and message expiration date, then allow time after running Start-ManagedFolderAssistant.
How do I check which retention policy is assigned to a shared mailbox?
In Exchange Online PowerShell, run Get-Mailbox "SharedMailbox" | Format-List RetentionPolicy, replacing SharedMailbox with the mailbox address. Use Get-RetentionPolicy and Get-RetentionPolicyTag to inspect its linked tags.
Why does a January message show an expiration date in July instead of April?
The displayed date may reflect a different applied tag or retention start date than expected. Check the message's retention information in classic Outlook if available, and inspect the policy's enabled tags and age limits in Exchange Online PowerShell.
Does a shared mailbox need a license for a basic deletion policy?
A shared mailbox generally does not need a license solely for a basic Exchange retention deletion policy. Licensing may be required for other features or circumstances, such as an archive or a mailbox exceeding shared-mailbox limits; check current Microsoft licensing requirements.
Does disabling single item recovery remove all holds?
No. Single item recovery and holds are separate settings. Check LitigationHoldEnabled and InPlaceHolds with Get-Mailbox, and review applicable Microsoft Purview retention policies and holds.




