Industry

Copilotforce: what Microsoft and Salesforce are connecting, and for whom

Copilotforce puts Salesforce data and sales actions inside Microsoft Copilot over authenticated MCP access, adds a Teams app and links Data 360 with Fabric. Most of it is preview or pilot, and no price is published.

Microsoft and Salesforce announced Copilotforce at Microsoft Ignite on 17 November 2026. The name covers three connections. A plugin called Salesforce in Copilot brings Salesforce customer records, sales workflows and CRM actions into Microsoft 365 Copilot, with more than 38 prebuilt sales skills. A Sales Cloud app puts pipeline and deal information into Microsoft Teams. And two-way Zero Copy links let Salesforce Data 360 query Microsoft Fabric data in place, and let Fabric read curated Data 360 data without a duplicate copy.

The single most useful fact for anyone planning around it is the status column. Only the Fabric-to-Data 360 query path is generally available. The Copilot plugin is in public preview, which both companies also call beta. Sharing Data 360 into Fabric is in public preview. The Teams app is in pilot with enterprise customers, and Microsoft says an open beta is “coming later this year”. Neither company has published a price, a licence requirement or a general-availability date for the Copilot plugin.

The piece that matters most for builders and administrators is how Copilot reaches Salesforce. Microsoft’s release says sellers do it “through authenticated Salesforce MCP access”, within their existing Salesforce permissions, and both companies say write-backs to the CRM need explicit user confirmation. That moves the governance question from “can Copilot see Salesforce?” to “what is each user permitted to do in Salesforce, and who approved the plugin?”. This article sets out what each component does according to the two announcements and the product documentation we could read, where the two companies’ accounts differ, what is not yet stated, and what an administrator can do now. GenAI Brief has not used the preview.

What was announced, piece by piece

The two press releases were published within minutes of each other on 17 November: Salesforce’s at 18:05 UTC and Microsoft’s at 18:10 UTC. They describe the same partnership in nearly the same words, and both carry the same executive quotes. They differ in emphasis and in a few details, which the table below and the section after it record.

ComponentWhat it doesStatus on 17 November 2026Where the status comes from
Salesforce in CopilotPlugin that brings Salesforce data, workflows and actions into Microsoft Copilot; more than 38 prebuilt sales skillsPublic preview (beta)Both releases
Sales Cloud in TeamsTeams app with pipeline and quota views, deal notifications, briefings and editable adaptive cardsPilot with enterprise customers; open beta “later this year” (Microsoft)Both releases
Data Federation (Fabric OneLake into Data 360)Data 360 queries supported OneLake data without moving it out of FabricGenerally availableBoth releases; Salesforce’s connector documentation still says Beta
Data 360 data sharing (Data 360 into OneLake)Curated Data 360 data exposed to Fabric through a shortcut, for analytics and AI workloadsPublic preview (Microsoft); “Public Preview, Beta” (Salesforce)Both releases
AccentureDesign and implementation partner, and “customer zero” in its own sales organisationPilot deploymentBoth releases

Compiled by GenAI Brief from the Microsoft and Salesforce releases of 17 November 2026 and Salesforce’s developer documentation, read on 18 November 2026.

Both releases carry the usual forward-looking caveats. Microsoft’s says statements about future direction “are subject to change or withdrawal without notice and represent goals and objectives only.” Salesforce’s ends: “Pricing and packaging are subject to change. Regional availability and customer access are governed by applicable customer agreements. Customers should base purchasing decisions on capabilities that are commercially available today.” For three of the four components, nothing is commercially available yet in the general sense.

Where the two accounts differ

The differences are small but useful, because each company describes its own side of the connection in more detail.

  • The connection mechanism. Microsoft names MCP: “Through authenticated Salesforce MCP access, sellers can securely retrieve customer information and take supported business actions within their existing Salesforce permissions.” Salesforce’s release does not use the term. It says the plugin is “Powered by AIforce, the live interface layer that brings Salesforce capabilities into external AI environments”, and that it “operates through authenticated user access”.
  • Agentforce in Teams. Salesforce says sellers in the Teams app “will be able to act on those insights with Agentforce Coworker”, its agent product, with updates syncing back to Salesforce. Microsoft’s release does not mention Agentforce at all.
  • Where to get the plugin. Salesforce says Salesforce in Copilot is “Available in our AgentExchange and the Microsoft Copilot plugin directory.” Microsoft’s release does not name a distribution channel; its Ignite blog points to a new plugin catalogue.
  • Named skills. Microsoft names six skills: Pipeline Review, Close Planning, Deal Review, Customer Health, Renewal Radar and Call Follow-Up. Salesforce describes three workflows instead: customer meeting preparation, deal-health analysis, and pipeline review with action plans.
  • Tense. Salesforce writes about the plugin and the Teams app in the future tense (“will enable”, “will bring”), consistent with a preview and a pilot. Microsoft writes in the present tense.

