Can we audit and retain Copilot prompts and responses?

You’re right to treat prompts as organisational records, not chat fluff. If staff paste client data into Copilot, “we can’t see it” is a compliance failure waiting to happen — not a privacy feature.

Here’s what’s going on. Microsoft Purview already covers Microsoft 365 Copilot and Copilot Chat for auditing, DSPM for AI, communication compliance, eDiscovery, and Data Lifecycle Management. Prompts and responses land in the unified audit log and can surface in DSPM activity explorer (including the prompt/response text if you’re in the right Content Viewer role group). For retention and legal hold, the interactions are stored in a hidden folder in the user’s Exchange mailbox — so eDiscovery searches mailbox sources and can use conditions such as Copilot activity / IPM.SkypeTeams.Message.Copilot.*. Retention policies use the Microsoft Copilot Experiences location; for some other AI apps you first need a collection policy (for example DSPM for AI’s “Capture interactions for Copilot experiences”).

Jack Schofield’s Second Law of Computing (historically attributed) says data doesn’t really exist unless you have at least two copies. For AI interactions, that means a retention policy and an eDiscovery path you have actually tested — not a screenshot of DSPM from a demo tenant.

Practical options:

1. Turn auditing on, then use DSPM for AI as the front door. Confirm Purview Audit is activated, open the Microsoft 365 Copilot view, and run the one-click recommendations (risky AI usage, unethical behaviour, protect labelled items from Copilot processing). Best first day for most UK tenants.
2. Add a retention policy for Microsoft Copilot Experiences with a period Legal can defend. Pair with auto-apply retention labels for cloud attachments and links shared in … and Copilot if you must keep the exact file version Copilot referenced. Moderate effort; matches Learn’s retention model.
3. Prove eDiscovery before the first case. Create a dry-run case, search a pilot user’s mailbox for Copilot activity, export a review set. If that fails, fix roles and collection policies before you promise auditors “full transcript retention.”
4. Communication compliance for generative AI if conduct and sensitive-data prompts matter as much as retention. Useful overlay; doesn’t replace retention/eDiscovery.

The caution: seeing prompts in activity explorer needs the right Purview roles — not every Compliance Admin can read the text. Some agent/Fabric surfaces still lag or need extra tenant settings and collection policies. Product names and ItemClass values change; verify against current Learn, not a 2024 slide deck. And retention in a hidden mailbox folder is verified with eDiscovery tools, not by scrolling the Copilot UI.

I’d suggest a one-page Wave 0 note: Audit on, DSPM Copilot view owned by Compliance, retention period agreed with Legal, and one successful eDiscovery dry run dated and filed. That is Steady GRC before you celebrate seat counts.

You’re asking the right question. Steady before scale means the prompts are governed like mail — because that’s where Microsoft stores them.