Microsoft Copilot Studio

Microsoft's platform for building and deploying custom AI agents, including agents that use Power Platform connectors, agent flows, REST API tools, MCP servers and computer use as tool mechanisms.

AI capabilities recorded

• Connector Tools

  Active · verified 2026-09-10

  Copilot Studio agents can be given Power Platform connector tools, allowing the agent to invoke connector actions that read from and write to connected Microsoft and non-Microsoft services.

• AI Approvals

  Preview · verified 2026-09-18

  A Microsoft-documented preview feature of Microsoft Copilot Studio agent flows in which an AI stage inside a multistage approval evaluates an approval request against maker-written natural-language instructions and supplied inputs (text, documents, images, knowledge and outputs of earlier flow stages) and returns an Approve or Reject decision with a rationale in JSON. The decision governs the approval: by default an approval decision continues the approval to the next stage, a rejection ends the approval as rejected, and a failure to decide ("Analysis failed") continues to the next stage. The decision and rationale are visible in the Approvals center History tab and logged in the Power Automate prompt builder Activity section. Any business-system write, message or transaction that follows is performed by other agent-flow actions and connectors, not by the AI approval stage, and is not attributed here.

• Computer use

  Active · verified 2026-09-21

  A Copilot Studio agent tool that uses a vision-and-reasoning model to operate websites and Windows desktop applications through a virtual mouse and keyboard on a configured Windows machine, enabling multi-step GUI tasks where no API integration exists.

• Event Triggers

  Active · verified 2026-09-22

  Event and schedule based initiation for Copilot Studio agents. A defined event in a connected system, or a recurrence schedule, sends a payload to an agent with generative orchestration turned on; maker-authored instructions and the payload determine which of the agent's existing topics, actions or tools are invoked. No originating user message is required. Trigger connections are authenticated with the agent maker's account.