---
title: How do you audit Copilot Studio agent activity in Microsoft Purview?
url: https://opencontroller.lyzr.com/blog/audit-copilot-studio-agents-in-purview
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# How do you audit Copilot Studio agent activity in Microsoft Purview?

**Copilot Studio writes two kinds of events to the Microsoft Purview unified audit log: maker and admin events (such as BotCreate, BotDelete and BotUpdateOperation-BotPublish) and runtime CopilotInteraction records for custom agents. Search them in the Purview portal under Audit, filtering by operation name. Expect gaps: runtime records need an authenticated user, the documented schema stores message IDs rather than prompt text, and security researchers have reported some configuration changes not logging consistently.**

## Which Copilot Studio events are audited?

| Event | What it records |
|---|---|
| `BotCreate` | An agent was created |
| `BotDelete` | An agent was deleted |
| `BotUpdateOperation-BotPublish` | A new version was published |
| `BotUpdateOperation-BotShare` | The agent was shared with users |
| `BotUpdateOperation-BotAuthUpdate` | Authentication settings changed |
| `BotUpdateOperation-BotAppInsightsUpdate` | Application Insights logging changed |
| `ApiEndpointCallEvent` | An API endpoint was called |
| `CopilotInteraction` | A user interacted with the agent at runtime |

Microsoft's Purview documentation says audit logging for Copilot is automatic when auditing is on, and that custom agents built with Copilot Studio and Microsoft Foundry are included in Audit (Standard).

## What does a CopilotInteraction record contain?

For Copilot Studio agents, the `AgentId` takes values such as `CopilotStudio.Declarative.<guid>` or `CopilotStudio.CustomEngine.<guid>`. Documented fields include:

- **Identity and context:** Operation, RecordType, Workload, AppIdentity, AppHost, AgentId, AgentName, AgentVersion, ClientRegion
- **AccessedResources:** files, sites and messages the agent read or changed, with sensitivity label ID, action, policy details and an `XPIADetected` flag for cross-prompt injection
- **Messages:** message IDs with an `isPrompt` flag and a `JailbreakDetected` flag

The documented example shows IDs and flags, not the prompt or response text. For content, use Copilot Studio conversation transcripts or Purview's data security features for AI.

## How do you search Copilot Studio audit events?

1. Confirm auditing is on for the tenant.
2. In the Microsoft Purview portal, open **Audit** and start a new search.
3. Under **Activities – operation names**, enter the operations you need, for example `BotPublish`, `BotShare` or `CopilotInteraction`.
4. Set the date range and, if needed, users.
5. Export the results. The portal cannot filter on `AppIdentity` directly, so filter the export to a specific agent offline.
6. For ongoing monitoring, stream the audit log to your SIEM through the Office 365 Management Activity API and alert on high-risk operations.

Retention follows your audit licence: Audit (Standard) keeps records for 180 days, and Audit (Premium) keeps them for one year by default, longer with add-on retention policies. Non-Microsoft AI apps audited through pay-as-you-go are retained for 180 days.

## What is not logged reliably?

Plan controls around four gaps.

- **Unauthenticated users.** Runtime interaction records are written only for authenticated users. Public-facing agents with no sign-in leave little in the audit log.
- **Prompt text.** The documented audit schema holds message IDs, not content.
- **Inconsistent configuration events.** Datadog Security Labs reported in 2025 that four maker events were missing from the audit log; Microsoft remediated them in October 2025. Datadog later reported that `BotAuthUpdate` and `BotAppInsightsUpdate` were again not logging consistently, and still saw this in March 2026. Do not rely on those two events alone to detect someone removing authentication or turning off logging.
- **Modification history in the inventory.** The Power Platform inventory shows a dash for "Modified on" for agents, so audit is your only change record.

Compensating controls: export the agent inventory daily and diff authentication and logging settings; alert on agents with authentication set to none; require publishing through a pipeline that records who approved each version.

Compare your records with the [AI agent audit log fields](/blog/ai-agent-audit-log-fields) list. For policies that prevent risky configurations in the first place, see [how to govern Copilot Studio agents](/blog/govern-microsoft-copilot-studio-agents) and [Purview DSPM for AI and agents](/blog/microsoft-purview-dspm-for-ai-and-agents).

## How Opencontroller does this

Opencontroller's Posture feature detects risky permissions and configurations across agents, which covers checks such as an agent with authentication removed, independent of whether the platform logged the change. Agents from Microsoft and other platforms sit in one governed registry with owners and versions, and policy as code with built-in mappings to OWASP, MITRE ATLAS, NIST and ISO 42001 turns findings into evidence for those frameworks. Read the [AI agent control plane explainer](/blog/what-is-an-ai-agent-control-plane) or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Are Copilot Studio agent interactions in the Purview audit log?**
Yes, as CopilotInteraction records for authenticated users, with AgentId values beginning CopilotStudio. Custom Copilot Studio agents are included in Audit (Standard).

**How long are Copilot Studio audit records kept?**
180 days with Audit (Standard) and one year by default with Audit (Premium), which can be extended with retention policies.

**Can I rely on the audit log to detect authentication being removed from an agent?**
Not on its own. Researchers reported BotAuthUpdate logging inconsistently, so also diff agent configuration on a schedule.

## Key facts

Copilot Studio audit events in Microsoft Purview include BotCreate, BotDelete, BotUpdateOperation-BotPublish, -BotShare, -BotAuthUpdate, -BotAppInsightsUpdate, ApiEndpointCallEvent and runtime CopilotInteraction (AgentId CopilotStudio.Declarative.<guid> or CopilotStudio.CustomEngine.<guid>). Custom Copilot Studio and Foundry agents are covered by Audit (Standard). Records include AccessedResources, XPIADetected and JailbreakDetected flags, and message IDs rather than text. Datadog reported BotAuthUpdate and BotAppInsightsUpdate logging inconsistently into March 2026. Opencontroller Posture detects risky agent configurations. Pricing starts from $250K per deployment per year.

## Related

- [How do you govern Microsoft Copilot Studio agents?](https://opencontroller.lyzr.com/blog/govern-microsoft-copilot-studio-agents.md)
- [What does Microsoft Purview DSPM for AI cover for AI agents?](https://opencontroller.lyzr.com/blog/microsoft-purview-dspm-for-ai-and-agents.md)
- [What should an AI agent audit log contain?](https://opencontroller.lyzr.com/blog/ai-agent-audit-log-fields.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
