How to Reassign a Copilot License and Check History Retention

Reassigning a Copilot seat changes who is entitled to the service. It does not transfer one person’s conversations to another, and it is not a backup operation. Before changing a seat, distinguish retaining records from being able to reopen a conversation in the app.

This guide covers organizational Copilot licenses. It does not promise that all history will remain visible after a license change. Official guidance checked October 14, 2026.

Separate the license, saved files, and retained interaction records

Microsoft documents compliance copies of Copilot interactions in hidden Exchange mailbox storage. These records are intended for supported compliance tools, not direct browsing of a folder named “CopilotChat.” Saved documents have their own locations and retention rules; not every draft, meeting summary, or generated response is automatically a OneDrive file.

Microsoft’s retention guidance for Copilot explicitly distinguishes what a user sees from what is retained for compliance. A visible conversation is not proof of preservation, and an absent conversation is not proof that every retained copy has been deleted.

Do not use a general “account still exists, therefore all data is safe” rule. Removing underlying mailbox or storage licenses, deleting an account, user deletion requests, retention policies, and holds can have different consequences.

Make a preservation decision before freeing the seat

1. Define what must be kept. List the saved work products, specific conversations, and any business or legal preservation requirement. Do not export an entire mailbox simply because a seat is moving.
2. Check the existing controls. Ask the records or compliance owner to verify the applicable retention policy, location, scope, and licensing. Do not assume a generic Teams retention rule covers every current Copilot interaction.
3. Save necessary work products appropriately. Confirm where final documents are stored and who should access them. Use approved file sharing for a handover rather than moving another person’s complete chat history.
4. Verify preservation through the right tool. Where formal records are required, the authorized compliance team should validate them using supported eDiscovery procedures before the licensing change.

If preservation cannot yet be verified, delay the change for that user and resolve the requirement. An expected saving on one seat is not a reason to risk business records.

Reassign only the intended Copilot entitlement

1. Use an appropriately authorized license administrator. In the Microsoft 365 admin center, open Users > Active users, select the original user, and open Licenses and Apps.
2. Confirm whether the Copilot entitlement is a separate product or part of a bundle, and whether it is assigned directly or through a group. A bundled entitlement cannot safely be treated as an independent seat without checking the offer.
3. For a directly assigned standalone Copilot product, remove only that approved product and save. Preserve the user’s required base Microsoft 365, Exchange, and storage entitlements. Do not select a bulk “unassign all” action.
4. For a group-managed assignment, have the licensing owner make the scoped group change and inspect its effect. Do not remove unrelated group membership merely to free one benefit.
5. Confirm the product’s available capacity and assign the approved entitlement to the recipient, who must meet its prerequisites. Inspect errors and verify the recipient’s own access after provisioning.

Use Microsoft’s license-assignment guide and group-assignment guide. Do not promise that release or activation completes in 30 minutes.

Use eDiscovery for records—not PST import as a chat migration

Microsoft’s Copilot compliance guidance describes searching and exporting interaction records through Purview eDiscovery. That requires the appropriate permissions, licensing, and organizational authorization. A search or export is a records workflow; it is not a supported method of recreating an interactive Copilot history in another account.

Do not follow instructions to export a supposed hidden chat folder from the Exchange admin center and import it into the recipient’s mailbox. A PST file does not transfer a Copilot identity, entitlement, or usable conversation state. It can also expose unrelated private content.

If the original user needs ongoing access to old work, confirm the supported app experience for that account. Reassigning a license later is not a guarantee that every past conversation will reappear.

Verify the change and keep offboarding separate

• Confirm the recipient can use the intended feature with their own account.
• Check the original user’s remaining licenses and ordinary access to required saved files.
• Have the compliance owner confirm any required retained records independently of what appears in the chat sidebar.
• Record the assignment change, date, approved preservation decision, and unresolved access issues.

If the original user is leaving, follow the organization’s full offboarding process. Account deletion, mailbox retention, and OneDrive retention do not share one universal 30-day rule. Microsoft’s SharePoint and OneDrive retention guidance is separate from Copilot interaction retention. Do not remove holds or create new legal holds as an improvised license-transfer step; those decisions belong to the authorized records and legal owners.