Microsoft 365 Copilot vs Salesforce Agentforce

Quick answer: where does the work finish?

Write down the task before the product. If a sales manager wants a summary of last week's Teams calls and a draft email in Outlook, that work finishes in Microsoft 365 and Copilot is the natural candidate. If a service team wants an agent to look up an order, update a case and reply to a customer on the website, the work finishes in Salesforce, and that is Agentforce's ground.

They overlap at the edges. Copilot can reach external data through connectors and agents built in Copilot Studio; Agentforce has an employee-facing Coworker licence that searches company data. We would still start each in its home system. We checked Microsoft's enterprise pricing page and Salesforce's Agentforce pricing page on 10 November 2026; security details come from our dated reviews. We haven't run either in production.

Pricing models: a seat versus a meter

Fixed per-user costs and consumption sit on different budget lines

Copilot is easy to forecast for the core seat: $30 per user per month, paid yearly, with the annual subscription renewing automatically. It isn't the whole bill. You need a qualifying Microsoft 365 plan for each user, and Microsoft says agents are priced on a metered basis and need an Azure subscription. Our review from 26 October also recorded a $31.50 monthly-payment option on an annual commitment and a separate Copilot Business add-on for organizations up to 300 users.

Agentforce is priced by what the agents do. A pack of 100,000 Flex Credits costs $500; Salesforce's examples count a standard action as 20 credits ($0.10) and a voice action as 30 ($0.15). Its own worked example of 100 service users handling three cases a day for 20 days comes to $1,800 a month, and Salesforce notes that such examples exclude other costs such as Data 360 credits. Per-user options exist too: a $5 Agentforce User License that still needs Flex Credits, a $50 Coworker licence with searches included, $125 add-ons for Sales, Service and Field Service, $150 Industries add-ons and Max Edition from $550 with 2.75 million Flex Credits per org a year.

Who should pick which

A professional-services firm of 60 people that lives in Outlook, Word and Teams and keeps clients in a small CRM gets more from Copilot. The work it wants help with is drafting, summarising and finding files, and the cost is a known seat price. An e-commerce company with a Service Cloud contact centre, by contrast, is buying deflected or faster cases, which is what Agentforce's consumption pricing measures.

Companies on both platforms shouldn't treat this as either/or. Copilot for staff productivity and Agentforce for customer-facing service matches how each vendor describes its own product. The decision is then about budget order and which pilot has the clearer owner.

Data access and governance

Copilot surfaces only what the user can already open under Microsoft 365 permissions, so messy SharePoint sharing becomes visible quickly. Microsoft says prompts, responses and Graph data aren't used to train foundation models, and Copilot is an EU Data Boundary service, though our review noted that Anthropic-provided models were excluded from that boundary.

Agentforce runs through the Einstein Trust Layer, which Salesforce describes as zero data retention with third-party LLM providers plus PII masking. EU residency means the paid Hyperforce Operating Zone, and our review couldn't confirm Agentforce's authorisation there from the pages we read. In both cases, test with an ordinary user's permissions, not an administrator's.

Migration and coexistence notes

There's nothing to migrate between the two; they don't store the same records. The practical work is integration: if Agentforce should use documents kept in SharePoint, or Copilot should see Salesforce data, check which connector is supported, which licence it needs and whose permissions apply. A connector existing isn't approval to use it.

Run separate two-week pilots with named owners. For Copilot, pick a group of 10 to 20 heavy Office users and record accepted drafts and time spent checking. For Agentforce, pick one intent, track actions and credits consumed per completed request, and compare with the human handling cost. Expand whichever shows accepted work at a cost you can explain.