> For the complete documentation index, see [llms.txt](https://msdocs.aohwv.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://msdocs.aohwv.com/quick-start/step-5-copilot.md).

# Step 5 — Copilot

Copilot activity is recorded in the Microsoft 365 audit log, so there's **no new connection to set up**. It arrives through the Microsoft 365 connection from Step 4.

{% hint style="info" %}
**Time:** about 5 minutes
{% endhint %}

### What we recommend

| Copilot activity                              | Collect?          | Why                                                                                    |
| --------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------- |
| **Admin changes** (settings, plugins, agents) | **Yes**           | An attacker or rogue admin could use these to expose company data                      |
| **Everyday Copilot use** (CopilotInteraction) | **No**            | Tracks who uses Copilot and how often. That's productivity data, not a security signal |
| **Prompts and responses**                     | **Not available** | Microsoft's audit log doesn't include what users typed or what Copilot answered        |

### Filter out everyday use

In your SIEM, add a filter that drops events where **Operation** equals **CopilotInteraction** before they're stored. Most SIEMs call this a **drop rule**, **filter** or **ingest-time exclusion**. 

{% hint style="warning" %}
**Drop only CopilotInteraction.** Filtering more broadly could remove Copilot admin changes and other Microsoft 365 activity, such as Teams.
{% endhint %}

{% hint style="info" %}
**Why we filter it:** collecting every Copilot interaction can look like employee monitoring to HR, legal and privacy teams, and it adds SIEM cost without improving threat detection.
{% endhint %}

## Related

* [Step 4 — Microsoft 365](/quick-start/step-4-microsoft-365.md) — The connection Copilot data arrives through
* [Step 6 — Azure](/quick-start/step-7-azure-defender-for-cloud.md) — Defender for Cloud and the Azure Activity Log
* [Get Expert Help ](/get-expert-help/overview.md)— Rolling out Copilot? RedLegg Advisory can help you set security guardrails first


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://msdocs.aohwv.com/quick-start/step-5-copilot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.