For a company that already runs Salesforce, the choice between Salesforce’s own AI and Microsoft Copilot depends on where the work is done. Which demo looked better does not settle it. If the task changes Salesforce records (a case, an opportunity, a work order), start with Agentforce, which works inside the org. If the task is email, meetings and documents, start with Copilot and connect it to Salesforce. Many companies end up with both. Then the real decision is who governs each one.
Take a sales team that logs opportunities in Salesforce but writes every follow-up in Outlook and holds client calls in Teams. Microsoft’s Sales agent connects CRM data from Dynamics 365 Sales or Salesforce. It drafts emails and follow-ups in Outlook and captures insights and action items in Teams meetings. The service team next door resolves cases in Salesforce all day. Salesforce’s own customer service demos for Agentforce show exactly that work: resolving an open case, drafting a follow-up email, escalating to a specialist. One company gets two answers because its work happens in two places.
What does each one offer that the other lacks?
Salesforce’s AI starts from the record. Salesforce describes purpose-built agents for sales, service, HR and more, with job-specific subagents, prebuilt actions and Salesforce context already in place. It presents Agentforce Coworker as working within the existing Salesforce permissions and business rules. Its pricing page also sells customer-facing agents, billed per conversation or in Flex Credits.
Copilot starts from the Microsoft 365 day. With the Premium add-on licence, Copilot grounds its answers in web and work data (Microsoft Graph and Work IQ) and gives priority access to Copilot in Word, Excel, PowerPoint and OneNote.
Next, separate what works today from what is only announced. Salesforce’s AIforce page presents Claudeforce, a prebuilt Salesforce MCP server with 37 ready-to-use sales skills inside Claude. It also presents Slackforce and a Headless Toolkit, next to newsroom items that “unveil” and “announce” them. The page does not say which of them are available today. On the Microsoft side, app creation in Copilot Studio is marked as preview, and Microsoft notes that Copilot might not be accessible in certain markets. Before a programme plan depends on any of these, sort them as described in Dreamforce 2026: what is available, what is announced.
When does Copilot fit better?
Copilot fits better in four situations.
- The work happens in Outlook, Teams, Word and Excel, and Salesforce is where the record lives but not where people work. Sales agent brings the CRM into those tools, so sellers do not have to change where they work.
- Many of the people involved never open Salesforce: finance, management, support functions. They already use Microsoft 365, and Copilot is sold as an add-on to the plan they have.
- The process crosses several systems. Copilot Studio connects to other data sources through prebuilt or custom connectors and publishes agents to Teams, Microsoft Copilot, websites and mobile apps.
- The company already runs its access reviews and compliance in Microsoft 365 and wants AI under the same controls.
Copilot fits worse when the agent has to update a case, change an opportunity stage or answer a customer from the service history. Reading Salesforce from Outlook is a different job from acting in the org.
How does the deployment effort differ?
The licence models start from different places. Copilot is an add-on that requires a qualifying Microsoft 365 plan. Microsoft’s list includes Business Basic, Business Standard, Business Premium, E3 and E5, and Microsoft 365 E7 includes Copilot. Salesforce’s pricing page lists:
- Agentforce add-ons for Sales, Service and Field Service and Operations at $125 per user per month
- an Agentforce User License at $5 per user per month, which requires Flex Credits
- Flex Credits at $500 per 100k credits
- conversations at $2 each
The page says it is for information only and subject to change. Both vendors bill part of the usage as it happens, and Microsoft bills Copilot Cowork that way too. Name someone to own the consumption report, or the first invoice will be the first time anyone reviews usage.
Admin work splits by vendor. Installing Sales agent requires a Microsoft 365 admin role. Data sharing with a third-party CRM stays off until administrators and users consent to connect their Microsoft account to their CRM account. So the Salesforce link needs three things: a Microsoft admin, a Salesforce-side decision on what users may read, and a consent step in the rollout plan. The Salesforce admin sets up Agentforce inside the org.
On both platforms, data access and governance follow user permissions. Microsoft states that Copilot access is scoped by user permissions, and Salesforce says the same of Agentforce Coworker. A field shared too widely becomes an answer shared too widely: a salary field visible to all users can turn up in anyone’s answer. Clean up the sharing model before you switch on either one. For Agentforce, the rules for changes after go-live belong in a written agreement, covered in Agentforce operating model: who owns changes after go-live.
Training differs too. Copilot users learn in the Office apps they already know. Agentforce users learn on the Salesforce screens they already use. The admin is the harder gap. When one admin runs two AI consoles, often neither one ends up governed.
Which one is more customisable?
Each one can be customised, in a different direction. Copilot Studio is a graphical, low-code studio for agents and workflows. It has prebuilt or custom connectors, and its workflows include built-in testing and human-in-the-loop controls. It reaches wide: many systems, many channels. Salesforce’s tooling reaches deep into the CRM. Agentforce Builder, Prompt Builder and Agent Script are in the free Foundations tier. Salesforce adds Agent Optimizer, plus Multi-Agent Orchestration to coordinate specialised agents across customer journeys.
Actions on Salesforce records point to Agentforce. A workflow that spans Microsoft 365 and other systems points to Copilot Studio. Every customisation is configuration that someone owns, tests and may switch off. A pilot on either side should end in a go, fix-and-retest or stop decision, as set out in Agentforce PoC to production: turn the demo into a decision.
Which one suits a small company?
A small company usually has one admin, sometimes part-time, and cannot run two AI platforms well. Pick the one that sits where staff spend the day, and keep the other for later.
Both vendors let a small team start small. Salesforce Foundations lists Agentforce Builder, Prompt Builder, Agent Script and Agentforce Coworker at $0, to get started “for any use case”. Microsoft’s basic Copilot Chat licence works with web data only. For Copilot Business, Microsoft lists small-business plans: Business Basic, Standard and Premium, Apps for Business, and Teams Essentials. Start with one use case, one owner and a short test set, then decide on paid licences. Run the path below for each use case, not once for the whole company.