When an employee asks Copilot to summarize the week's email or draft a proposal, documents, emails, and chats are opened in the background on that person's behalf. The user sees the answer. The IT and security team learns what happened from what Microsoft 365 records about the interaction.
That record goes into the Microsoft Purview unified audit log, the same place that holds file opens, sign-ins, and administrator actions. Below we go through what data a Copilot question produces, how long it is kept, how you can search it, and what to watch out for, since the log describes what your employees do.
Why you need to see how Copilot is used
Copilot works with the permissions of the signed-in user. If too many people have access to a file, Copilot makes that access quick and convenient to use. Finding overly broad sharing is work for before the rollout; the log shows afterward what actually reaches the answers once the cleanup is done.
The log is typically needed in four situations:
- Incident investigation. If an account has been taken over, the attacker can use Copilot to gather whatever the account can reach in minutes. The log shows which sources the questions touched, and when.
- Looking into a report. An employee reports that Copilot surfaced a document they should not be able to see. The log tells you which file it was and where it is stored, so the permission can be fixed.
- Checking the rules. If content labeled confidential must not end up in answers, the log lets you check whether the rule you configured really works that way.
- Usage overview. Which apps and which departments use Copilot, and where it is not used. This gives you data for planning licenses and training.
As regulatory background: for organizations within the scope of NIS2, handling and reporting incidents also assumes that logs of security events exist. The Copilot log is one more source for this, and it belongs in the logging policy next to the others. Which sources are generally worth collecting for an incident is covered in our article on logging.
Copilot events in the audit log
Microsoft 365 Copilot and Copilot Chat interactions go into the audit log without any extra configuration, as long as auditing is turned on in the tenant. It is on by default in most tenants, but check it anyway, especially in older or migrated tenants where someone may have turned it off at some point.
Each interaction creates one record with the CopilotInteraction record type. An interaction here is one question and the answer to it. A record is also created when the user has Copilot write text in Word, asks for a meeting summary in Teams, has it draft an email in Outlook, or asks a question in the Copilot chat interface.
Use of agents built in Copilot Studio also shows up in the audit log, as do some other Microsoft-managed AI experiences. Logging interactions with non-Microsoft AI apps is a separate Purview feature tied to pay-as-you-go billing. So do not assume the log shows the use of every AI tool: public chatbots used with a personal account do not appear in it by default.
Get-AdminAuditLogConfig cmdlet returns a UnifiedAuditLogIngestionEnabled value that shows whether auditing is on. If it is false, no Copilot records are created either, and records for the period when auditing was off cannot be recovered later.
What an interaction record shows, and what it does not
A Copilot record contains the following data:
- Who and when: the user ID, the time, and client details, as in every audit record.
- Where: the app in which the question was asked (Word, Excel, PowerPoint, Outlook, Teams, the Copilot chat interface), and the context, such as the ID of the open document or the meeting.
- From which sources: the list of resources used for the answer, such as files, emails, and sites, with their path and, where there is one, the ID of the sensitivity label.
- Which messages: the message IDs of the question and the answer, a conversation ID that links consecutive questions, and a flag if the system detected an attempt to get around the safeguards in a message.
- With which plugin: a trace of web search or any other plugin, if the answer needed one.
The record does not contain the text of the question or the answer. The log tells you that a user asked something in Outlook on Tuesday afternoon and that the answer drew on three files from a particular site. It does not tell you what the user asked. The source list still says a lot: if files from an HR site show up in the questions of a user who has no business there, there is a permissions problem, whatever the question was.
Where the question and answer text is kept
Microsoft 365 stores the text in a hidden folder of the user's Exchange mailbox, much as it does with Teams chats. The user cannot see this folder in the mailbox, but it can be searched and exported with Purview eDiscovery. It falls under Purview retention policies, not the audit log settings: you can create a separate retention or deletion policy for Copilot interactions.
Because the text lives in the mailbox, a departing employee's Copilot conversations are lost when the mailbox is deleted in the usual way, unless a retention policy or a legal hold keeps it as an inactive mailbox. Audit log records stay for their own retention period regardless.
| Data | Where it is kept | What governs its retention |
|---|---|---|
| Who, when, in which app, from which sources | Unified audit log, CopilotInteraction record | Audit retention (depends on the license level and the audit retention policy) |
| The text of the question and the answer | Hidden folder in the user's mailbox, searchable with eDiscovery | Purview retention policy for Copilot interactions |
| The content of the file used | In its original location (SharePoint, OneDrive, Exchange) | The retention settings of that location |
Retention period and license levels
How long the audit log is kept depends on the license. Audit (Standard), available in most Microsoft 365 subscriptions, keeps records for 180 days by default. Audit (Premium) comes with Microsoft 365 E5-level subscriptions or with an add-on license. It lets you create audit retention policies by record type and by user, with retention of up to one year, or up to ten years with a further add-on license.
The one-year default in Premium applies to Exchange, SharePoint, and Entra ID records. To keep Copilot records longer, create a policy specifically for the CopilotInteraction record type, and after setting it up, check that records really are kept for the intended period.
Choosing the retention period means weighing two considerations that pull in opposite directions:
- The needs of an investigation. An account takeover or internal misuse often comes to light months later. If the log has been deleted by then, the investigation cannot establish what the attacker or the employee accessed.
- Data minimization. The log is personal data and may only be kept for as long as its purpose justifies. A Copilot log kept for years that nobody uses is a privacy risk.
Record the decision in the logging policy, together with the reasoning. Keep Copilot records at least as long as file access records, because an investigation has to compare the two. Retention of the question and answer text is a separate decision: it can be shorter than for the audit record, since the text carries far more personal and business content.
Search, export, and alerting
Searching in the Purview portal
In the Audit section of the Purview portal you can filter for Copilot activities by date range, user, and activity. Searches require the Audit Logs or View-Only Audit Logs role. Assign these roles to a few named people only, because they show the activity of the whole tenant. Records do not appear right away: according to Microsoft's documentation, an event usually becomes searchable after 60–90 minutes, and the delay can be longer. For a fresh report, “no results” is therefore not a final answer yet.
Export and processing
Results can be exported to a CSV file. The details sit in a single column in JSON format, so they have to be split out for analysis, for example in a spreadsheet or with a script. For larger volumes, use the Exchange Online PowerShell command Search-UnifiedAuditLog -RecordType CopilotInteraction; for continuous collection, use the Office 365 Management Activity API, which can forward the records to a central log collector or a SIEM.
Forwarding to a SIEM pays off when Copilot records need to be read alongside other sources. Take a suspicious sign-in followed by a series of Copilot questions from the same session that draw on finance and HR sources: you only see that connection if the sign-in log and the Copilot log are in one place.
What to build alerts on
Purview alert policies work with activity-level conditions; you cannot filter in them on the details of a record, such as the labels of the sources used. For the rules below, the records therefore have to be exported or forwarded and processed in a SIEM or with a script. A few starting points:
- the sources of an answer include content marked with the highest sensitivity label, for a user whose job does not call for it,
- a user asks an unusually large number of questions in a short time, with sources from many different sites,
- the system flags an attempt to get around the safeguards in a message,
- Copilot activity appears on an account that should not be using it interactively, such as a service account or the still-active account of an employee who has left.
You can only set the threshold for “unusually large” once you know the real usage, so in the first weeks the rule should just notify and not trigger any automatic action. If a DLP policy blocks the use of labeled content, its matches also appear among the DLP alerts, so you do not need a separate rule built from the log for that case.
Privacy considerations in handling the logs
The Copilot log is about how employees do their work: who worked when, with what, and on which documents. The text of the questions can reveal even more, about the private affairs, health, or workplace conflicts of the person asking or of third parties. Handling it is therefore subject to the GDPR and to employment law.
A few points to settle at rollout:
- Purpose and legal basis. Write down what the organization uses the log for (security investigations, checking the rules, usage statistics) and what the legal basis is; for employer logging this is typically legitimate interest, supported by a balancing test. The log may only be used for the recorded purpose: a security log must not later turn into a tool for performance reviews.
- Informing employees. Under the Hungarian Labor Code (Act I of 2012, Section 11/A), an employer may monitor employees only with respect to conduct related to their employment, and must inform them in advance about the technical tools it uses. Copilot logging therefore has to be covered in the employee privacy notice. Where there is a works council, it has the right to give an opinion on the introduction of technical tools for monitoring employees (Labor Code, Section 264).
- Access on two levels. Audit records and question text each need a separate role. The audit records show the source and the time; only a specific, documented investigation justifies access to the text. A good practice here is the four-eyes principle: a second person also approves the eDiscovery search. eDiscovery actions are themselves recorded in the audit log, so you can check afterward who searched for what.
- Exported files. A CSV export takes the log out of the controlled Purview environment. Store exports in a location with restricted access, and delete them when the investigation is closed.
- Data subject rights. Under Article 15 of the GDPR, an employee can request the data held about them, and that can include the Copilot log and the text of their questions. Agree in advance who handles such a request, and how.
Employees need to know what goes into the Copilot log, who can look at it, and in what cases. The logging policy is therefore part of the Copilot rollout, and it helps to include a short, plain summary of it in the user guide.
Related service: Secure Copilot and Microsoft 365 AI rollout →