Comparison

Dust vs Copilot Studio vs Atipol: Pricing, SSO, Logs

· founder of ETCSEC · updated November 18, 2026 · 8 min
Illustration of a robot comparing three governance approaches side by side.
The short answer

Read only each vendor's own documentation, not its marketing page, and Dust, Copilot Studio, and Atipol turn out to solve three different shapes of the same governance problem: a hosted workspace, a Microsoft 365 control plane, and a cross-client ticket and audit layer. Entry price, SSO, and audit logging sit at different tiers for each one, which is exactly where the comparison below starts.

Three tools, three different shapes of the same problem

A PME comparing Dust, Microsoft Copilot Studio, and Atipol to govern its AI agents usually gets three vendor pages that each describe a different product shape as if it were the obvious default. Dust is a hosted workspace where a team builds agents against connected company data and chat clients. Copilot Studio is Microsoft's agent builder and governance layer for anything that lives inside Microsoft 365. Atipol is a governance layer for agents working across whichever MCP client a team already uses, Claude Code, Codex, Cursor, or others, rather than a workspace that hosts the agents itself.

These three governance shapes break down as follows:

DustCopilot StudioAtipol
Entry price 24 €/seat/month (Pro, billed yearly) $30/user/month (M365 Copilot add-on) 19 €/user/month (Pro, including tax)
SSO Included from the Business plan Via Microsoft Entra, included Planned for Enterprise, not yet available
Audit log Enterprise plan only Purview audit logs, Sentinel monitoring Every call logged to agent, ticket, result
Where agents run Dust's own hosted workspace and connectors Power Platform environments, Microsoft 365 channels Any MCP client: Claude Code, Codex, Cursor, others

None of that difference shows up clearly from reading one vendor's pricing page against another's feature list, since each page is written to make its own shape look complete. What follows uses only each vendor's own documentation, dated, to describe what each one actually governs, what it costs at each tier, and where a team's actual agents decide which shape fits.

What Dust documents

Dust's own pricing page, verified 11 November 2026, describes one plan named Business, for teams up to 100 people, with Free, Pro, and Max as seat types inside it: Free gives 500 credits for the lifetime of the seat, Pro gives 8,000 credits per seat per month at 24 euros billed yearly or 30 euros billed monthly, and Max gives 40,000 credits per seat per month at 120 euros billed yearly or 150 euros billed monthly. A separate Enterprise plan, reached only through sales, adds workspace-pooled credits and volume pricing instead of per-seat credit caps.

Governance features are split the same way the page splits plans. Single sign-on with Okta, Microsoft Entra ID, or JumpCloud is listed under the Business plan. SCIM provisioning, audit logs, custom data retention, and custom legal terms such as a tailored MSA or DPA are listed only under Enterprise. US and EU data residency is listed under Business, and Enterprise repeats it alongside single-tenant deployment, a stronger isolation guarantee than the shared Business plan offers.

None of this is unusual for a per-seat SaaS pricing structure; it is the same pattern Microsoft applies to Copilot Studio and Atipol applies to its own plans, where the entry tier buys access and a higher tier buys the audit and compliance features. What changes between vendors is exactly where that line sits, which is why reading the line rather than the plan name is what actually tells a PME what a given monthly price includes.

What Copilot Studio documents

Copilot Studio's own documentation, covered in more detail in a separate comparison on this blog, governs agents built inside Microsoft 365 through data policies configured in the Power Platform admin center, updated 22 October 2026: enforced in real time since early 2025, these policies can require Microsoft Entra authentication, block connectors, HTTP requests, Azure Bot Service skills, specific publishing channels, and event triggers.

Microsoft Agent 365, documented 5 November 2026, adds a control plane that represents Copilot Studio agents as Entra identities with Conditional Access and role-based access controls, with maker audit logs in Microsoft Purview and monitoring through Microsoft Sentinel. Pricing starts at 30 US dollars per user per month for the Microsoft 365 Copilot add-on, which covers internal use; publishing to external channels or letting unlicensed users interact with an agent requires a standalone Copilot Studio license billed through 25,000-credit capacity packs at 200 US dollars per month.

What Atipol documents

Atipol works as a governance layer rather than a hosting workspace: each agent is declared under one person's agent lead, which never holds more rights than that person, and each tool a declared agent can call carries one of three states, allowed, subject to approval, or denied, set tool by tool rather than as one blanket grant per agent.

Every call an agent makes is logged and linked to that agent, the ticket it was working on, and the result, along with any approval granted or denied, which is the audit record a DSI or a PME owner pulls up when asked what an agent did. Pricing runs Free, Pro at 19 euros per user per month including tax, Business at 39 euros, and Enterprise by quote; Atipol does not detect shadow AI on its own, single sign-on with SAML or OIDC is planned for Enterprise rather than available today, and self-hosting is planned rather than shipped.

Three vendors, the same dimensions

