Microsoft Copilot works with Salesforce, but only in limited ways, and the answer depends entirely on which Copilot product you are using. Microsoft 365 Copilot does not natively read Salesforce records. Sales in Microsoft 365 Copilot (previously called Copilot for Sales) can surface Salesforce CRM data inside Outlook and Teams. Copilot experiences inside Dynamics 365 apps work from Dynamics and Dataverse data only, unless Salesforce data is synchronized first.
If your company runs both Salesforce and Dynamics 365, here is what is actually happening: you have multiple AI layers running simultaneously, and each one is working from an incomplete picture of your business. Copilot experiences in Dynamics cannot see your Salesforce pipeline. Salesforce Einstein AI cannot see your Dynamics financials. Neither flags the gap, because neither knows what it is missing.
Key takeaway: The real question is not whether Copilot "works with" Salesforce in a technical sense. It is whether your AI tools have a complete enough view of your business to give you answers you can actually act on. For most companies running both platforms without integration, the answer is no.
This article covers exactly what each Microsoft Copilot product can and cannot see, what that costs your business in practice, and the most direct way to give your AI tools a complete view of your customer and operational data.
Which Copilot Are We Talking About?
This is where most articles on this topic lose people. "Microsoft Copilot" is not one product. Microsoft has built Copilot as a set of experiences across different apps and platforms, each with its own data access and scope. Before getting into what it can and cannot see, it helps to know which product is which.
| Copilot Product |
Where It Runs |
Default Data Source |
Salesforce Access |
| Microsoft 365 Copilot |
Word, Excel, Outlook, Teams, OneDrive, SharePoint |
Microsoft 365 tenant data |
None natively |
| Sales in Microsoft 365 Copilot (previously Copilot for Sales) |
Outlook and Teams |
Microsoft 365 + live CRM records |
Yes, via connector (Outlook and Teams only) |
| Copilot experiences in Dynamics 365 apps |
Dynamics 365 Sales, Customer Service, Business Central, Finance, Field Service, and others |
Dynamics 365 and Dataverse |
None natively |
| Dynamics 365 AI agents |
Specific Dynamics 365 workflows |
Dynamics 365 and Dataverse |
None natively |
| Salesforce Einstein AI |
Salesforce platform |
Salesforce CRM data |
Native (Salesforce only) |
Microsoft has updated the naming over time, so this article uses "Sales in Microsoft 365 Copilot" for the current experience and notes "Copilot for Sales" where that older name is still widely searched. The core point holds regardless of naming: only one product in this list has a native Salesforce connection, and it is scoped to Outlook and Teams only.
What Data Can Each Copilot Product Actually See?
Direct answer: Each Copilot product is bounded by the platform it lives in. Microsoft 365 Copilot sees Microsoft 365 data. Copilot experiences inside Dynamics 365 apps see Dynamics and Dataverse data. Sales in Microsoft 365 Copilot is the one exception: it can pull live Salesforce CRM records into Outlook and Teams, but that connection does not extend to the rest of the Microsoft product suite.
Microsoft 365 Copilot
Can see:
-
Emails and calendar events in Outlook
-
Documents and spreadsheets in OneDrive and SharePoint
-
Teams messages and meeting recordings
-
Microsoft 365 user activity across the tenant
Cannot see:
-
Salesforce leads, opportunities, contacts, or activity history
-
Dynamics 365 orders, inventory, or financials
-
Any data stored outside the Microsoft 365 tenant
Sales in Microsoft 365 Copilot (previously Copilot for Sales)
This is the product most people mean when they ask "does Copilot work with Salesforce?" It connects to Salesforce and surfaces live CRM data inside Outlook and Teams. Key features include automatic capture of emails and meetings into Salesforce, live CRM data visible alongside your inbox, and AI-drafted recap emails and follow-up tasks based on Salesforce records.
As Microsoft's own documentation notes, the integration depth is stronger with Dynamics 365 than with Salesforce, but Salesforce customers using Microsoft 365 get meaningful value from these communication-side AI features.
Can see (when connected to Salesforce):
-
Accounts, contacts, opportunities, and activities in Salesforce
-
Email and meeting data captured and synced to Salesforce
-
CRM context surfaced inside Outlook and Teams
Cannot see:
-
Salesforce custom objects beyond standard CRM records (more on this below)
-
Data outside Outlook and Teams, it does not extend to Word, Excel, or other Microsoft 365 apps
-
Dynamics 365 financial, ERP, or operational data
Copilot experiences inside Dynamics 365 apps
Microsoft has built Copilot into individual Dynamics 365 applications: Sales, Customer Service, Business Central, Finance, Field Service, Supply Chain, and others. Each experience is scoped to that app's data in Dynamics 365 and Dataverse, or finance and operations environments where relevant.
Can see:
-
Customer records inside Dynamics 365
-
Orders, invoices, and inventory in Business Central
-
Financial data in Finance and Operations
-
Sales and service data in Dynamics 365 Sales and Customer Service
Cannot see:
Does Sales in Microsoft 365 Copilot work with Salesforce custom objects?
This comes up often in community forums, and the short answer is: not well, by default. Sales in Microsoft 365 Copilot is built around standard Salesforce objects: accounts, contacts, opportunities, and activities. Custom objects, custom fields beyond a limited set, and non-standard data structures are not surfaced automatically. If your Salesforce instance has significant customization, what appears in Outlook and Teams will reflect only a fraction of your actual CRM data. For teams that have built out Salesforce heavily over the years, this is a real limitation worth knowing before rollout.
The Copilot Blind Spot: What It Costs Your Business
Direct answer: When Salesforce and Dynamics 365 are not connected, every AI tool in your stack gives answers that are structurally incomplete. The problem is not that the AI is wrong. It is that neither tool knows what it cannot see, so neither flags the gap.
Here is what this looks like in practice.
A sales rep is preparing for a call with a key account. They ask the Copilot experience in Dynamics 365 Sales: "What is the current status of this account?" Copilot pulls the order history, invoice status, and support tickets from Dynamics. But the most recent email chain, the open opportunity, and the renewal discussion are all logged in Salesforce. Copilot cannot see any of it.
The same problem runs in reverse. A Salesforce user asks Einstein AI to summarize an account before a meeting. Einstein sees the pipeline and the recent emails logged in Salesforce. It cannot see that the customer has three outstanding invoices in Business Central, or that they called your support team last week with a product issue tracked in Dynamics.
Both AI tools give answers. Both answers are incomplete. And neither tool flags the gaps, because neither knows what it does not know.
What this looks like at scale
Thames Water, the UK's largest water utility, was running exactly this setup. Salesforce and Microsoft Dynamics NAV operated in parallel without proper synchronization. Teams were manually reconciling records, delayed invoicing was common, and reporting was inconsistent. Laurence Sidney, who led the project, described the wider problem: "Every division has at least 10 different programs trying to do something and of course that leads to duplication of effort and inefficiency."
They had previously evaluated MuleSoft but found it would still require substantial custom development on the Dynamics side, the Salesforce side, and inside MuleSoft itself. After switching to Rapidi, synchronization runs every 10 minutes, manual reconciliation is gone, and the integration structure is reusable across future divisions without additional development work. As Paul Ison from KE Consulting put it: "There's no development work whatsoever. It's an out-of-the-box solution."
Researchers at IESGP describe this as an "AI completeness" problem: the extent to which AI can understand and act on the entirety of an organization's operational reality, not just one platform's slice of it. Running Salesforce and Dynamics 365 without integration fails that test.
According to Microsoft's 2026 Work Trend Index, there are now 33 million active Copilot users, with over 90% of Fortune 500 companies using the platform. Users complete tasks 20 to 55% faster and save one to four hours per week. Those gains assume Copilot has complete data to work from. When it does not, the speed improvement produces faster incomplete answers.
The downstream costs are concrete:
-
Sales reps making calls without the full account picture
-
Finance teams generating reports that exclude CRM pipeline data
-
Customer success managers are missing signals sitting in the other system
-
Leadership receiving AI summaries that are structurally incomplete
What happens when Salesforce and Dynamics 365 are not connected?
When the two systems run in isolation, several things happen across the business simultaneously.
Data is entered twice. A new customer is created in Salesforce when the deal closes, and then manually re-entered in Dynamics when the order is processed. Every change to a record in one system requires a manual update in the other.
Reports are manually assembled. Getting a full view of an account means pulling data from two platforms, exporting to spreadsheets, and combining them by hand. This takes time and introduces errors.
AI answers miss half the context. Copilot experiences in Dynamics and Einstein AI each give answers based on what they can see. The answers are not wrong; they are just incomplete.
Teams work from different versions of the truth. Sales sees the Salesforce version of a customer. Finance sees the Dynamics version. When these differ, and they often do, it creates friction, delays, and occasionally lost revenue.
Rapidi customers describe exactly this before they connected their systems. Homespice Décor reported saving half a full-time job per week after integration. Expedeon's team lead said: "I've got 60% of my former day back." These are not productivity improvements from switching tools. They are what happens when data stops living in silos and starts flowing across the business.
What Copilot Sees With and Without Salesforce Integration
Direct answer: Integration changes what your AI tools can see, not how they work. Once Salesforce and Dynamics 365 share synchronized data, Copilot experiences in Dynamics draw on the full picture instead of half of it.
| Scenario |
What Copilot Sees |
Quality of AI Answers |
| Salesforce only |
CRM data only |
Incomplete, no ERP or financial context |
| Dynamics 365 only |
ERP and financial data only |
Incomplete, no CRM or pipeline context |
| Salesforce surfaced in Outlook and Teams via Sales in Microsoft 365 Copilot |
Standard CRM records in Outlook and Teams only |
Partial, scoped to communication workflows |
| Both Salesforce and Dynamics 365, not synchronized |
Each AI sees only its own system |
Both incomplete, no shared view of the customer |
| Both synchronized via Rapidi |
Full CRM and ERP data available across systems |
Complete, reflects the whole business |
The difference between the fourth and fifth row is not a feature upgrade. It is a structural change to what your AI can actually know.
How to Give Copilot Access to Salesforce Data
Direct answer: Connect Salesforce and Dynamics 365 through an integration platform. Once the two systems share a synchronized data set, Copilot experiences in Dynamics draw on the full picture. Integration changes what your AI tools can see, not how they work. Once Salesforce and Dynamics 365 share synchronized data, the underlying record is complete, so the answers your AI gives reflect the whole business, not just one platform's slice of it.
What is the fastest way to connect Salesforce and Dynamics 365?
Rapidi's no-code integration platform connects Salesforce and Dynamics 365 directly, using pre-built, production-tested templates that cover the most common data flows: accounts, contacts, orders, invoices, and more. No developers are required. The platform is configured through a visual interface, and the average implementation takes three to four weeks from kickoff to live.
Rapidi has been a Microsoft partner since 1987 and a Salesforce partner since 2007. That depth of experience in both ecosystems is built into the templates: the data mappings, field transformations, and error-handling logic reflect decades of real implementation work. The platform also supports hybrid and on-premise Dynamics 365 deployments, which cloud-only tools cannot serve.
Pre-built templates cover:
No-code setup. No developer resources needed to get started. Your IT team manages the integration without writing custom code.
Pre-built templates. The common data flows are already mapped. Implementation starts from a working baseline, not a blank page.
A real support team. Not a ticket queue. Rapidi's support team knows both platforms in depth and works directly with customers. The average customer relationship lasts three to six years.
Transparent pricing. No hidden costs or usage-based surprises. Rapidi's pricing tiers are clear up front.
Results from Rapidi customers
Dutco Tennant, a leading UAE enterprise, processes over 100 orders per day through the Rapidi connection between Salesforce and Dynamics 365 Finance. Before integration, data syncing between systems took days and errors in order and customer records were routine. After implementation, sync time dropped to hours and error rates fell significantly.
Kimberley Group connected their systems and reported: "Automated sales are up by 50% and delivery times are cut in half." ReadSoft put it plainly: "Critical business data is now always available, accurate and up-to-date."
Kevin Gilmore, Director of IT at Educate 360, summed it up: "Rapidi is the way to go. It is the most cost-effective solution on the market, and it just works."
Frequently Asked Questions
Does Microsoft 365 Copilot connect to Salesforce natively?
No. Microsoft 365 Copilot works within the Microsoft 365 ecosystem: Outlook, Teams, OneDrive, and SharePoint. It has no native connector to Salesforce and cannot read Salesforce CRM data without a third-party integration. Sales in Microsoft 365 Copilot is the exception; it connects to Salesforce but only surfaces data inside Outlook and Teams, not across the full Microsoft 365 or Dynamics 365 environment.
Is Copilot for Sales the same as Sales in Microsoft 365 Copilot?
They are the same product, different names. Microsoft rebranded Copilot for Sales to "Sales in Microsoft 365 Copilot" as part of its broader Copilot naming update. Both names refer to the product that connects to Salesforce or Dynamics 365 CRM and surfaces live CRM data inside Outlook and Teams. If you are searching for setup guides or documentation under the older name, you will find the same product.
Does Dynamics 365 Copilot read Salesforce data, or only Dynamics and Dataverse data?
Copilot experiences inside Dynamics 365 apps read Dynamics 365 and Dataverse data only. There is no native Salesforce connection. To give Dynamics 365 Copilot experiences access to Salesforce data, the two systems need to be synchronized through an integration platform. Once data flows between them, Copilot can draw on the full combined data set.
Why does Copilot show some Salesforce data in Outlook but not the full account picture?
This is one of the most common frustrations in Microsoft community forums. Sales in Microsoft 365 Copilot surfaces Salesforce data inside Outlook and Teams, but it is limited to standard CRM objects: accounts, contacts, opportunities, and logged activities. Custom objects, custom fields, and non-standard data structures do not appear automatically. The integration is also scoped to communication-side workflows, meaning Copilot helps with email drafts and meeting summaries but does not give you a full CRM view inside Microsoft 365.
What permissions or identity settings affect Salesforce data visibility in Copilot?
Sales in Microsoft 365 Copilot respects Salesforce's field-level security and record-level sharing rules. If a user does not have permission to see a field or record in Salesforce directly, Copilot will not show it either. If your Salesforce instance has complex permission structures, some users may see less data than expected in Copilot even after the connector is set up. It is worth auditing Salesforce permissions alongside any Copilot rollout.
What is the difference between Microsoft Copilot and Salesforce Einstein AI?
Both are AI assistants embedded in their respective platforms. Copilot draws on Microsoft ecosystem data and delivers broad productivity gains: Microsoft's 2026 data shows users completing tasks 29% faster overall, with 73% reporting increased productivity. Einstein AI draws on Salesforce CRM data and delivers stronger CRM-specific outcomes, with reported improvements including 27% higher sales productivity, 32% better lead conversion rates, and 25% shorter sales cycles. As one 2026 comparison analysis puts it: "Einstein generally delivers stronger CRM-specific predictive outcomes, while Copilot delivers broader productivity gains." Without integration, neither can deliver on the other's strengths.
Does integrating Salesforce and Dynamics 365 improve Copilot ROI?
Yes, directly. Integration does not change Copilot's capabilities; it changes what Copilot can see. For companies running both platforms, it is the single highest-leverage step to improving AI output quality. The productivity gains Microsoft reports, 20 to 55% faster task completion and one to four hours saved per week, depend entirely on the quality of data Copilot can access.
How long does it take to connect Salesforce and Dynamics 365?
With Rapidi, the average implementation takes three to four weeks from kickoff to a live, synchronized connection. The timeline depends on data model complexity, the number of entities being synchronized, and how much customization is required beyond the pre-built templates. Rapidi's team works with you through discovery, configuration, testing, and go-live.
Can a no-code tool connect Salesforce and Dynamics 365?
Yes. Rapidi is a no-code iPaaS platform built specifically for this connection. No developer resources are required. The platform uses pre-built templates for the most common data flows, and your IT team manages the integration through a visual interface without writing custom code.
Ready to Give Copilot the Full Picture?
The data your AI needs already exists. It is split across two systems. Connecting them is a defined, manageable project with a clear timeline and measurable results.
Rapidi has been connecting Salesforce and Microsoft Dynamics 365 for companies worldwide for over 30 years. The setup takes three to four weeks. No code to write, no long-term lock-in from opaque pricing. Contour Design has been a Rapidi customer through three generations of Microsoft Dynamics, from Dynamics C5, through NAV, and now on Dynamics 365 Business Central. As they put it: "This partnership has not only enhanced our operational capabilities but also improved our working efficiency and cooperation between teams around the world."
Book a demo and see exactly what synchronized data means for your business.
