The agentic platform race in 2026 is no longer about who has the biggest LLM.
It is about who can ground an agent in clean enterprise data, hand it a tool palette wide enough to actually finish work, and prove to a CISO that the thing will not exfiltrate a quarter’s pipeline.
Salesforce Agentforce, Microsoft Copilot Studio, and ServiceNow Now Assist all claim the same outcome — autonomous work — from three very different starting points.
We have shipped agents on all three in the last year. None of them are interchangeable.
TL;DR pick
- You sell, market, or service from a Salesforce-anchored stack — Agentforce.
- Your work happens in Teams, Outlook, Excel, and SharePoint — Copilot Studio.
- Your business of record is ServiceNow workflows — Now Assist.
These are not interchangeable. The right choice is almost always “the platform that already owns your action surface.”
The mistake we see most often is buying the agent platform that won the demo rather than the one whose data the agent will actually need to act on. Demos are theater; production is plumbing.
The comparison at a glance
| Dimension | Agentforce | Copilot Studio | Now Assist |
|---|---|---|---|
| Reasoning engine | Atlas reasoning engine, multi-model via Vibes 2 | Azure OpenAI + orchestration over Microsoft 365 Graph | NowLLM plus BYO-LLM (Azure OpenAI, Anthropic via vault) |
| Grounding | Data Cloud (Data 360) zero-copy + CRM records | Microsoft Graph + Dataverse + SharePoint embeddings | Now Platform tables + Knowledge + CMDB |
| Action ecosystem | AgentExchange (1,000+ MCP servers, ISV actions) | Connectors (1,400+) + plugins + Power Platform | Workflow Studio + IntegrationHub spokes |
| Authoring surface | Agent Builder, conversational workspace | Copilot Studio low-code + pro-code via Power Fx | Now Assist Skill Kit + Flow Designer |
| Governance | Einstein Trust Layer, Agent Data Access Scopes | Purview, Entra ID, sensitivity labels | AI Control Tower, ACL inheritance, policy-as-code |
| Cost model | Per-conversation + platform license | Per-user Copilot license + per-message consumption | Pro Plus / Enterprise Plus subscription, message packs |
| Ideal customer | Revenue + service orgs on Salesforce | M365 enterprises, knowledge-worker heavy | ITSM, ESM, ops-heavy enterprises |
Reasoning engine: same words, different physics
Agentforce runs on the Atlas reasoning engine.
It is a planner-executor pattern with built-in reflection loops and topic-bound tools.
Atlas is opinionated — topics scope the agent’s job, actions define what it can do, and the runtime decides when to call which.
Vibes 2 lets you swap the underlying model per topic (Anthropic Claude, OpenAI, Google Gemini, or Salesforce-hosted xGen).
The practical effect is that Agentforce agents behave more predictably across builds. Two agents with the same topics and actions answer similarly even when the model changes underneath.
Copilot Studio is more like an orchestration shell over Azure OpenAI.
You build topics in a low-code canvas that compile to a YAML graph; the runtime turns user intent into plugin and connector calls.
The reasoning is largely model-side, not platform-side, which makes it flexible but less predictable when topics overlap.
Now Assist sits closer to Agentforce in shape.
Skills are explicitly named, scoped to tables and roles, and routed by an intent classifier.
BYO-LLM is production-ready in 2026 via the vault, but the platform’s value is the grounding into Now Platform records, not the model itself.
For workflows that have to act on records — file a change, update a CI, escalate an incident — Now Assist’s grounding is the differentiator.
Grounding quality decides the agent
Every vendor talks about “grounding.” The differences are about what the agent can see without leaving the platform.
Agentforce grounds on Data 360 (formerly Data Cloud), with zero-copy lake support that lets Snowflake, BigQuery, Databricks, and Iceberg-backed lakes register as data lake objects. The CRM record graph is first-class.
Copilot Studio grounds on Microsoft Graph (mail, calendar, documents, chats, meetings), Dataverse, and SharePoint embeddings. For knowledge-worker tasks, the surface is the surface — almost nothing is outside it.
Now Assist grounds on Now Platform tables, Knowledge articles, the CMDB, and any custom table you have built. The grounding inherits ACLs, so a user who cannot see a record cannot ask the agent about it.
Action ecosystem: what can the agent actually do
This is the unsexy variable that decides project outcomes. An agent that cannot file a case, update an opportunity, or open a change request is a chatbot.
Agentforce ships with native CRM actions (lead routing, case triage, opportunity updates) plus AgentExchange — over a thousand listed MCP servers and packaged actions as of April 2026.
The MCP standard means even custom internal tools light up if you wrap them once.
Copilot Studio leverages the 1,400+ Power Platform connector library, plus first-party Microsoft Graph actions (mail, calendar, files, Teams).
Custom plugins are authored as OpenAPI or Power Fx. The ceiling is high; the floor is “if it is Microsoft, it works on day one.”
Now Assist uses Workflow Studio actions and IntegrationHub spokes.
Tighter ecosystem (hundreds, not thousands) but each action is governed by ACLs, so the action surface inherits your security model rather than fighting it.
Integration surface and a small code lens
Most teams will end up cross-wiring all three. Here is the rough shape of what each agent calls when it needs to talk to a foreign system.
# Conceptual sketch — not runnable
agentforce_action:
type: external_service
named_credential: NOW_INSTANCE
endpoint: /api/now/table/incident
invocable: true
copilot_studio_plugin:
schema: openapi-3.0
auth: entra_oauth2
operationId: createIncident
host: instance.service-now.com
now_assist_spoke:
type: integrationhub
connection: outbound_rest
scope: x_company_app
acl_required: trueThree different mental models. Same outcome.
The deeper question is which platform owns the records being touched. Whoever owns the records should own the agent; the others should be tools, not orchestrators.
Governance: where buyers actually argue
Agentforce’s Einstein Trust Layer is the most marketed.
Dynamic grounding, PII masking, prompt defense, audit trails, and zero data retention with model providers.
Agent Data Access Scopes (rolled out late 2025) tie tool calls back to user permissions on a per-record basis.
Copilot Studio governance leans on Microsoft Purview for DLP and sensitivity labels, Entra ID for identity, and admin center for tenant policy.
Strong because it inherits your existing M365 controls; weak because those controls were not originally designed for autonomous agents and the policy surface is still consolidating.
Now Assist’s AI Control Tower is the dark-horse story.
Policy-as-code, prompt-injection defense at the platform layer, message budget controls, and the cleanest “this agent acted on behalf of this user against this record” audit trail of the three.
If your CISO is the deciding vote, Now Assist usually wins the demo.
Pricing model: don’t anchor on sticker
All three vendors are still actively re-pricing in 2026. The structural differences matter more than the headline numbers.
Agentforce is largely per-conversation consumption layered on top of a platform license.
It rewards bursty, high-value workflows (sales prospecting, service triage) and punishes always-on assistant patterns.
Copilot Studio is per-user Copilot license plus message capacity.
Predictable, but the per-user model means you over-pay for occasional users and the message overage is easy to miss in budgeting.
Now Assist is bundled into ServiceNow’s Pro Plus and Enterprise Plus SKUs with message packs for overflow.
Cleanest for finance teams, least flexible for “let’s just try this with one team.”
Model 24-month cost across all three at your real volume. Sticker pricing changes; structural pricing rarely does.
Authoring and admin UX
Agentforce Agent Builder has converged on a conversational workspace with side-panel previews.
Builders can clone topics, ship to sandboxes, and run the regression suite without leaving the canvas. Pleasant once you learn the topic-action-instruction trio.
Copilot Studio is the most accessible — a business analyst with Power Platform experience is productive in a week.
Trade-off: it is easier to ship something subtly wrong, and debugging multi-turn flows still requires Power Fx fluency.
Now Assist Skill Kit is the most explicit and the steepest.
You define inputs, outputs, prompts, tools, and routing as artifacts. Great for engineering-led teams; intimidating for a citizen developer pilot.
End-user UX where it differentiates
For end-users, Agentforce shows up most often as embedded copilots on Lightning record pages and the Service Console. Service agents can co-pilot mid-case; sales reps can ask the agent to draft outreach against the current account.
Copilot Studio’s end-user surface is wherever the worker already is — Teams, Outlook, Microsoft 365 Copilot. Adoption follows the work surface; you do not have to teach the workforce a new tab.
Now Assist shows up in the ServiceNow portal, in the Now mobile app, and in Slack and Teams via the platform’s chat surfaces. For the population that uses ServiceNow daily, this is the right shape; for the population that opens ServiceNow twice a quarter, the surface matters less.
Ecosystem and ISV motion
Agentforce’s AgentExchange is the loudest, with a 50M USD ISV initiative and a partner monetization model that pays per-conversation revenue share. Distribution is the moat.
Copilot Studio’s ecosystem is Microsoft’s partner network, which is enormous but oriented around Dynamics 365, Power Platform, and M365 — agentic-specific marketplace momentum is younger.
Now Assist ISVs build on the Now Store with the same per-instance app model that has worked since the New York release. Quieter, but adoption by existing ServiceNow partners is high.
Observability and AI Ops
Agentforce ships an agent regression suite, conversation observability, and evaluation runs as first-class platform features. You can re-play production conversations against a candidate build and see deltas.
Copilot Studio observability uses Azure Monitor, Application Insights, and Power Platform analytics. Mature infrastructure tooling, but the agent-specific UX is more scattered.
Now Assist observability lives in the AI Control Tower — message volume, success rates, escalation patterns, and policy violations all in one place. The cleanest of the three for an SRE-shaped reader.
Who should pick which
- Salesforce-anchored revenue org with a Data Cloud footprint — Agentforce. The grounding story is hard to beat when the records already live in Data 360.
- Microsoft 365 enterprise with knowledge workers as the persona — Copilot Studio. Adoption follows the work surface, and the work surface is already Teams and Outlook.
- Operational backbone runs on ServiceNow — Now Assist. Anything else creates a second source of truth, and the governance story is sharper.
- Hybrid shop with no dominant platform — start with the workflow that has the clearest ROI and pick the agent that lives closest to that workflow. Do not buy the all-platform vision; buy the next 90 days.
- Heavily regulated (finance, public sector, life sciences) — Now Assist or Agentforce, with a hard pass on consumer-grade plugins. Both have audit and trust stories that survive procurement; Copilot Studio is improving but lags here.
- AI-research-forward engineering team — Copilot Studio for the model flexibility via Azure AI Foundry; Agentforce for the action ecosystem; Now Assist for governance maturity.
The pick
If we had to recommend one without knowing the buyer, it would be Agentforce — the action ecosystem, MCP support, and reasoning engine are the most mature in 2026.
But that recommendation falls apart the moment you tell us where your records actually live.
The honest answer is the platform that already owns your data and your workflows. Pay the integration tax once with that platform; do not pay it three times trying to make every agent talk to every system.
For related reading on the underlying patterns, see our Salesforce vs ServiceNow for ITSM breakdown and the Salesforce vs Dynamics 365 comparison.
