Microsoft Copilot · Agent and workflow builder
Product and access
Copilot Studio is Microsoft's development environment for custom agents and agent flows. Microsoft 365 Copilot is one possible channel or product context, rather than the same component.
Core features
7 features from provider sources · sources reviewed on 30 September 2026. Availability and limitations are listed directly below.
Agents with generative orchestration
The agent selects a combination of topics, tools, and knowledge to match the request.
Source 6Topics and conversation flows
Topics form conversation paths from messages, questions, conditions, and routing.
Source 3Publish and analyze
Documentation covers testing, evaluations, channels, publishing, and management.
Source 2
Requirements and limits
‘Still open’ means the reviewed sources do not answer this point clearly.
Requirement
Choose the execution environment
The standard runtime and GitHub Copilot runtime offer different capabilities. The selected environment determines the available scope.
Source 8Requirement
Requirement for event triggers
Event Triggers require generative orchestration and a configured connector connection.
Source 4Limitation
Managed data policies
Available Event Triggers depend on the organization's data policies administered in Power Automate.
Source 4Limitation
Usage and billing
Event payloads also count as agent messages and may consume Copilot credits.
Source 4Not yet confirmed
License by use case
The license and billing that apply to a specific agent configuration must be checked against the current tenant and use case.
Source 8
Practical tasks
Editorial examples based on documented features. No product tests performed.
Questions about internal policies
- Your input
- Approved policy documents and employee questions
- Possible result
- An internal agent answers questions from connected knowledge.
- What to check
- Check answers against source documents and restrict the publishing channel.
New task triggered by an event
- Your input
- SharePoint event, instructions, and defined agent flow
- Possible result
- The flow starts the agent and performs the planned processing step.
- What to check
- Check maker registration, policies, and the error path before activation.
Configure an internal assistant for questions about approved company documents.
Your possible prompt
Design a process for new requests: capture information, sort it by topic, and create a proposed response. Plan an approval step before external actions.
Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.
What you should know first
Microsoft Learn reviewed. The documentation distinguishes the standard harness from a GitHub Copilot harness; features, channels, and event triggers depend on the harness, environment, and policies.
Requirements & limitations
Quality depends on the workflow, data, model, and approvals. Check integrations and usage limits before use.
Setup
Configure environment, agent, and policies.
Pricing model
License / usage. Check current terms and included quotas with the provider.
The classification indicates the scope of effort. It is not a price or performance commitment.
Sources from the provider
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
-
learn.microsoft.com /en-nz/microsoft-copilot-studio/agents-overview
-
learn.microsoft.com /en-us/microsoft-copilot-studio
-
learn.microsoft.com /en-us/microsoft-copilot-studio/guidance/topics-overview
-
learn.microsoft.com /en-us/microsoft-copilot-studio/authoring-triggers-about
-
learn.microsoft.com /en-us/microsoft-copilot-studio/extend-agent-capabilities
-
learn.microsoft.com /en-us/microsoft-copilot-studio/advanced-generative-actions
-
learn.microsoft.com /en-us/microsoft-copilot-studio/advanced-flow-input-output
-
learn.microsoft.com /en-us/microsoft-copilot-studio/