Control 3.2: Data Retention Policies for Copilot Interactions — Portal Walkthrough
Step-by-step portal configuration for establishing data retention policies that govern the lifecycle of Copilot-generated content and interaction history in financial services environments.
Regulatory applicability
Regulatory citations identify commonly referenced requirements. Applicability, record classification, and retention periods are a firm and counsel determination; this framework does not assert that any regulation applies or is satisfied. See the Regulatory Applicability Questions appendix.
Prerequisites
- Role: Purview Compliance Admin or Records Management Administrator
- License: Microsoft 365 E5 or E5 Compliance add-on
- Access: Microsoft Purview portal
Steps
Step 1: Navigate to Data Lifecycle Management
Portal: Microsoft Purview portal Path: purview.microsoft.com > Data lifecycle management > Microsoft 365
- Open the Data lifecycle management solution.
- Select the Retention policies tab to view existing policies.
- Identify any existing policies that may already cover Copilot content locations.
Step 2: Create Retention Policy for Microsoft Copilot Experiences
Portal: Microsoft Purview portal Path: purview.microsoft.com > Data lifecycle management > Retention policies > New retention policy
The Microsoft Copilot experiences location is the primary retention target for M365 Copilot deployments. It covers Microsoft Copilot Chat history, Copilot interactions in Word/Excel/PowerPoint/Outlook/Teams, and Copilot Pages.
- Click New retention policy and name it
FSI-Copilot-Experiences-Retention. - Add a description: "Retains Microsoft Copilot experiences content per FSI regulatory requirements — covers Copilot Chat history, meeting recaps, and in-app Copilot interactions."
- Under Choose the type of retention policy, select Static.
- Select the locations to include:
- Microsoft Copilot experiences — toggle to On
- Set retention period to 3 years for the communications baseline if approved in the firm's records schedule (commonly cited for SEC/FINRA business-communication records; applicability: confirm).
- For regulated deployments, create a separate 6-year policy for this location if approved in the firm's records schedule (commonly cited for broker-dealer/financial records; applicability: confirm).
- Choose Retain items for the specified period with Do nothing at the end (retain only).
- Click Submit.
Note on related location categories: You will also see Enterprise AI Apps and Other AI Apps in the location selector. Current Microsoft Learn documentation lists Copilot Studio under Microsoft Copilot experiences. Enterprise AI Apps covers Entra-registered AI apps, ChatGPT Enterprise, and Microsoft Foundry; Other AI Apps covers third-party AI tools detected through browser or network activity. For M365 Copilot and Copilot Studio deployments covered by this framework, configure retention policies targeting the Microsoft Copilot experiences location. Assess the other AI app categories separately for broader AI governance programs.
Step 3: Create Retention Policy for Copilot-Generated Documents
Portal: Microsoft Purview portal Path: purview.microsoft.com > Data lifecycle management > Retention policies > New retention policy
- Create a policy named
FSI-Copilot-Generated-Content-Retention. - Select locations: SharePoint sites, OneDrive accounts, Exchange email.
- Set retention to 6 years for financial records coverage if approved in the firm's records schedule; SEC Rule 17a-4(a) applicability: confirm.
- This policy covers documents, emails, and presentations created or modified with Copilot assistance.
Step 4: Verify Microsoft Copilot Experiences Policy Distribution
Portal: Microsoft Purview portal Path: purview.microsoft.com > Data lifecycle management > Retention policies > [select policy] > Policy status
After creating the Microsoft Copilot experiences retention policy:
- Select the policy from the Retention policies list.
- Under Status, verify the Distribution status shows Success (may take up to 24 hours after creation).
- If status shows Pending after 24 hours, review the error details and re-submit if needed.
- Verify the policy scope includes all users or the targeted user groups.
Step 5: Configure Retention Labels for Copilot Content
Portal: Microsoft Purview portal Path: purview.microsoft.com > Records management > File plan > Create a label
- Create a retention label named
FSI-Copilot-Regulatory-Record-6yr. - Set the retention period to 6 years from creation date if approved in the firm's records schedule.
- Mark as a regulatory record if required by your compliance framework.
- Publish the label to supported file and email locations such as SharePoint sites, OneDrive locations, Exchange email, and Microsoft 365 Groups as applicable. Use retention policies, not retention labels, for Copilot prompts and responses in the Microsoft Copilot experiences location; use auto-apply retention labels for cloud attachments referenced in Copilot when the goal is to retain file versions.
Step 6: Evaluate Priority Cleanup for Documented Storage Remediation (Recommended Tier)
Portal: Microsoft Purview portal Path: purview.microsoft.com > Data lifecycle management > Priority cleanup
Priority cleanup is a separate Data Lifecycle Management feature that can override existing retention settings or eDiscovery holds for selected SharePoint and OneDrive content after simulation and approval. Microsoft documents Copilot-related use cases such as stale Teams meeting recordings/transcripts and departed-user Preservation Hold Library cleanup. It is not documented as a detector for unsent Copilot drafts or generic Copilot-generated content signatures. Baseline-tier deployments should use standard retention.
- Confirm the operator has the Priority Cleanup Admin role.
- Define the narrow business scenario, such as stale Teams meeting recordings/transcripts or departed-user Preservation Hold Library cleanup.
- Run the required simulation and review the item sample, affected holds, and any eDiscovery-hold dependencies.
- Confirm that no items marked as records or regulatory records are in scope; Priority cleanup cannot target them.
- Route the request through the required approval workflow, including eDiscovery Administrator approval when an eDiscovery hold applies.
- Document the scope decision, simulation results, approvals, and regulatory rationale in the firm's records management schedule.
Important: Do not apply Priority cleanup to documents that have been shared, sent, saved to shared drives, declared as records, or otherwise treated as business records unless compliance/legal has approved the exception. If the firm needs shorter retention for unsent Copilot drafts, implement and document a standard retention/deletion policy rather than labeling it as a Microsoft-documented Priority cleanup scenario.
Step 7: Verify Threaded Summary Retention Coverage
Portal: Microsoft Purview portal Path: purview.microsoft.com > Data lifecycle management > Retention policies
Threaded Copilot summaries (meeting recaps, conversation summaries) are retained independently from their source content. Verify complete coverage:
- Confirm the Microsoft Copilot experiences retention policy is active — this location covers Copilot-generated meeting recaps and summaries.
- Confirm the Teams retention policy is active — this location covers native Teams channel and chat messages. Copilot prompts, responses, recaps, and threaded summaries require the Microsoft Copilot experiences policy.
- Run a test: delete a Teams meeting transcript and verify that the Copilot-generated meeting recap is still present and covered by the Microsoft Copilot experiences retention policy.
- Document the verification outcome in the firm's retention coverage log.
FSI Recommendations
| Setting | Baseline | Recommended | Regulated |
|---|---|---|---|
| Microsoft Copilot experiences retention | Required | Required | Required (6 years as a firm-approved extended-retention example; applicability: confirm) |
| Exchange retention (email + legacy Copilot Chat) | Required | Required | Required |
| SharePoint/OneDrive retention | Required | Required | Required |
| Teams retention | Required | Required | Required |
| Priority cleanup for AI drafts | Not recommended | Optional (scoped) | Optional (conservative) |
| Regulatory record label | No | Recommended | Required |
| Threaded summary coverage verification | Optional | Recommended | Required |
Regulatory Alignment
- SEC Rule 17a-4(a) — Six-year retention citation for broker-dealer records; Microsoft Copilot experiences scope: confirm
- SEC Rule 17a-3(a)(17) — Communications-record citation; conservative retention of Copilot-generated content is a firm-approved example pending counsel confirmation
- FINRA Rule 4511 — Books-and-records retention citation; Copilot Chat history and meeting recap scope: confirm
- FINRA Rule 4511(c) — Preservation format citation; threaded-summary treatment and accessible-format requirements: confirm
- SOX Section 802 — Record-destruction citation; Copilot-generated financial content scope: confirm
Next Steps
- Proceed to PowerShell Setup for automated retention policy deployment
- See Verification & Testing to validate retention policies are applied correctly
- Back to Control 3.2