Microsoft and Salesforce launch Copilotforce, and Microsoft keeps selling a tool to leave Salesforce
Copilotforce puts Salesforce customer data inside Microsoft Copilot through a new plugin, even as Microsoft keeps building a separate tool to help customers leave Salesforce entirely.

Microsoft and Salesforce, longtime rivals in sales software, launched a joint integration called Copilotforce on November 17, putting Salesforce customer data and actions directly inside Microsoft's Copilot assistant for the first time.
The centerpiece, unveiled at Microsoft Ignite, is a plugin called Salesforce in Copilot, now in public preview with more than 38 prebuilt "skills" grouped under three goals. Under "grow revenue" sit Pipeline Review and Close Planning; under "manage risk" sit Deal Review, Customer Health and Renewal Radar; under "move faster" sits Call Follow-Up. Sellers reach their CRM data through an authenticated Salesforce MCP connection, and any write-back to the CRM, such as updating a deal stage or logging a call, requires the seller to confirm the action first, according to Microsoft's announcement.
A second piece, Sales Cloud in Teams, is still in pilot with enterprise customers and surfaces pipeline progress, deal notifications and briefing material inside Teams itself, with a wider beta planned later this year. On the data side, Microsoft Fabric's OneLake can now feed Salesforce's Data 360 customer-data platform directly (general availability), and Data 360 can share curated data back into OneLake (public preview) through what Microsoft calls a "Zero Copy" link, meant to avoid building custom pipelines between the two systems.
What changed
For years, Microsoft and Salesforce have built competing versions of the same product: an AI layer that sits on top of a company's customer data and tells sales reps what to do next. Copilotforce doesn't retire that rivalry, it just adds a second track alongside it. The same week, per CX Today, Microsoft extended its own Dynamics 365 Activate migration tool to help customers move off SAP's ECC system, a reminder that Microsoft is still courting CRM switchers with one hand while building the plugin that keeps Salesforce customers productive with the other. The same report notes Microsoft's own Dynamics 365 Sales and Customer Service plugins for Copilot already shipped generally available with more than 57 skills, well ahead of the Salesforce plugin's preview status, so the partner getting the faster on-ramp into Copilot right now is Microsoft's own CRM, not Salesforce's.
Microsoft Commercial Business CEO Judson Althoff framed the deal around data, saying Copilotforce "will give sales teams the intelligence they need to make faster, higher-confidence decisions." Salesforce president and COO Miguel Milano cast it as bringing Salesforce to "the largest surface in enterprise software today." Accenture, serving as both implementation partner and first pilot customer, is testing the integrations across its own 55,000 Salesforce seats and, per Microsoft, more than 740,000 Copilot users firmwide.
A CRM's job becomes being a well-structured data source an agent can call, not a screen someone stares at.
Who it affects
This lands directly on anyone marketing CRM, sales-enablement or sales-intelligence software. The pitch for a standalone sales tool used to rest on its interface, the dashboard a rep opened every morning. Copilotforce, like the ChatGPT for Sales plugin ecosystem OpenAI launched the same week, treats the interface as someone else's property: a CRM's job becomes being a well-structured data source an agent can call, not a screen someone stares at.
- Vendors that compete with Salesforce or Dynamics now need a story for showing up inside both companies' agent surfaces, not just their own app.
- ISVs built on top of Salesforce or Microsoft 365 should expect customers to start asking whether their data is exposed through MCP or an equivalent connector.
- Buyers comparing CRM platforms will increasingly weigh which agents can reliably act on the data, alongside the usual feature checklist.
What a software marketer should do
Audit how your own product's data would read to an outside agent: field names, completeness, permission structure, before pitching "AI-ready" as a feature. Stop positioning purely against Microsoft or Salesforce as platforms, and position instead on what an agent can and can't reliably do with your data once it sits inside either one's Copilot.
The arrangement also carries a trust question worth watching. Microsoft is asking Salesforce customers to let an outside assistant write to their CRM, while separately marketing a tool to help those same customers leave Salesforce altogether. Most martech and sales-tool vendors now sit inside at least one rival's ecosystem in a similar way, so this is not a one-company problem.
- Write down, in plain language, whether a given integration partner is a genuine complement to your product or a long-term substitute for it, and say so to prospects before they ask.
- If your product writes to Salesforce or Dynamics, test what a seller sees when they ask Copilot about your data today, not just what your own dashboard shows.
- Treat "preview" versus "generally available" status, like the gap between Salesforce's and Microsoft's own Copilot plugins here, as a real signal of whose roadmap is ahead, not a footnote.
None of this is final: Microsoft's release notes that forward-looking statements may change, and regional availability depends on individual customer agreements. But the direction is clear enough to plan around. Software marketers who sell into, around or against Salesforce and Microsoft should expect their product's next evaluation to include a question neither company's sales deck answers cleanly: what happens to your data, and your pitch, once it's inside somebody else's assistant.
AIChatGPT shows purchase intent in just 6.9% of conversations, new study finds
Sienna Mcpherson · 4 min read
Tools & AnalyticsOpenAI launches ChatGPT for Sales, and more than 30 vendors sign on as plugins
Sienna Mcpherson · 4 min read
Tools & Analytics