Salesforce’s release also folds in a separate announcement about Informatica, which Salesforce owns: an Informatica Plugin for Copilot that lets business users discover data and check its quality in natural language, plus Foundry and Fabric integrations. That is a distinct product and has its own Salesforce story.

Salesforce in Copilot: what the plugin does

The plugin is the centre of the announcement. According to both releases, a seller working in Copilot can ask natural-language questions about accounts and opportunities, get answers grounded in Salesforce records, and take supported Salesforce actions without opening Salesforce.

What both releases stress is that the Salesforce data is combined with Microsoft’s own context. Microsoft calls that layer Work IQ, “the intelligence layer powering Copilot”, which it says draws on Teams meetings, Outlook email and documents in SharePoint and OneDrive. The Microsoft release puts the pitch this way: Work IQ and Salesforce “help sellers understand not only what’s recorded in CRM, but what’s happening across customer conversations and collaboration”, and what should happen next.

The workflows Microsoft describes fall into three groups:

  1. Revenue planning. The Pipeline Review and Close Planning skills pick which opportunities deserve attention and draft a path to signature; that deal context then informs the proposals and business cases sellers develop in Word and PowerPoint.
  2. Risk. The Deal Review, Customer Health and Renewal Radar skills compare the stage or renewal date recorded in Salesforce with concerns raised in Outlook threads, escalations in Teams and unresolved commitments.
  3. Follow-up. The Call Follow-Up skill turns a customer conversation into a follow-up draft, an internal recap and proposed CRM activities for the seller to review and confirm.

Salesforce’s version is the same idea in different words. A meeting-preparation workflow combines “account history and meeting transcripts into a single executive brief”; deal-health analysis surfaces “hidden deal risks and customer sentiment”; pipeline review turns pipeline data “into ready-to-execute close plans directly inside Word and PowerPoint”. The phrases “saving hours of prep time” and “slashing administrative overhead” in Salesforce’s release are claims, with no measurement attached.

What a skill is in this context

Both companies now use “skill” and “plugin” in a specific sense. Microsoft’s plugin registry announcement, published on 30 September 2026, defines a plugin as a package that can contain skills (“reusable instructions for specialized work”), connectors (“approved access to services and data”) and agents. Developers can package “the metadata and configuration needed to connect to MCP servers” inside a plugin.

Salesforce’s AIforce guide for administrators uses the same vocabulary. It defines a skill as “a folder of instructions, with optional scripts and reference files, that an AI client loads when a task calls for it”, and a plugin as “the package that delivers skills to a client”, which can also carry MCP server connections. Its example is Salesforce’s Claude integration: “Sales Cloud for Claude is a plugin that packages sales skills with the connection to Salesforce’s hosted MCP server.” The same guide counts “37 prebuilt sales skills for Claude across 8 categories” in Salesforce in Claude.

Read together, the documents suggest that Salesforce in Copilot follows the same pattern as Salesforce in Claude: a packaged set of sales instructions plus an authenticated MCP connection to Salesforce. That is our inference from the vocabulary and from Microsoft’s MCP wording. Neither Copilotforce announcement publishes the plugin’s manifest, the MCP server it calls or its OAuth configuration, and we have not inspected the preview.

For readers new to the protocol, our guide to MCP explains how an AI application connects to a tool server, and why a skill (instructions) and a server (capabilities) are separate pieces.

Copilotforce as one surface of AIforce

The name places the partnership in a family. Salesforce announced AIforce at Dreamforce in September 2026 as a layer that connects Data 360, Customer 360 and Agentforce to outside AI interfaces. Its admin guide lists the named experiences: Claudeforce, the partnership with Anthropic whose product is Salesforce in Claude; Slackforce, which brings Salesforce into Slack; and Agentforce Coworker in Salesforce’s Lightning interface. It also describes a “Headless Toolkit” of “60+ MCP tools, 4,000+ existing APIs, and 220+ CLI commands, all accessible to authenticated users governed by the same security model you already manage.”

