Pyrana vs Microsoft Copilot Studio

Architecture

Copilot Studio is a SaaS studio on the Power Platform where makers build agents, workflows, and agent flows, then publish them to channels. Pyrana is a platform where the deliverable is an application: declared pages, operations, versioned outputs, and agents that belong to that application and inherit its rules. Copilot Studio starts from the conversation. Pyrana starts from the business record and the people who review it.

Microsoft Copilot Studio (formerly Power Virtual Agents) now describes three runtimes it calls harnesses. The standard harness runs rule-based agents built from topics and agent flows, where a request is matched to a designed conversation path. The GitHub Copilot harness takes a goal, breaks it into steps, calls connectors, knowledge, MCP servers, and connected agents, creates Office and PDF files, and runs each task in a sandbox. The Copilot chat harness extends Microsoft 365 Copilot Chat with an organization's knowledge. Microsoft also lists an app creation experience in Copilot Studio as preview.

Pyrana's architecture has seven shared layers: the harness, durable orchestration on Temporal, tool sources, tool approval policies, durable storage, the context engine, and the frontend surface layer. Identity, authorization, and audit sit under all of them. An application is one App configuration that names surfaces (pages), targets (operations), resources, agents, workflows, tool bindings, access profiles, and approval policies. Every call, whether it comes from a page, the copilot, the API, MCP, a schedule, or an external event, goes through the same eight-step gate.

Is Copilot Studio an application platform?

In Pyrana's view, Copilot Studio is an agent and automation platform with a growing app surface. Its center of gravity is the agent: what it says, which tools it calls, which channel it is published to. Pyrana's center of gravity is the application: what records exist, who may read, run, or approve, and which version of each output a page shows.

Context and knowledge

Copilot Studio agents answer from knowledge sources a maker connects, such as SharePoint sites, files, and connector data, and the GitHub Copilot harness adds skills and memory. Pyrana's cortIQ engine stores company knowledge as typed, classified Context Units with evidence passages and content-hash identities, and it records which units were retrieved, injected, and cited in every run.

The difference shows up when knowledge changes. In cortIQ, a unit's classification decides how it may change: absolute units never change automatically, regulated units wait for a person, tribal units are conflict-checked, and derived units update themselves. Changes supersede and never overwrite. Because citations are content-addressed, the exact business context behind any output is provable later. Copilot Studio shows the highest sensitivity label of SharePoint sources used in a response, which helps with data protection, and governance of the knowledge itself stays with the source system.

Agent capabilities

Both products run capable agents on frontier models. Copilot Studio offers child agents, connected agents, autonomous triggers, and on the GitHub Copilot harness, multi-step reasoning with retries. Pyrana runs agents inside workflows that fan out per entity and group, each agent restricted to the tools its job needs, and each publishing versioned outputs back to the application.

Copilot Studio can connect an agent to other Copilot Studio agents, to agents over the A2A protocol, and, in preview, to Microsoft Foundry agents, Fabric data agents, and agents built with the Microsoft 365 Agents SDK. Microsoft's guidance suggests splitting into connected agents when a main agent has more than 30 to 40 choices of action.

In Pyrana, agents do not write free-form queries. A tool holds the query; the agent passes the entity and the period. One workflow can dispatch dozens of specialized agents in parallel, each reading what siblings and prior runs published.

Copilot Studio or Microsoft Foundry?

Microsoft's Cloud Adoption Framework frames this as SaaS versus PaaS. Copilot Studio is low-code SaaS for business teams that want fast delivery, prebuilt connectors, and built-in responsible AI features. Microsoft Foundry is PaaS for developers who need model choice, hosted agents running their own code, multi-agent workflows, and private networking. Microsoft recommends one to two week prototypes on each and notes that organizations often use both. A Copilot Studio agent can call a Foundry agent (preview). Pyrana sits above both: it can call Foundry-hosted models and agents as tools while providing the application, authorization, and audit layer neither is designed to supply.

Governed actions and approvals

Copilot Studio handles approvals in agent flows, where multistage approvals combine human stages, AI stages, and conditions (preview). Pyrana handles approvals at the tool call: a policy over typed arguments decides which invocations need a person, then freezes the operation, exact arguments, scope, and evidence under a hash and queues it to a named lane.

Copilot Studio's multistage approvals let a flow route an expense above a threshold to a manager, add an AI screening stage, and collect responses through the Teams approvals app, Outlook, or Power Automate. Microsoft documents current limits: file attachments are not supported, the same approver cannot be assigned to two stages, and advanced approvals are not yet supported in application lifecycle management.

