The short version
- The Salesforce plugin for Microsoft Copilot is in public preview as of November 17, 2026, distributed through the Salesforce AgentExchange listing and the Microsoft Copilot plugin directory, with launch coverage reporting 38-plus prebuilt sales skills.
- Enablement is two-sided: a Salesforce admin requests access via the AgentExchange listing and activates the Salesforce MCP server in Setup, and a Microsoft 365 admin adds the Salesforce (beta) connection under Copilot connectors.
- Every user needs a Microsoft 365 Copilot licence on a commercial tenant, plus appropriate Salesforce access - and the M365 side needs tenant-admin or Copilot-administrator rights to add the connection.
- Watch the old-connector trap: early setup guidance is explicit that you want the new Salesforce (beta) connection, not the older Microsoft-built Salesforce connector that already exists in the catalog.
- This is preview software: pilot against a sandbox with scoped access, keep a human gate on writes, and expect the flow to change before GA - we will update this guide as it does.
Before You Start: What This Is and Is Not
The Salesforce plugin for Microsoft Copilot went to public preview on November 17, 2026, as part of the Copilotforce announcement. It lets sellers ask natural-language questions answered from live Salesforce data and take CRM actions inside Copilot, with launch coverage reporting 38-plus prebuilt sales skills. Two honesty notes before the steps. First, this is preview software: the flow below reflects the AgentExchange listing and early setup guidance as of November 2026, and preview flows change - we will update this post as they do. Second, nothing here is a production rollout guide; it is how to evaluate the real thing safely.
Step 1: Check the Prerequisites
On the Microsoft side you need a Microsoft 365 Copilot licence for every user who will touch the plugin, a commercial Microsoft 365 tenant, and someone holding tenant admin or the Copilot administrator role to add the connection. On the Salesforce side you need an admin who can work in Setup, and users whose Salesforce permissions match what the skills will read and write - the plugin respects your org's access model, so a seller who cannot see a record in Salesforce will not see it in Copilot either.
Step 2: Request Access on AgentExchange
The Salesforce side starts at the Salesforce in Microsoft Copilot (Beta) listing on AgentExchange - the same marketplace that hosts the Salesforce-in-Claude plugin and the MCP server catalog. Request access through the listing; preview programs typically involve an approval step rather than an instant install, so build a few days of slack into your pilot plan.
Step 3: Activate the Salesforce MCP Server
Under the hood, the plugin rides the Salesforce MCP server - the same plumbing behind Salesforce in Claude and the Headless Toolkit. In Salesforce Setup, activate the MCP server so external AI surfaces can reach the org through governed, permissioned tools. If you have already enabled it for the Claude plugin, this step is familiar ground; if not, it is the moment to decide scoping deliberately, because this server is now the front door for every AI surface you add.
Step 4: Add the Connection in Microsoft 365
On the Microsoft side, the admin goes to Copilot settings, then Connectors, then Add connection, and searches for Salesforce (beta). The trap early guidance calls out explicitly: the catalog also contains an older, Microsoft-built Salesforce connector - do not pick that one. Choose the new beta connection that belongs to the Copilotforce integration. Once added, allow roughly 30 minutes for the connection to propagate before users see it in Copilot.
Step 5: Pilot Like You Mean It
Connect a sandbox or a tightly scoped pilot group first, not production for the whole revenue org. Have the pilot group run the real workflows - meeting prep against actual accounts, deal-health questions on live opportunities - and log where answers are wrong, stale, or grounded in bad data. That log is gold: wrong answers in a copilot are almost always your org's data quality wearing an AI costume, and fixing the underlying hygiene is what makes the eventual rollout work. It is also exactly what our fixed-scope Salesforce org audit maps, and the wider rollout question - this plugin versus Teams versus the Claude side, and in what order - is what a Copilotforce scoping call is for.