Copilotforce follows the naming pattern, and the Salesforce release says the Copilot plugin is “Powered by AIforce”. The strategic reading is that Salesforce is making its CRM reachable from whichever assistant a company standardises on, rather than requiring sellers to work inside Salesforce’s own interface. An analyst quoted by CIO Dive at the AIforce launch raised the obvious dependency: Terra Higginson of Info-Tech Research Group said customers will still need clean, connected and governed data underneath.

How access and write-back are governed

The governance model the two companies describe is a split. Salesforce decides what data a user can reach and which actions are allowed. Microsoft applies its compliance controls to the communications and documents Copilot touches. Both releases use the same sentence: “Salesforce controls data access and governs supported business actions, while Microsoft ensures communications and documents adhere to existing enterprise compliance policies.”

Salesforce adds that the plugin “operates through authenticated user access, preserving the granular permissions, sharing rules, and audit trails established in both environments.” Both releases also make the same promise about changes to Salesforce data: “Supported writeback actions to the CRM require explicit user confirmation and respect existing validation rules.”

Three practical consequences follow from that design.

Copilot acts as the user, with the user’s permissions. Salesforce’s AIforce admin guide states this plainly for any agent that reaches Salesforce through its MCP servers or APIs: “When an agent acts on behalf of a user, it can do anything that user is permitted to do. That means your permission model matters more than ever.” The guide lists what travels with each call: the user’s identity, sharing rules and field-level security, the set of tools explicitly exposed, and validation rules, triggers and approval chains, which “all fire regardless of entry point”. It also says Salesforce “plans to roll out Agentic Identity”, under which agents would have their own credentials and permissions. That is not available yet, so for now a Copilot session’s reach in Salesforce is the seller’s reach.

Confirmation covers writes, not reads. The explicit-confirmation promise applies to write-back actions. Reads within a user’s permissions, which are what feed meeting briefs and deal reviews, are governed by Salesforce’s sharing model, not by a confirmation step. Data that a seller can see in Salesforce can therefore appear in a Copilot answer, a Word draft or a PowerPoint deck, where Microsoft’s compliance tooling takes over. Teams with strict rules about which CRM fields may leave Salesforce should check field-level security before enabling the plugin.

“Supported” actions are not yet listed. Both releases qualify the actions as “supported” without publishing the list. Microsoft mentions proposed CRM activities from call follow-ups; Salesforce mentions updating “supported opportunity details” in Teams. Which objects and fields the preview can write is something to test, not assume.

Microsoft’s side: who may install the plugin

On the Microsoft side, a third-party plugin is governed like other plugins in the Microsoft 365 admin centre. Microsoft’s admin documentation describes the controls we could confirm:

  • By publisher. Under Agents, Settings, Agent and plugin access, administrators choose which publisher categories users may install from: Microsoft, the organisation itself, or certified external publishers.
  • By user. For each plugin, under Agents, Tools, Plugins, availability can be set to all users, no users, or specific users and groups.
  • Requests. Users who are blocked can still see a plugin and select Request access; the request lands in the admin centre for approval or rejection.
  • Block. Blocking a plugin blocks it and the agents that depend on it, although “Associated MCP servers and connectors remain available to other plugins.”

The same page carries a warning that applies directly to a Salesforce plugin: “Approval grants access to the requested plugin; it doesn’t replace permissions or connection setup required by its connected services.” It adds that users “might still need to sign in, grant consent, or configure a service connection after installation”, and that administrators should not “treat package approval or blocking as granting or revoking connected-service permissions or credentials.” In other words, enabling Salesforce in Copilot in Microsoft 365 does not by itself give anyone Salesforce access, and blocking it there does not revoke a Salesforce token.

Microsoft’s Ignite post adds a wider control: Agent 365, its agent-management product, is “broadening visibility through new connected platforms, including Anthropic, Databricks, OpenAI, Salesforce and more”, and adding controls for agent tools “including model context protocol (MCP) servers, plugins, and skills.” The post does not say what Agent 365 can see or control in Salesforce specifically.

Salesforce’s side: how MCP clients authenticate in general

Salesforce has not documented the Copilot connection, but its developer documentation for hosted MCP servers shows the controls a Salesforce administrator generally has over any MCP client. The guide says: “Use an External Client App to connect an MCP client to a Salesforce org. Connected Apps aren’t supported.” The app needs the OAuth scopes “Access MCP servers (mcp_api)” and “Perform requests at any time (refresh_token)”, and can take “up to 30 minutes to become available”.

