Microsoft's low-code tool for building workflows and AI agents. Its generative agents may hand each tool call they intend to make to an external threat detection service, Microsoft Defender for example, for checking.
Also called Microsoft Copilot Studio.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Copilot Studio in context, with comparison tables and the common traps.
Terms in this definition
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
- External
API Management virtual network mode in which the gateway stays public but can call private back ends inside the VNet.
Related terms
- Agent
A specialised form of Microsoft Copilot set up for one particular job, pairing instructions with knowledge and skills. You can create one in Copilot Studio, SharePoint or Agent Builder, and administrators control them from the Microsoft 365 admin center.
- Agent Builder
A Microsoft Copilot tool where people describe a declarative agent in plain language, or fill in a Configure tab, and ground it in sources like SharePoint or Copilot connectors. If the agent later needs actions or workflows, a copy moves into Copilot Studio.
- Copilot Credits
The single unit in which Microsoft meters usage-based charges for agents and AI services, Copilot Studio among them. They're paid for with prepaid packs, a pre-purchase plan, or pay-as-you-go through Azure.
- Copilot Studio external threat detection
Preview option in the Power Platform admin center whereby each tool call a generative Copilot Studio agent plans is sent to a provider endpoint, authorised via an Entra app ID, that permits or blocks it; with no reply within one second, the call is allowed.
- CRM
Customer relationship management software, which keeps track of customer contacts, sales and service. A CRM sales assistant is a common example of an agent made with Copilot Studio.
- Data policy
Also known as a DLP policy in Power Platform, it puts each connector into a Business, Non-business or Blocked group. Apps, flows and Copilot Studio agents may then only combine connectors from the same group.
- Defender security for AI agents
Set up in the Defender portal by connecting Copilot Studio and the Microsoft 365 app connector, which share one Entra App ID. Agent tool calls are then checked at run time, risky ones blocked, and alerts and incidents raised.
- Microsoft Copilot experiences
A location you can pick in retention policies and in Communication Compliance to capture what people ask Microsoft-built Copilots and what those Copilots answer, covering, for example, Copilot Studio, Security Copilot, Copilot in Fabric and Microsoft Copilot. Copilot messages used to fall under the older Teams chats and Copilot interactions location.