Microsoft 365 Copilot + Salesforce: What the Integration Can (and Can't) Do in 2026
Partly — Microsoft ships an official Salesforce CRM Copilot connector, but it’s read-only. It indexes five standard Salesforce objects — Account, Contact, Opportunity, Lead, and Case — into Microsoft Graph so Copilot, Copilot Search, and Microsoft Search can ground answers in your CRM data and cite the record. It does not write back: Copilot can’t create a task, log an activity, or update a stage in Salesforce through it. Writing to Salesforce exists only through a separate, extra-licensed product — the Sales agent (formerly Sales Copilot / Viva Sales) — which reaches Salesforce over a Power Platform connector inside Outlook and Teams. And either way, everything happens inside a Copilot session you’re driving — nothing watches your pipeline between chats.
Here’s what the two paths actually do, how to turn them on, where the ceiling is, and what to use if you want Salesforce-adjacent work that runs on its own.
What Microsoft 365 Copilot can actually do with Salesforce
Through the Salesforce CRM connector (the default, read-only path):
- Answer questions grounded in CRM records. “What stage is the Dickenson Mobile Generators opportunity in?” or “Show me escalated cases for Pinnacle Health Systems” — answered from indexed Salesforce data, with the record cited, without leaving Teams or Outlook.
- Surface accounts, contacts, opportunities, leads, and cases in Microsoft Search — the same five indexed objects show up across Copilot, Copilot Search, and Search.
- Respect Salesforce permissions. The connector honors Salesforce record-level sharing rules and role hierarchy via identity mapping, so a user only sees CRM records they can already see in Salesforce.
- Ground custom agents. Developers can use the connector as a knowledge source in declarative agents built in Copilot Studio, Agent Builder, or the Microsoft 365 Agents Toolkit — still for retrieval, not writing.
Through the separate Sales agent (extra Microsoft 365 Copilot license, Outlook + Teams):
- View and update CRM records, and create contacts from inside Outlook and Teams — this is the write path, over a Power Platform connector rather than the Graph connector.
- Save Outlook activities to Salesforce, draft emails, and generate Teams meeting summaries tied to a CRM record.
How to set it up
The read-only connector is a tenant-admin job:
- In the Microsoft 365 admin center, go to Copilot → Connectors and select Salesforce CRM, then follow the deployment guide.
- Authenticate to Salesforce and configure the crawl. Optionally add custom fields (fields ending in
__c) and standard fields beyond the default schema. - Set the access model — Only people with access to this data source (enforces Salesforce ACLs via Entra ID identity mapping) or Everyone — and let the full crawl run. Schedule full crawls for off-peak hours; they consume Salesforce API quota.
- Test in Copilot with something read-only: “Give me the name, title, and email for all contacts at United Oil.”
To write to Salesforce, you deploy the separate Sales agent: assign each user a Microsoft 365 Copilot license, install the integrated app from the admin center, enable the Microsoft Power Platform connected app in Salesforce, make sure users are API-enabled in Salesforce, and a msdyn_viva Dataverse environment is provisioned on first sign-in. It’s a heavier lift, and it’s a different product from the base connector.
The limits that matter
- The connector is read-only. It indexes for grounding and search — it cannot create tasks, log activities, or update records back in Salesforce. Microsoft’s own docs describe it purely as surfacing and searching CRM records.
- Only five objects. Account, Contact, Opportunity, Lead, and Case. Activities, Orders, Contracts, and custom objects aren’t indexed by the standard connector; you’d need a custom synced connector via the Copilot connectors API to go further.
- Write-back means a second product and more licensing. The Sales agent can update records, but it requires per-user Microsoft 365 Copilot licenses, a Power Platform connected app, a Dataverse environment, and it lives inside Outlook and Teams — scoped to a seller editing records by hand.
- No triggers, ever. Neither path fires on a Salesforce event. Copilot answers when you prompt it; the Sales agent updates a record when a person clicks. A deal can go cold or a case can breach SLA over the weekend and nothing moves on its own.
- Session-bound and tenant-scoped. Every action needs a driver in a live session, and access is bounded by your tenant’s licensing and each user’s Salesforce permissions. There’s no standing watch on your funnel.
If you want Salesforce-adjacent work that runs on its own: Carly
The moment you want something to happen around Salesforce without you in the chat — a new lead routed and emailed within minutes, a nudge when an opportunity stalls in a stage, a Monday pipeline digest built and sent, a case escalation posted to the right Slack channel — you’ve crossed past what a grounding connector or a manual Sales agent is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a session:
- Fires on events and schedules, 24/7, in the cloud. When an opportunity changes stage or a lead lands in Salesforce, Carly reacts — summarizes it, emails the owner, updates the record, posts to Slack — while your laptop is closed.
- Actually reads and writes. Salesforce is a native Carly integration, so Carly can update records, log activity, and create tasks — not just surface them in a chat.
- Sends, not just drafts. Carly drafts and sends email across Gmail and Outlook, books meetings, manages tasks, and records meetings — the follow-through that stops at the chat with Copilot.
- Builds the workflow by interviewing you. Tell Carly “when an opportunity moves to Negotiation, draft a recap email to the account owner and create a follow-up task” in plain English; it interviews you and builds it — no admin center, no Dataverse, no prompt engineering.
Carly connects to 200+ tools across 40+ categories natively, plus any other tool via your own API key — paste it on carlyassistant.com/integrations. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations.
Microsoft 365 Copilot vs Carly
| Microsoft 365 Copilot (Salesforce) | Carly | |
|---|---|---|
| Answer questions grounded in CRM data | Yes (connector, read-only) | Yes |
| Search Salesforce records in Microsoft 365 | Yes | Via the integration |
| Update / create records in Salesforce | Only via Sales agent (extra license) | Yes, natively |
| Log activity, create tasks in Salesforce | No (connector) | Yes |
| Objects reachable | 5 standard (connector) | Full API scope |
| Acts on Salesforce triggers / events | No | Yes |
| Monday pipeline digest, on schedule | No | Yes |
| Sends email as part of the flow | No (drafts only, in Sales agent) | Yes (Gmail + Outlook) |
| Works while laptop is closed | No (session-bound) | Yes (cloud, 24/7) |
| Setup | Admin center + connector (+ Sales agent for writes) | Describe it in plain English |
| Pricing | Microsoft 365 Copilot license per user | AI agents from $35/mo |
Copilot’s Salesforce connector is a grounding layer that pulls CRM context into your chats. Carly is a teammate that acts on Salesforce events as they land.
Frequently Asked Questions
Does Microsoft 365 Copilot work with Salesforce?
Yes, for reading. Microsoft ships an official Salesforce CRM Copilot connector that indexes Account, Contact, Opportunity, Lead, and Case records into Microsoft Graph so Copilot and Microsoft Search can answer questions grounded in your CRM data. It’s read-only — it surfaces and searches records but doesn’t write anything back to Salesforce.
Can Microsoft 365 Copilot update or create records in Salesforce?
Not through the standard connector. Write-back exists only through the separate Sales agent (formerly Sales Copilot / Viva Sales), which uses a Power Platform connector to view, update, and create records inside Outlook and Teams. It requires a per-user Microsoft 365 Copilot license, a Power Platform connected app in Salesforce, and a Dataverse environment — and every edit is a person acting in a session.
How do I connect Copilot to Salesforce?
A tenant admin adds the connector in the Microsoft 365 admin center → Copilot → Connectors → Salesforce CRM, authenticates to Salesforce, configures the crawl and custom fields, sets the access model, and runs a full crawl. See Microsoft’s deployment guide. Full crawls consume Salesforce API quota, so schedule them off-peak.
Can Copilot react to a new Salesforce lead or a stalled deal automatically?
No. Neither the connector nor the Sales agent fires on Salesforce events — Copilot answers when you prompt it, and the Sales agent updates a record when someone clicks. For “when a lead lands, route it and email the owner” or “when a deal stalls, nudge the rep,” you need a trigger-based assistant like Carly, which integrates natively with Salesforce and runs in the cloud around the clock.
More: Best AI CRM tools · Best AI agents for productivity · Claude + Salesforce · ChatGPT + Salesforce
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
