Bring the agents employees build in Microsoft Copilot under an attested owner.
Amplifier connects with Microsoft Copilot to find the AI agents employees build, confirm an attested owner and purpose for each, and scope down access for Copilot Studio agents through Microsoft Entra instead of revoking it.
From Copilot usage to Copilot-built agents
How employees use Microsoft Copilot is AI Governance. When an employee builds an agent with Microsoft Copilot, that agent gets its own attested owner, purpose, and record
The likely builder gets one question in Slack or Teams: did you build this agent, and will you attest as its owner?
We ask each owner what the agent is for and record the answer. No purpose is recorded until the owner confirms it
At a glance
Release Status
Beta
Categories
AI Security
Reaches employees in
Slack and Microsoft Teams
Scope access down instead of shutting agents off
Amplifier compares access and behavior signals from connected tools with the purpose the owner declared
An agent that can read an entire OneDrive but uses one folder gets one question: scope it down, revoke it, or keep it?
For Copilot Studio agents, security decides the action and Amplifier narrows the agent's permissions through Microsoft Entra
Keep a record from onboarding through retirement
Each agent carries its attested owner, declared purpose, and every decision, with timestamps
We keep the decisions, not the activity log: Amplifier monitors agent activity without storing prompts, responses, or tool calls
Report validated, scoped-down, and retired agents to auditors, insurers, and the board from your own environment