The guide’s production hardening section is the part administrators should read. “By default, any user in your org can authenticate through the External Client App,” it says, and access can be limited by requiring a custom permission set for pre-authorisation. Connections can also be restricted by IP range, with a warning that “Some MCP clients operate from IP ranges that exceed Salesforce’s allowlist capacity.” Whether the Copilot plugin uses an External Client App that customers configure themselves, or a managed connection that Salesforce and Microsoft provision, is not stated in the announcements. Our explainer on MCP security and authentication covers how the OAuth flow behind such connections works and where it can be attacked.

Sales Cloud in Teams and Agentforce Coworker

The Teams component predates Copilotforce. Salesforce says Sales Cloud in Teams was “introduced at Dreamforce and currently in pilot”, and calls the Copilotforce work an extension of it. Microsoft’s release describes it as “now available in pilot” and promises an open beta “later this year”, which on a 17 November announcement means by 31 December 2026.

According to the two releases, the Teams app gives sellers a view of pipeline and quota progress, deal notifications and briefing materials, which Salesforce calls “AI-driven”. Salesforce adds that interactive adaptive cards will let sellers “update supported opportunity details, with changes saved back to Salesforce”, and share records in deal rooms “to align cross-functional teams without tool-switching”. Salesforce’s release adds that the app reaches the place “where over 400M active users already chat and collaborate”; that is Salesforce’s figure for Teams, not a Copilotforce adoption number.

The Agentforce detail is Salesforce’s alone. Its release says sellers “will be able to act on those insights with Agentforce Coworker”, with the “same Salesforce permissions and governance coordinating the right Agentforce agents”. The availability list adds that Agentforce Coworker “allows sellers to delegate work and take action directly within Teams”. Microsoft’s release does not mention this, so customers should not assume that an Agentforce agent running inside Teams is covered by the same Microsoft-side controls as the Copilot plugin until both companies document it.

The data half of the partnership is the most concrete, because one direction is generally available and documented. “Zero Copy” is Salesforce’s term for reading data where it lives instead of copying it through an extract, transform and load pipeline.

Fabric into Data 360: Data Federation

Data Federation lets Salesforce Data 360, Salesforce’s customer data platform, “directly query and analyze supported Microsoft Fabric OneLake data”, leaving the data in Fabric. Microsoft’s examples are a service agent seeing a customer’s recent purchases, a marketer building a segment from spending behaviour, and “an AI agent” answering “from current data”. Salesforce adds that the combined data can be explored in Tableau and used by Agentforce.

Both releases call this generally available. Salesforce’s own connector documentation, read on 18 November 2026, still titles it “Microsoft Fabric OneLake Connector (Beta)” and says “The connector is beta for file federation”, subject to Salesforce’s Beta Services Terms. It lists the connection method as “Zero Copy (File Federation): Commercial Only”. Documentation often lags a launch by days, but a customer relying on the general-availability status for a contract should get it confirmed in writing.

The setup guide shows what the connection requires, and it is a reminder that “no pipelines” does not mean “no configuration”:

RequirementWhat the documentation says
Salesforce permissionSystem Admin profile or Data 360 Architect permission set to create the connection
Fabric tenant settingsAllow apps outside Fabric to access OneLake data; allow service principals to call Fabric public APIs
IdentityRegister Data 360 as an application in Microsoft Entra ID with a client secret
Access scopeContributor on a workspace, or Read and ReadAll on selected lakehouse items
NetworkAllowlist Data 360’s IP addresses for catalog and storage endpoints; private endpoints not supported
Data formatLakehouse items only; Apache Iceberg-compatible Delta tables in Parquet; no native Iceberg tables, external tables, views or Delta tables using deletion vectors
LimitsNo time or timestamp_ntz types; change-data features that need a primary key are not currently possible for OneLake Delta tables

From Salesforce’s OneLake file federation setup guide, read on 18 November 2026.

The last row matters for the agent use case in Microsoft’s examples. Salesforce’s guide says some Data 360 features “require detecting when a data lake object changes (for example, data actions)”, which needs a primary key, and “Currently, this isn’t possible for Microsoft Fabric OneLake Delta tables.” An agent can read current Fabric data through federation, but event-driven Data 360 features that react to changes in that data are not available on this path today.

Data 360 into Fabric: data sharing

The reverse direction lets organisations “securely share curated Data 360 customer intelligence into OneLake”, in Microsoft’s words, so that data teams can analyse it alongside other enterprise data “without duplicating data”. Microsoft calls the mechanism a “Salesforce Data 360 shortcut”; OneLake shortcuts are Fabric’s way of referencing data stored elsewhere. Both companies say this is in public preview, and Salesforce’s release describes it in the future tense.

