Copilot in Outlook and Email Retention: Check Missing Messages Safely

When Copilot in Outlook misses an older message, first establish where that message is and whether the particular Copilot feature supports that mailbox. Do not extend retention, exempt a folder or automatically copy email just to make a summary work. Those changes can undermine an organization’s approved disposal and preservation requirements.

This guide separates mailbox availability, retention and Copilot feature support so you can investigate the missing information without creating uncontrolled copies.

Separate Email Retention From Copilot Availability

Microsoft Purview retention policies can retain, delete, or retain and then delete supported mailbox content. Exchange’s older MRM retention tags and policies also include mailbox-management actions such as moving items to an archive. These are not two interchangeable “Copilot retention modes.”

A message can disappear from the ordinary mailbox view while a compliance copy remains. Microsoft’s Exchange retention guidance explains the Recoverable Items store and the effect of overlapping preservation. That copy is not automatically an ordinary Copilot source.

Similarly, a Copilot answer is not an inventory of every retained message. Do not infer permanent deletion from a missing citation, or legal preservation from a successful summary.

Check the Message and Mailbox Before Changing Policy

1. Identify a specific missing message. Record its sender, subject, date, intended account and the task that failed. Avoid sending confidential message content to a public support forum.
2. Look for it directly in Outlook. Confirm whether it is in the primary mailbox, the ordinary Archive folder, an online archive mailbox, Deleted Items or another mailbox. An Archive folder and an archive mailbox are not the same location.
3. Identify the exact Copilot experience. A thread’s Summarize button, Copilot Chat inside Outlook, and the separate Copilot app are different entry points. Record which one failed, the client and the signed-in account; do not diagnose every missing message as a primary-mailbox restriction.
4. Compare with an allowed test. Try the same task on a harmless message in the supported primary mailbox. This helps distinguish general feature availability from a particular source limitation.

Mailbox scope checked October 14, 2026: Microsoft’s requirements page, updated October 5, says Copilot can use permitted content in archive, shared and delegate mailboxes as well as the primary Exchange Online mailbox. Group mailboxes remain unsupported. Availability still depends on the experience, app, license and tenant configuration.

• Copilot Chat inside Outlook: the dedicated shared/delegated mailbox guide supports summarizing and drafting while working in that mailbox, including folder-level permissions. It does not require special mailbox text in the prompt. That guide does not yet support direct email triage, sending, or meeting-management actions for those mailboxes.
• The separate Copilot app: its shared/delegate mailbox instructions require the applicable Copilot license, say to specify the mailbox in the prompt, and require full delegate access rather than only shared-folder permissions. Do not expand delegation solely to work around a failure; use the approved experience that matches the user’s existing access.
• A specific Outlook button or archive scenario: verify that particular feature in the deployed client. The general requirements establish archive-content support, not a guarantee that every Outlook button works across every archive. An archive license by itself does not establish Copilot entitlement or feature availability.

The general Outlook FAQ still contains a blanket primary-mailbox-only statement that conflicts with the current requirements and dedicated shared-mailbox guidance. Do not use that statement to reject all shared/archive use, or assume the opposite—that all Outlook actions now work there. For an unresolved feature-specific mismatch, provide these document references and your reproduction to Microsoft support.

There is no established “Copilot pane > Settings > Data sources > Archive mailbox” checkbox for solving this problem. Keep product-specific source support separate from what Outlook itself can display.

Have the Records Owner Investigate the Actual Retention Rule

If the message was moved or removed, ask the Exchange or compliance administrator to identify the applicable MRM tag, Purview policy or retention label, its scope, and any hold. Provide the message details and observed location instead of asking for a blanket 30-to-90-day extension.

Adaptive scopes select supported users, groups or sites using their attributes. The previously suggested NOT (FolderName eq 'CopilotProcessed') query is not a documented way to exempt an Outlook folder from a Purview mailbox policy.

If the business genuinely needs a different lifecycle, the records owner should approve a documented change with the proper scope and impact review. A missing Copilot result does not, by itself, justify overriding a deletion requirement or releasing a hold.

For a legal or investigative request involving retained copies, use the organization’s authorized discovery process. Do not broaden mailbox delegation simply to make the evidence available to a conversational feature.

Use a Safe Workflow for Ongoing Summaries

Work from approved, currently available messages, review the relevant thread directly and verify important dates, names and decisions against the originals. If an essential item is outside the feature’s supported scope, complete that part manually or use another explicitly approved records workflow.

Do not set up an arrival-triggered flow that moves every new email into an exempt folder. Moving is not copying, and neither action guarantees that retention no longer applies. A shadow archive can create its own privacy, access and disposal problems.

There is no verified fixed 15-minute Copilot indexing cycle on which to base a retention schedule. Record the product/client, task, timestamp, message location and error for support if a supported message still fails. The objective is an accurate summary within approved data handling—not a promise that Copilot can always access the full history.