Microsoft Copilot Studio vs Orchestrator Zero
oz0 records agent jobs running on your infrastructure. Copilot Studio builds and hosts agents for Microsoft 365 and other channels. oz0 focuses on self-hosted operation across your machines, reviewed tool definitions and access to local and cloud models.
What Microsoft Copilot Studio is
Microsoft Copilot Studio is Microsoft's low-code studio for agents and workflows, part of Power Platform. Agents run in Microsoft's cloud, call connectors, MCP servers and other agents as tools, and publish to Teams, Microsoft 365 Copilot and websites. A computer use tool can drive Windows machines you register in Power Automate.
learn.microsoft.com- Runs
- Managed service
- Licence
- Proprietary SaaS
- Checked
- 27 October 2026
Side by side.
Microsoft Copilot Studio's ratings come from its own pages. A column's name opens its definition and how Orchestrator Zero does it. How we rated
Where it runs
Any machine you own
Yes
DocsConditional: Computer use on own PCs
Agents run on Microsoft's harnesses in Azure; only the computer use tool can work on Windows machines you own and register, or on Microsoft-hosted Cloud PCs.
Linux, macOS and Windows
No: Their cloud; Windows PCs
The agent runtime is Microsoft's cloud service, and the machines you can add for computer use must run Windows.
Self-hosted control plane
Yes
DocsNo: Microsoft cloud only
Copilot Studio is a hosted service in Microsoft's Azure datacenters; no self-hosted edition is documented.
No inbound ports
Yes
DocsConditional: Own PCs dial out; A2A calls in
Machines registered for computer use and desktop flows connect out through Azure Relay with no inbound ports, while external A2A agents and MCP servers must expose an HTTPS endpoint that Copilot Studio calls.
Fleet operations
Yes
DocsConditional: Computer-use machines only
Power Automate registers the Windows machines used for computer use, queues runs per machine, blocks new runs with maintenance mode and updates them automatically; the agents themselves run on Microsoft compute.
Durability
Durable runs
Conditional: Flows hold waits up to 30 days
Agent flows keep their state while they wait on steps such as approvals, for up to 30 days; resuming an agent run from its last finished step after a crash is not documented.
Governance
Tool policy outside the model
Conditional: Connector block, no approve
Admin data policies allow or block connectors, MCP tools and HTTP endpoints at runtime, with no rule that sends a call to a person; per-call allow or block comes only from previews (threat detection or maker-built hooks).
Approvals in chat
Yes: Teams, Outlook, portal
Agent flows pause on an approval step until assignees respond, and approvers answer from Teams, Outlook or the Power Automate portal; multistage and AI approvals are in preview.
Tool snapshots
Yes
DocsNo: MCP changes apply live
Copilot Studio picks up changed or removed tools on a connected MCP server automatically, with no review step.
Tenants built in
Yes
DocsYes: Power Platform environments
Each Power Platform environment holds its own agents, connections and Dataverse data with its own roles, and apps in one environment can only reach data sources in that environment.
Cost
Budgets that stop a run
Conditional: Credit cap; delayed enforcement
An optional monthly Copilot Credit limit can turn an agent off, but enforcement is not immediate. Agent flows have separate capacity checks and are not stopped by the parent agent's limit.
Security
Provider keys off the workers
Yes
DocsYes: Models served by Microsoft
The harness calls the model for the agent and makers pick models from a list, so no provider key sits with agent logic; Azure AI Foundry models connect through a stored connection.
Sandbox with an egress allowlist
Conditional: Offline sandbox; URL filters
Code interpreter runs in an isolated sandbox with no network access and GitHub Copilot harness tasks run in a sandbox, with no egress allowlist documented for either; data policies can filter HTTP endpoints separately.
Audit and compliance
Tamper-evident audit trail
Conditional: Purview log, no hash chain
Admin, maker and user interactions with agents go to the Microsoft Purview unified audit log; no hash chaining or other tamper-evidence is documented.
Erasure by key
Conditional: Purview delete; env-level keys
Admins can find and delete a user's AI interaction data with Purview eDiscovery; customer-managed keys are set per environment, so there are no per-person keys.
Retention with legal hold
Yes: Purview retention and holds
Purview retention policies keep or delete Copilot Studio interactions for a set period, and eDiscovery holds keep them past that period.
Openness
Model provider choice
Yes
DocsConditional: No local models
Agents can use OpenAI, Anthropic, Mistral, xAI and Azure AI Foundry models, hosted by Microsoft or the vendor; no local model option is documented.
Where Microsoft Copilot Studio is stronger.
Inside Microsoft 365 and Teams
Agents publish to Teams, Microsoft 365 Copilot, websites and mobile apps, and approvals are answered in Teams or Outlook. Orchestrator Zero has a Teams plugin, tested only against a stand-in so far.
learn.microsoft.comHosted, with compliance attestations
A Microsoft-hosted service covered by Microsoft's compliance programme, including SOC 2 and ISO 27001.
learn.microsoft.comLow-code builder, 1,500+ connectors
Makers describe agents in plain language or build workflows on a drag-and-drop canvas, with over 1,500 prebuilt connectors plus MCP servers.
microsoft.comPurview covers agent conversations
Microsoft Purview audit, DLP, eDiscovery and retention apply to Copilot Studio agent interactions with the same tools used for the rest of Microsoft 365.
learn.microsoft.com
Full in Microsoft Copilot Studio, partial in oz0: Approvals in chat, Retention with legal hold.
Differences to examine.
Compare the scope, conditions and editions in the source notes.
- Any machine you own
- Linux, macOS and Windows
- Self-hosted control plane
- No inbound ports
- Fleet operations
- Tool snapshots
- Budgets that stop a run
- Tamper-evident audit trail
- Erasure by key
- Model provider choice
Using both
Copilot Studio connects to external agents over A2A and to MCP servers, so a Copilot Studio agent in Teams could hand work to an Orchestrator Zero agent over either.
Based on documentation; this pairing has not been tested.
Find your first task.
Explore an example or read the public Docs preview. Software access is coming soon.