The table below applies the same six questions to each vendor's own documentation; a blank or a qualifier means the page itself did not make a stronger claim, not that the feature is assumed absent.

DimensionDustCopilot StudioAtipol
Entry price24 €/seat/month (Pro, billed yearly)$30/user/month (M365 Copilot add-on)19 €/user/month (Pro, including tax)
SSOIncluded from the Business planVia Microsoft Entra, includedPlanned for Enterprise, not yet available
Audit log / SCIMEnterprise plan onlyPurview audit logs, Sentinel monitoringEvery call logged to agent, ticket, result
Data residencyUS or EU (Business); single-tenant (Enterprise)Within Microsoft's own geographic availabilityPer-organization encryption, hardware master key
Where agents runDust's own hosted workspace and connectorsPower Platform environments, Microsoft 365 channelsAny MCP client: Claude Code, Codex, Cursor, others
Self-hostingNot offeredNot applicable (Microsoft-hosted service)Planned, not yet available

Sovereignty: what the residency claims do and do not mean

Residency claims are easy to state and easy to misread. Copilot Studio is entirely a Microsoft service, so its geographic options follow Microsoft's own documented availability regions; there is no separate vendor layer to evaluate. Dust states US and EU data residency under its Business plan without naming the underlying cloud infrastructure on its pricing page, which leaves that detail to Dust's own separate documentation rather than something this comparison can confirm from the pricing page alone.

Atipol encrypts your data per organization, under a hardware master key; every access is checked against your rights and logged. Keeping a key, and the data it protects, inside a named EU region is a real control, but it does not make that data immune to a request made under a law that reaches the cloud provider operating the infrastructure, regardless of the region the data physically sits in. A PME evaluating any of these three tools on sovereignty should ask the same question of all three: which company actually operates the infrastructure holding the key, not only which region the page names.

This is not a criticism specific to any one vendor; it is a property of relying on a major cloud provider's infrastructure at all, which every vendor compared here does in some form. The honest answer for a PME is not to expect immunity from any of the three, but to know, for each one, exactly which company holds the key before deciding how much weight the region name alone should carry.

When each is the right choice

A team already inside Microsoft 365, publishing agents to Teams or SharePoint, with Entra and Purview already in place for everything else, gets the most out of Copilot Studio without adding a second governance system, the same conclusion this blog's dedicated Copilot Studio comparison reaches in more detail.

A team under 100 people that wants a single hosted workspace connecting chat, documents, and a shared set of agents, without standing up its own governance layer across multiple clients, fits the shape Dust's Business plan describes, with the understanding that audit logs, SCIM, and custom legal terms sit behind the separate Enterprise plan rather than inside Business.

A team running agents across more than one client, a coding agent in one tool, a support agent in another, with tickets, acceptance criteria, and an audit log that has to look the same regardless of which client ran the agent, is the shape Atipol describes, and the one neither Dust's hosted workspace nor Copilot Studio's Microsoft 365 boundary was built to cover on its own.

None of these three conclusions is permanent; a team that starts inside Microsoft 365 and later adds a non-Microsoft coding agent, or a team that outgrows Dust's 100-person Business plan, moves the right answer along with it, which is why the dimension that changed, not the vendor name, is what should trigger re-evaluating the choice.

Building the comparison into a decision

The permission model and audit log behind Atipol's numbers above, including how an MCP server gets reviewed before an agent connects to it, are covered at atipol.ai/agentic-ai-blog/mcp-security. How that model's per-user pricing translates into a cost per accepted delivery, the number that actually matters once agents are running in production, is covered at atipol.ai/agentic-ai-blog/ai-agent-costs, and the full comparison across all three tools, kept current, is at atipol.ai/comparison.

Frequently asked questions

What is the main structural difference between Dust, Copilot Studio, and Atipol?

Dust is a hosted workspace where a team builds and runs agents against connected data and chat clients. Copilot Studio is Microsoft's own agent builder and governance layer for Microsoft 365. Atipol is a governance layer for agents that already run in whichever MCP client a team uses, rather than a workspace that hosts the agents itself.

Which plan do I need for audit logs and SCIM with Dust or Copilot Studio?

Dust's own pricing page lists SCIM provisioning, audit logs, and custom data retention only under its Enterprise plan, not under the Free, Pro, or Max seat types inside the Business plan. Copilot Studio's audit logging, through Microsoft Purview and Microsoft Sentinel, is documented as part of its standard security and governance controls rather than gated to a separate tier.

Does keeping encryption keys in a named EU region make agent data immune to foreign law?

No. Atipol encrypts your data per organization under a hardware master key, with every access checked and logged; keeping a key in a named EU region is a real control, but it does not make the data immune to a legal request that reaches the company operating that infrastructure, regardless of the region named.

Sources

Try it on a real project

The public demo shows a fictional organization at work, no account needed. The free plan includes a project, three agents and an agent lead.