In Pyrana, approval is a property of the operation, not of one flow. Whether the request comes from a page, the copilot, an agent, or an external system, the same policy applies. Reviewer eligibility is checked at decision time, the frozen invocation is revalidated before dispatch, and dispatch is idempotent, so a retry reuses the receipt. A queued request is visibly different from a posted entry.

Building the application

Copilot Studio is built for makers: describe an agent in plain language, refine topics and tools on a canvas, test, and publish to channels. Pyrana is built for an application team: write one App configuration, configure agents in plain language within Agent Studio guardrails, and build the frontend experience, which is typically the main effort.

Copilot Studio's publishing reach is wide. One publish updates Teams and Microsoft Copilot, SharePoint, WhatsApp, websites, mobile apps, Facebook, and Azure Bot Service channels. Pyrana's reach is narrower by design: the App's own pages, the copilot over those pages, personal pages people ask the copilot to build, the API, and MCP. Pyrana's lifecycle separates push (compile an immutable version), activate (an audited pointer move by an App owner), and deploy (ship the frontend). Rollback is an activation of a prior version.

Governance and security

Copilot Studio inherits Power Platform and Microsoft 365 governance: data policies over connectors, knowledge, channels, and triggers; environment routing; Purview audit logs; Sentinel alerts; customer-managed keys; and, with Microsoft Agent 365, agent identities in Entra. Pyrana enforces authorization per call inside the application, in layers from tenant to approval lane.

Copilot Studio's controls govern what makers may build and which data an agent may touch. Pyrana's controls govern what each person or agent may do to each record. Access is layered: tenant, App membership, access profile (read, run, approve), scope entitlement (an entity, project, or queue), and approval lanes. Unauthorized things read as absent, not denied, and an execution row and audit record are written in one transaction before anything dispatches. Pyrana is SOC 2 aligned, supports Entra ID SSO, and runs on Azure.

Operations

Copilot Studio provides analytics, evaluations with test sets and graders, credit monitoring per agent, and admin inventory in the Power Platform admin center. Pyrana captures every run's traces, tokens, and tool errors as JSON through an administrative API, runs deterministic checks, then an LLM-as-judge stage in Agent Studio.

Durability differs in mechanism. Copilot Studio's runtime is managed by Microsoft. Pyrana's workflows run on Temporal workers, so a run waiting days for an approval survives a restart or deploy and resumes where it stopped.

Cost structure

Copilot Studio is consumption-priced in Copilot Credits. Microsoft lists a prepaid pack of 25,000 credits at $200 per month, pay-as-you-go through Azure, and a one-year prepurchase plan. Microsoft 365 Copilot licenses include internal agent use in Copilot Chat, Teams, and SharePoint. Pyrana is an enterprise platform subscription plus implementation.

Two Copilot Studio details matter for forecasting. Credits measure model tokens, tools, knowledge, and the harness itself, and unused pack credits do not carry over month to month. On the GitHub Copilot harness, building, previewing, testing, and generating evaluations all consume credits, while the standard harness bills after publish. For Pyrana, time to first application with clean data is typically about a week; a first engagement including SSO, access profiles, approval policy, and policy library runs about six weeks.

What it takes to ship the same application

Reference application: an approval-gated procurement request. A person or agent drafts a purchase request; amounts above a threshold need a finance approver; the request waits durably for the decision; everything is recorded.

Both columns describe documented features; neither has been benchmarked for build effort.

Using them together

Pyrana runs on Azure, uses Azure OpenAI and Entra ID, and can call Foundry-hosted models and agents, so it sits naturally in a Microsoft estate next to Copilot Studio. The cleanest pattern: Copilot Studio is the conversational front door in Teams and Microsoft 365 Copilot, and Pyrana is the governed application behind it.

• Copilot Studio to Pyrana over MCP. Each Pyrana App exposes an MCP server through which an agent works with the App as the user. A Copilot Studio agent can submit a procurement request or read a status; Pyrana's gate applies the user's profile and the approval policy.
• Shared identity. Both use Entra ID, so the person in Teams is the same principal Pyrana authorizes.
• Shared models and agents. Pyrana supports Azure OpenAI and can call Foundry agents, which Copilot Studio can also connect to.
• Outputs into Microsoft 365. Pyrana can deliver outputs to OneDrive and other targets the client accepts, where Copilot Studio agents can ground on them.

When not to choose Pyrana

• The deliverable is an FAQ, help desk, or simple intake agent in Teams, and nobody needs a separate application.
• Business makers must own and change the solution without an engineering team.
• Your Microsoft 365 Copilot licenses already cover the internal agent usage you need.
• You need one publish to reach many consumer channels such as WhatsApp, Facebook, and websites.
• Your process fits inside an agent flow with a standard approval, and record-level authorization lives elsewhere.