If your sellers work in Outlook and Teams and your pipeline lives in Salesforce, Copilotforce lets Microsoft Copilot read and update those records under each seller's existing Salesforce permissions. It asks the seller to confirm every write. The catch is that the plugin is a public preview with no published price or license terms. It also lands in a budget line many Salesforce shops already pay for through Agentforce. Pilot it now, and keep both renewals open until the general availability terms are written down.
Copilotforce is the name Microsoft and Salesforce gave to the partnership they announced at Microsoft Ignite on November 17, 2026. It has four parts, and they ship at four different maturity levels. Your rollout plan should treat them separately.
What Is Actually Available Today?
Only one piece of Copilotforce is generally available: federation that lets Salesforce Data 360 query supported Microsoft OneLake data without moving it. The rest is preview or pilot, per Microsoft's release:
| Component | Status on November 17, 2026 | What it does |
|---|---|---|
| Salesforce in Copilot | Public preview | A plugin with 38+ prebuilt sales skills inside Microsoft Copilot |
| Data federation (OneLake into Data 360) | Generally available | Query supported OneLake data from Data 360 without copying it |
| Data 360 shortcut (Data 360 into OneLake) | Public preview | Share curated Data 360 data into OneLake for analytics and AI |
| Sales Cloud in Teams | Pilot with enterprise customers | Pipeline, quota progress, deal alerts and briefings inside Teams; open beta planned "later this year" |
The skills include Pipeline Review, Close Planning, Deal Review, Customer Health, Renewal Radar and Call Follow-Up. Sellers reach Salesforce through what the release calls "authenticated Salesforce MCP access." MCP (Model Context Protocol) is an open standard that lets an AI assistant call another system's tools and data through a defined interface. In this case Salesforce decides what data the assistant sees and which actions it may take, and Microsoft applies its own compliance controls to the communications and documents involved.
The release has no line on price. Futurum's analysis confirms the announcement materials "did not include pricing or licensing terms" for Salesforce in Copilot, and it lists whether the plugin will need Agentforce credits or new fees at GA as an open question. Microsoft's own Ignite ecosystem post says Microsoft will "partner with Salesforce to bring Salesforce to Copilot" and gives no date or GA status.
How Is This Different From the Salesforce Connector You May Already Run?
The difference is live access with write actions instead of a read-only index, and that changes your permissions risk. Microsoft already ships a Salesforce CRM Copilot connector that crawls Account, Contact, Opportunity, Lead, Case, Event, Task and Campaign records into Microsoft 365 so Copilot can search them. Its documentation lists limits that matter here:
- An admin can set indexed data to "Everyone," which makes it searchable by any user in the tenant.
- If you opt in to indexing fields restricted by field-level security, the connector "doesn't enforce Salesforce FLS when showing results."
- Permission group changes sync only on full crawls, and full crawls consume Salesforce API quota.
Copilotforce works the other way. The release says Salesforce "controls data access and governs supported business actions," that sellers act "within their existing Salesforce permissions," that writebacks "require explicit user confirmation," and that they must pass your existing Salesforce validation rules. Read literally, a seller sees in Copilot what they can see in Salesforce at the moment they ask, and nothing goes back without a click and a rule check.
That's the better design. It also means your Salesforce profiles, permission sets and validation rules now gate an assistant that runs inside your email client. Many of those rules were written with a person clicking through Lightning in mind. If a validation rule is the only thing stopping a bad stage change today, it is now the only thing stopping Copilot too. Salesforce's own agent surfaces have shown how quickly an injected instruction can reach CRM data: the SalesBleed web-to-lead injection turned a public form into an Agentforce leak.
Who Wins, and What Microsoft Sold the Same Day
Each vendor gets something it couldn't get alone, and Microsoft keeps a migration offer on the table. Futurum's read is that Salesforce gains reach into Outlook, Teams and Word while Microsoft gains the customer records that make Copilot useful for sales, with Sales Cloud staying the system of record. That's the strongest case for the deal, and for a company standardized on both vendors it's a fair one. Futurum also calls the trip out of Microsoft 365 to check an account or log a call a common cause of stale CRM data, and the plugin removes that trip.
Read the rest of Ignite, though. On the same day, Microsoft made Dynamics 365 in Copilot generally available with Sales and Customer Service plugins and more than 57 skills, according to Futurum and CX Today. It also extended Dynamics 365 Activate, its tool for moving customers off Salesforce, to SAP ECC in private preview. When CIO.com covered Activate in September, it was a public preview that analyzes a company's Salesforce data, customizations and dependencies to plan a migration, and an analyst cited there called it "a migration accelerator rather than a migration autopilot."
So the Salesforce plugin is a preview with 38+ skills, sitting in the same Copilot surface as a GA Dynamics plugin with more than 57. Microsoft gets Copilot revenue whichever CRM you run. Satya Nadella's own line, quoted by CX Today, was "it is not just Dynamics." Microsoft is pitching Copilot as the place sellers work and Dynamics as a CRM that is already wired into it. If your Salesforce renewal is within a year, expect Microsoft to bring that comparison to the table.
Salesforce, for its part, is now in several assistants at once. At Dreamforce it launched Salesforce in Claude as a prebuilt MCP server with 37 sales skills, "available to all customers in beta," and a release-wide note that "pricing and packaging are subject to change." We covered how that one ended up with two separate meters. Salesforce is also selling its own assistant into Teams: the Agentforce Coworker page lists a $50 per user per month license and says you can "use Agentforce Coworker in Salesforce, Microsoft Teams, and on mobile."
Where Could You End Up Paying Twice?
The likeliest double payment is a seller who holds a Microsoft 365 Copilot seat and a Salesforce AI seat and uses only one of them. List prices make the stakes concrete. Microsoft 365 Copilot is $30 per user per month on annual billing, on top of a qualifying Microsoft 365 license. On Salesforce's Sales Cloud pricing page, Agentforce for Sales starts at $125 per user per month as an add-on, and the $550 Max edition includes Agentforce for Sales and Agentforce Coworker. Coworker on its own is $50.
None of those numbers includes Salesforce in Copilot, because nobody has priced it. Futurum flags the renewal problem directly: a Salesforce seat used mainly to feed another vendor's assistant "is harder to justify at renewal," and its 2H 2026 survey found 32.7% of buyers' preferred vendors still sell generative AI as a per-seat add-on while 57.7% of buyers paying for AI add-ons would rather pay by consumption or outcome. The analyst's summary is blunt: "the hidden cost is the interface."
Microsoft is also moving agent work off the seat. We reported in October that its new Copilot bills Autopilot outside the $30 seat in Copilot Credits. If Salesforce in Copilot reaches GA with any metered component on either side, a seller's pipeline review could draw on two meters plus two seats.
Accenture is the reference customer worth watching. It is design partner and "customer zero," with 55,000 Salesforce users inside a company with more than 740,000 people on Copilot, per the release. Neither company has published results from that rollout yet.
What Sales Ops and Microsoft 365 Admins Should Do Now
Run a scoped pilot with measured baselines and get the commercial questions answered in writing before either renewal.
This Week:
- Pull three license lists and join them on email: Microsoft 365 Copilot holders, Salesforce users on Agentforce for Sales or the Max edition, and Agentforce Coworker holders. The overlap is your double-paid population and your pilot pool.
- Open your existing Salesforce CRM Copilot connector settings. If access is set to "Everyone" or FLS-restricted fields are opted in, fix that first, because a pilot will put more sellers in front of Copilot answers.
- Send one written question to your Salesforce account executive and one to your Microsoft account team: "At general availability, which licenses does Salesforce in Copilot require, and does it consume Flex Credits, Copilot Credits or Salesforce API limits?" Ask each reply to cite the governing document.
This Month:
- Pick 25 to 50 sellers from the overlap pool and record baselines before turning anything on: time from meeting to logged follow-up, share of opportunities updated in the last 7 days, and forecast accuracy for the quarter. Futurum recommends judging the plugin on exactly this kind of measured result, set during the pilot.
- Review the validation rules and field permissions on Opportunity, Account and Task with your Salesforce admin. Add rules for any stage or amount change you would not want made from a chat window, since writeback respects only what those rules enforce.
- Run the same seller tasks through Agentforce Coworker in Teams if you already license it. If you are weighing a CRM move, run them through Dynamics 365 in Copilot too. One week of side-by-side use tells you which assistant your sellers actually open.
- Before you use the GA OneLake federation, have your data governance lead decide which Fabric tables Data 360 may query and who approves new ones. Zero copy still creates a new access path.
Before Renewal:
- Don't add multiyear Agentforce seats for sellers who will mostly work in Copilot until Salesforce publishes GA terms for the plugin. Ask for a swap right that converts unused Agentforce seats to whatever Salesforce in Copilot requires.
- If Microsoft raises Dynamics 365 Activate in your Copilot renewal, ask for an Activate assessment of your org in writing. It gives you a documented alternative to bring to the Salesforce negotiation.
The Bigger Picture
Salesforce has offered its sales skills to Claude through MCP since September, and to Copilot since this week. Our Work IQ coverage shows Microsoft building the same grounding for Dynamics 365 from the other side. When the interface moves, the money follows the interface and the system of record has to justify its own fee. Salesforce is betting its data, rules and actions are enough. Microsoft is collecting the Copilot seat either way and keeping a migration tool ready.
For a buyer the practical move is narrower: find out which assistant each seller uses, and pay for that one. Send the two licensing questions this week, and bring the pilot numbers to the table when Salesforce publishes GA terms for the plugin.
Continue Reading
- Claudeforce Has No Published Price and Two Separate Meters
- Get Agentforce Coworker Action Billing in Writing Before You Buy
- Microsoft Work IQ Builds Copilot's Dynamics 365 Model From CRM Views
- Microsoft's New Copilot Bills Autopilot Outside the $30 Seat
- SalesBleed Turned a Public Web Form Into an Agentforce Data Leak
- AI Bundles Push Microsoft, Google and Salesforce to Raise Prices