The practical significance is that customer profiles and segments built in Data 360 become available to Fabric notebooks, Power BI reports and Microsoft-side AI workloads. That is useful for analytics teams that sit on the Microsoft stack. It also means governance of that data now spans two systems, so data owners need to decide which Data 360 objects are curated for sharing and who in Fabric can read the shortcut.

Pricing, licensing and what is not stated

The gaps are as important as the announcements for anyone budgeting.

  • No price. Neither release gives a price for the plugin, the Teams app or either Zero Copy feature.
  • No licence requirements. Neither says which Microsoft 365 Copilot licence, Teams licence, Salesforce edition or Data 360 entitlement a customer needs. Microsoft’s plugin registry post says only that “Basic registry and management capabilities for Microsoft Copilot experiences are included with qualifying Microsoft cloud subscriptions.”
  • No general-availability dates for the Copilot plugin or data sharing. The only dated commitment is the Teams open beta “later this year”.
  • No region list. Both releases say regional availability is governed by customer agreements. The Fabric connector documentation says “Commercial Only”.
  • No skill list. “38+” skills are counted, but only six are named.
  • No measured results. Neither company, nor Accenture, publishes time saved, adoption or accuracy figures for the integrations.

Microsoft’s Ignite post describes its general commercial model for Copilot as “our predictable, per-user subscription” plus “a usage-based consumption model” for the hardest tasks. It does not say which of these a third-party plugin’s activity falls under, or whether skills that draft Word and PowerPoint deliverables from Salesforce data consume metered capacity. A customer piloting the preview should ask both vendors how preview usage will be billed after general availability.

Accenture as customer zero

Accenture’s role is the main evidence offered that the integrations work at scale, and it is a deployment, not a measurement. Both releases say Accenture has scaled Copilot “to more than 740,000 people” and is “one of the largest Salesforce users globally with 55,000 users” (Salesforce says 55,000 active users). It is deploying and validating the integrations in its own global sales organisation, and sharing what it learns with clients. Accenture’s boilerplate puts its headcount at about 814,000.

Julie Sweet, Accenture’s chair and chief executive, is quoted in both releases: “As a Global Partner of the Year for both Salesforce and Microsoft and one of their top customers, we are uniquely positioned to bring our expertise to help design and implement Copilotforce so that our clients can quickly get more value from their technology investments.” Accenture is also the design and implementation partner, so the pilot customer and the systems integrator selling the rollout are the same company. That is common in enterprise launches and does not make the pilot less real, but it means the first published lessons will come from a party with a commercial interest in adoption.

Why Microsoft is hosting a rival CRM in Copilot

The partnership sits awkwardly with Microsoft’s own sales software, and the Ignite programme shows both at once. The same Copilot post that announced Salesforce in Copilot also announced “Dynamics 365 in Copilot”, with updated plugins for Dynamics 365 Sales, Service and Finance and Operations that “bring more than 100 prebuilt skills into Copilot”. A few paragraphs later, it says: “For sales and service, we know connecting to every system of record is crucial. So, we’re excited to announce Salesforce in Copilot.”

The quotes from the two executives make the same trade explicit. Judson Althoff, chief executive of Microsoft’s commercial business, says: “AI is only as powerful as the data and context that grounds it.” Miguel Milano, Salesforce’s president and chief operating officer, says: “By bringing together the #1 CRM with the #1 productivity surface, we’re transforming AI from a standalone tool into a powerful driver of productivity, smarter decisions and customer success.” Microsoft’s release calls Copilot “the front door to business process”.

Our reading, which is inference rather than anything either company says, is that each side gets something it could not easily build. Microsoft wants Copilot to be the place where work starts even for customers whose system of record is not Microsoft’s, and the volume of Salesforce customers makes that impossible to ignore. Salesforce wants its data, permissions and workflows to stay authoritative even when sellers never open a Salesforce tab, which is the stated aim of AIforce. MCP, which both now support, lowers the cost of that arrangement because neither side has to build a bespoke API bridge for the other. The cost to customers is a governance surface that now spans two vendors’ admin consoles.

What to do now

