AI for admins

Copilotforce explained: what Salesforce in Microsoft Copilot actually does

By the orgadmin.ai team7 min read

On 17 November 2026, at Microsoft Ignite, Salesforce and Microsoft announced Copilotforce. Three months after the Claude partnership Salesforce called Claudeforce, it is the same idea pointed at Microsoft: put Salesforce data and sales workflows inside the AI assistant your company already uses, rather than asking everyone to come to Salesforce.

The announcement bundles several products at different stages of readiness. This post separates what you can switch on this week from what is still a pilot, lists what it needs, and walks through the admin setup.

Copilotforce in one table

PieceWhat it doesStatus (18 Nov 2026)
Salesforce in Microsoft CopilotA plugin that lets Microsoft 365 Copilot read and update Salesforce data using sales skillsBeta (public preview), request access through AgentExchange
Sales Cloud in TeamsSalesforce sales workflows inside Microsoft Teams, with Agentforce Coworker as the action layerPilot with enterprise customers; Microsoft says open beta later this year
Data Federation (OneLake → Data 360)Query Microsoft Fabric / OneLake data from Salesforce Data 360 without copying itGenerally available
Data 360 sharing into OneLakeThe reverse direction: Data 360 data visible in Fabric without copying itPublic preview (beta)
Informatica plugin, Foundry and Fabric scanningData governance and developer tooling around the aboveAnnounced; no availability date given

Pricing has not been published. Both companies' releases say packaging may change and that availability depends on your agreements.

The part most people mean: Salesforce in Microsoft Copilot

What sellers get. Inside Microsoft 365 Copilot (Salesforce recommends using it in Copilot Chat or Cowork for now), a seller can ask about accounts, deals, pipeline and activity, and Copilot calls Salesforce skills to fetch the data or propose an update. Microsoft's release says the plugin ships with "38+" prebuilt sales skills and names examples like pipeline review, close planning, deal review, customer health, renewal radar and call follow-up. Copilot can combine that with what it already knows from Outlook, Teams meetings and SharePoint, which is the real selling point: the meeting notes and the opportunity in one answer.

Salesforce says support inside Outlook, Word and Excel is planned for later this year.

How it connects. Under the hood, Copilot talks to your org through the Salesforce MCP server, the same Model Context Protocol approach Salesforce uses for Claude and other AI clients. Salesforce describes the plugin as running on AIforce, its layer for exposing Salesforce capabilities to outside AI tools (we explained AIforce here).

What you need.

  • A Salesforce org on Enterprise, Performance, Unlimited or Developer edition, using Lightning Experience.
  • A Microsoft 365 Copilot licence for every user who will use it.
  • A commercial Microsoft 365 tenant. During the beta, Government tenants (GCC, GCC High and DoD) are not supported.
  • A Microsoft 365 tenant admin, or someone with the Copilot administrator role.
  • Acceptance of Salesforce's beta terms. It is a beta service, so read them with whoever owns your contracts.

How an admin sets it up

Salesforce documents the setup in two halves: Salesforce first, then Microsoft 365.

In Salesforce

  1. Request access through the Salesforce in Microsoft Copilot (Beta) listing on AgentExchange.
  2. Activate the Salesforce MCP server in Setup.
  3. Optionally create a permission set for the users who get access. Salesforce suggests the label Salesforce in Microsoft Copilot (Beta) Users.
  4. Create an External Client App for Copilot. Salesforce's suggested name is Microsoft Copilot Integration, and the callback URL is https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect.
  5. In the External Client App, set access to admin-approved users and approve only your pilot group. Note the consumer key and secret.

In the Microsoft 365 admin center

  1. Go to Copilot → Connectors → Add connection and search for Salesforce (beta). Do not pick the older Microsoft connector for Salesforce. It is a different product.
  2. Choose OAuth 2.0, paste the consumer key as the client ID and the consumer secret as the client secret, click Authorize and log in to Salesforce. Your own Salesforce user must be approved in the External Client App, and your browser must allow pop-ups.
  3. Choose who can use the connector (everyone, or specific users and groups), then Create. Salesforce says it can take about 30 minutes to appear.
  4. Roll out the plugin to the same users in the Microsoft 365 admin center, and keep that list in step with the approved users in Salesforce.

What Copilot can and cannot do in your org

This is the part security teams will ask about, and the documentation is reassuringly specific.

  • Each user signs in as themselves. Their profile, permission sets, sharing rules and field-level security apply to every request. Copilot sees what that user could see in Salesforce, no more.
  • Writes need approval by default. Copilot groups the Salesforce tools into read tools (such as Discover and Describe), which always run, and write tools, which ask first. The write tools are Dispatch, which creates and updates records, and Display widget, which only renders cards and tables but is grouped with writes. Users can switch a write tool to Always allow under Settings → Sources in Copilot.
  • It cannot delete records. Copilot labels the write tools "Write/Delete", but Salesforce says the plugin cannot delete.
  • Validation rules still apply to any record it updates.
  • Once data reaches Microsoft, Microsoft's terms apply. Salesforce's documentation says your contract with Microsoft, not Salesforce, governs how Microsoft handles the data after it crosses the MCP connection. Check that with whoever owns your Microsoft agreement before a production rollout.

Two practical consequences for admins:

  1. Over-permissioned users become over-permissioned AI. If a seller can see every account in the org because of a broad permission set or "View All", so can Copilot on their behalf, now with a natural-language search box. Clean up access before the pilot. A security review that lists who holds View All Data, Modify All Data and broad object access is a sensible first step.
  2. Decide the "Always allow" policy up front. Approve-each-write is the safe default. If sellers turn it off, Copilot can update stages and fields without a second look. Agree a rule and say it in your rollout note.

Copilotforce vs Claudeforce vs Agentforce

CopilotforceClaudeforceAgentforce
Where the user worksMicrosoft 365 Copilot, TeamsClaude apps (and Claude inside Salesforce)Salesforce, Slack, your channels
Who pays for the AIYour Microsoft 365 Copilot licenceYour Claude planSalesforce Flex Credits / Agentforce licences
How it reaches SalesforceSalesforce MCP server + External Client AppSalesforce MCP server + plugin or custom connectorNative
Best forMicrosoft-first companies whose sellers live in Outlook and TeamsTeams standardised on ClaudeCustomer-facing and Salesforce-native agents

They are not mutually exclusive. The same org can run all three, and each runs as the signed-in user. The more AI front doors you open, the more it matters that user permissions are right, because every door inherits them.

For the Claude side of the same story, see Claude and Salesforce: every way to connect them.

What Copilotforce does not cover

Copilotforce is built for sellers working with records. It does not help an admin or developer understand the org itself: why a deployment failed, which flows touch a field, what a debug log says, or which permission set grants Modify All Data. That needs tools that read metadata, code and security settings, not opportunities.

That is the job of an admin-focused MCP server such as orgadmin.ai's, which connects to Claude, ChatGPT and coding agents with read-only access by default and no deploy tool in its catalog. It does not plug into Microsoft 365 Copilot, and it does not need to: it serves a different person in the same org.

A sensible pilot plan

  1. Week 0: confirm editions, Copilot licences and tenant type; read the beta terms; review who has broad data access.
  2. Week 1: set up the MCP server and External Client App in a sandbox or with a small group of approved users; keep write approvals on.
  3. Weeks 2–3: have five to ten sellers use it for real meeting prep and pipeline reviews; collect wrong answers and surprising data exposure.
  4. Week 4: decide whether to widen the group, and write down your approval policy before you do.

Copilotforce is a meaningful step for companies that live in Microsoft 365. It is also a beta, and it makes every seller's Salesforce permissions reachable from a chat box. Treat the rollout as an access review as much as a feature launch, and it will be worth the effort.

Try it on your own org

orgadmin.ai puts an AI assistant, a security review and 21 more tools on your Salesforce org. 14-day free trial, no credit card.

Start free trial