For most organisations that run Salesforce for sales and Microsoft 365 for everything else, Copilotforce is a preview to evaluate, not a rollout to plan. A sensible sequence:

  1. Treat the plugin as a preview. Run it with a small group of sellers, against a sandbox or a narrowly scoped production profile, and record which actions are actually supported for writes.
  2. Audit Salesforce permissions first. Because Copilot acts with the seller’s permissions, review profiles, permission sets, sharing rules and field-level security for the pilot users before they connect. Anything a pilot user can read can end up in a Copilot draft.
  3. Use both admin consoles. In the Microsoft 365 admin centre, scope the plugin to specific users and groups and decide whether certified external publishers are allowed. In Salesforce, find out how the plugin’s connection is registered and whether it can be restricted to a permission set, as the hosted-MCP documentation allows for other clients.
  4. Ask the pricing and licensing questions now. Before a pilot creates dependence, get written answers on licence prerequisites, how preview usage will be billed after general availability, and regional availability.
  5. For data teams, test federation against the documented limits. Check that the Fabric tables you need are lakehouse Delta tables without deletion vectors, that private endpoints are not a requirement, and that no Data 360 feature you plan to use depends on change detection.
  6. Wait for documentation on Agentforce in Teams. Salesforce describes Agentforce Coworker acting inside Teams; Microsoft does not. Until both document how that agent is governed on the Microsoft side, keep it out of production channels.

Copilotforce is a credible sign that the large platform vendors will expose their systems to each other’s assistants through MCP rather than fight over where the user sits. What it does not yet offer is a priced, generally available product with published controls. The organisations that benefit most from the preview will be the ones that use it to find out what their own Salesforce permission model actually allows, before an assistant starts acting on it.

Sources

  1. Microsoft and Salesforce Announce Copilotforce, Bringing Trusted Customer Context and Action into Microsoft AI Experiences Microsoft
  2. Salesforce and Microsoft Announce Copilotforce, Bringing Salesforce Customer Context and Sales Workflows to Microsoft Copilot Salesforce
  3. Copilot at Microsoft Ignite: Expanding what's possible with intelligence built for work Microsoft
  4. Introducing the plugin registry: one place to discover and govern plugins for Microsoft Copilot Microsoft Tech Community
  5. Manage plugins, skills, and MCP servers in Microsoft 365 admin center Microsoft Learn
  6. Introduction to AIforce for Admins Salesforce Admins
  7. Create an External Client App (hosted MCP servers) Salesforce Developers
  8. Microsoft Fabric OneLake Connector (Beta) Salesforce Developers
  9. Set Up a Microsoft Fabric OneLake File Federation Connection (Beta) Salesforce Developers
  10. Informatica from Salesforce brings Trusted Enterprise Data into Microsoft Copilot, Microsoft Foundry, and Microsoft Fabric Salesforce
  11. Salesforce launches AIforce interface layer CIO Dive

Frequently asked questions

What is Copilotforce?

Copilotforce is the name Microsoft and Salesforce gave on 17 November 2026 to a set of integrations: a Salesforce in Copilot plugin with more than 38 prebuilt sales skills, a Sales Cloud app inside Microsoft Teams, and two-way Zero Copy data links between Salesforce Data 360 and Microsoft Fabric OneLake. Accenture is the design and implementation partner and a pilot customer, which it calls customer zero.

Is Salesforce in Copilot generally available?

No. Both companies say Salesforce in Copilot entered public preview (beta) on 17 November 2026. Neither announcement gives a general-availability date. Salesforce says it is listed in AgentExchange and the Microsoft Copilot plugin directory.

How much does Copilotforce cost?

Neither company has published a price or a licence requirement for the plugin, the Teams app or the Zero Copy features. Salesforce's release says pricing and packaging are subject to change and that customers should base purchasing decisions on capabilities that are commercially available today.

Does Copilot use MCP to reach Salesforce?

Microsoft's release says sellers retrieve customer information and take supported business actions through authenticated Salesforce MCP access, within their existing Salesforce permissions. Neither company has published the technical details of that connection, such as which Salesforce MCP server or OAuth configuration the plugin uses.

Can Copilot change records in Salesforce?

Yes, for supported actions. Both releases say supported write-back actions require explicit user confirmation and respect existing Salesforce validation rules. The Teams app also lets sellers update supported opportunity details through adaptive cards, with changes saved back to Salesforce.

Does Copilotforce copy Salesforce data into Microsoft Fabric?

The two Zero Copy features are designed not to duplicate datasets. Data Federation, which both companies call generally available, lets Data 360 query supported OneLake data in place. Data 360 data sharing into OneLake, in public preview, exposes curated Data 360 data to Fabric through a shortcut rather than a copy.

All industry →