If you manage Salesforce and your organization also uses Microsoft 365, you have probably heard that Copilot for Sales can surface Salesforce data inside Outlook and Teams. That part is true. What is less well understood is how limited that surfacing actually is, and why many users still get incomplete AI answers even after the connector is set up.

This article covers exactly what Microsoft 365 Copilot for Sales, which Microsoft now also refers to as the Sales agent and which was previously called simply Copilot for Sales, can and cannot pull from Salesforce. It also covers the permissions and custom object questions that come up most often in CRM admin forums, and the deeper cross-system gap that the connector alone does not solve.

For the full breakdown of all Microsoft Copilot products, data limits, permissions, and FAQs, see the complete guide here.

Key point: Microsoft 365 Copilot for Sales connects to Salesforce and surfaces CRM data inside Outlook and Teams. But out of the box it covers only a few standard objects, it is centered on communication workflows, and it does not extend to your Dynamics 365 ERP and operational data.

First, Which Copilot? The Versions That Get Confused

Part of the confusion is that Microsoft ships many products under the Copilot name, and they see very different data. Copilot for Sales, which Microsoft now also calls the Sales agent, is only one of them, and it is licensed as part of Microsoft 365 Copilot rather than sold separately. Here is how the versions are most likely to compare.

Copilot version	Where do you use it	What it can see	Sees Salesforce CRM and Dynamics 365 ERP together?
Microsoft Copilot (free)	Web, Windows, Edge	The public web only. No access to your business data.	No
Microsoft 365 Copilot Chat	Teams, Outlook, web chat	The web, plus anything you paste or upload into the prompt. No work data by default.	No
Microsoft 365 Copilot (paid add-on)	Word, Excel, Outlook, Teams	Your Microsoft 365 work content through Microsoft Graph: files, emails, chats, meetings.	No
Copilot for Sales (Sales agent)	Outlook and Teams	One connected CRM at a time, either Salesforce or Dynamics 365 Sales.	No, CRM only
Copilot for Service	Outlook, Teams, service desk	One connected service or CRM system: Salesforce, Dynamics 365, ServiceNow, or Zendesk.	No, service side only
Copilot in Dynamics 365 (Sales, Business Central, Finance)	Inside each Dynamics 365 app	That app’s own CRM or ERP data that the user can access.	No, one app only

The pattern in the last column is the point. Each Copilot is scoped to a single slice of data, and none of them, on its own, sees your Salesforce CRM and your Dynamics 365 ERP together. That is the cross-system gap this article keeps coming back to.

Copilot version details are drawn from Microsoft Learn and the Microsoft 365 Copilot pricing page; edition names and prices are current as of July 2026 and change frequently.

What Microsoft 365 Copilot for Sales Can Pull From Salesforce

When connected to Salesforce, Copilot for Sales surfaces the following inside Outlook and Teams:

• Accounts, contacts, and opportunities, plus activities such as emails and meetings saved to Salesforce
• Email and meeting data captured and synced to Salesforce
• AI-drafted recap emails and follow-up tasks based on Salesforce records
• Live CRM context visible alongside your inbox

This is genuinely useful for sales reps who live in Outlook. It removes the need to switch between Salesforce and email constantly, and it keeps CRM records up to date without manual logging.

What It Cannot Pull From Salesforce

This is where the gap matters for CRM administrators and RevOps teams.

The default scope is a handful of standard objects. Out of the box, Copilot for Sales surfaces the contact, account, and opportunity records, with leads available in preview. Everything else has to be added deliberately by an administrator.

Custom objects require configuration, and there is a cap. A CRM administrator can add custom Salesforce objects to Copilot for Sales, but only up to 10 record types in total. So if your Salesforce instance uses many custom objects for contracts, projects, support cases, or other business processes, only a chosen 10 record types can ever appear in Outlook or Teams, and only after an admin configures them.

Custom fields are configurable, up to a limit. Admins can add both standard and custom fields to each record form, up to 40 fields per form. Beyond that, additional fields, including custom ones your team relies on, will not appear. For Salesforce specifically, an admin should add only fields that all users can access, or the record will not display for a user who lacks access to one of those fields.

Primarily an Outlook and Teams experience. Copilot for Sales lives mainly in Outlook and Teams, and it also surfaces in Microsoft 365 Copilot chat. It is centered on communication and selling workflows rather than document work, and it does not give the Copilot experiences inside Dynamics 365 ERP apps any Salesforce visibility.

No Dynamics 365 ERP or operational data. Copilot for Sales connects to one CRM at a time, either Salesforce or Dynamics 365 Sales. When it is connected to Salesforce, it works from your Salesforce CRM data plus your Microsoft 365 data. It has no connection to Dynamics 365 Finance, Business Central, or other operational and ERP records.

Permissions and Field-Level Security

This comes up frequently in Microsoft community forums and Salesforce admin discussions. The short answer is: Copilot for Sales respects Salesforce’s existing permission model.

If a user does not have access to a field or record in Salesforce directly, Copilot will not show it to them either. Field-level security, record-level sharing rules, and profile-based permissions all apply. This means:

• Users with restricted Salesforce profiles will see less data in Copilot than users with full access
• Records shared only with specific teams or roles will not appear for users outside those groups
• Fields hidden by field-level security will not surface in Copilot even if the record is visible

If your Salesforce instance has a complex permission structure, it is worth auditing user access alongside any Copilot for Sales rollout. Users who expect to see full account context may see much less than expected, and the reason will not be obvious without checking Salesforce permissions directly.

Why AI Answers Still Feel Incomplete After Setup

This is the most common frustration in forums after the connector is configured. Users expect to ask Copilot about an account and get a complete picture. Instead, they get a partial view, and they are not sure why.

 

Part of the problem starts with the data itself. In Validity’s State of CRM Data Management study, 76% of organizations said that less than half of their CRM data is accurate and complete. Any AI reading those records, Copilot included, inherits whatever is missing.

There are two reasons this happens.

First, the configuration and cap limits. If your Salesforce instance has significant customization, the data that appears in Outlook and Teams reflects only the record types and fields an admin has configured, within the 10-object and 40-field caps. Anything beyond that is invisible to Copilot.

Second, the cross-system gap. Even if your Salesforce data is surfacing correctly in Outlook and Teams, Copilot for Sales is still only working from the CRM side of the business. If your company also uses Dynamics 365 for order management, invoicing, finance, or customer service, that operational data is not visible to Copilot for Sales. And it is not visible to Salesforce Einstein AI either.

The result is two AI tools giving answers simultaneously, each from half the business data, and neither designed to tell you what it cannot see.

The Cross-System Gap and What It Means for RevOps

For RevOps teams managing both Salesforce and Dynamics 365, the connection between Salesforce and Outlook is a useful workflow tool. It is not a solution to the underlying data split.

A sales rep using Copilot in Outlook can see Salesforce pipeline context. They cannot see that the same customer has three outstanding invoices in Business Central or that a support escalation was logged in Dynamics last week. That context sits in a different system, and no connector between Salesforce and Outlook changes that.

When the two systems are synchronized, the picture changes. CRM data from Salesforce and operational data from Dynamics 365 share a common record, and the AI tools on both sides draw on a fuller view of the customer. You do not reconfigure Copilot or Einstein to get there; the only thing that changes is how complete the record underneath them is.

Analysts are pointing the same way. In BARC’s Data, BI and Analytics Trend Monitor 2026, a survey of 1,579 organizations worldwide, data quality returned to the number one priority, ahead of AI itself. The teams getting value from these tools are the ones treating connected, trustworthy data as the foundation, not the AI feature on top of it.

How to Close the Visibility Gap

So what actually closes the gap? Not another connector between Salesforce and Outlook, but synchronizing the two systems of record themselves, so that a customer’s CRM history and their Dynamics 365 orders, invoices, and service activity live in one connected picture. Once the data is complete and consistent on both sides, every Copilot, and Salesforce Einstein, works from the same full view of the customer rather than half of it. That synchronization can be built as a custom integration, run through a general-purpose iPaaS, or handled by a purpose-built connector. Rapidi is one such option: it keeps Salesforce and Microsoft Dynamics 365 in continuous two-way sync without custom code, so the data your AI tools read stays both complete and current.

Questions CRM Admins Should Ask Before Rolling Out Copilot for Sales

• Which standard Salesforce objects does your team rely on most, and are they within the default set of contact, account, and opportunity, or will they need to be added?
• How many custom objects and custom fields does your Salesforce instance use? With caps of 10 record types and 40 fields per form, heavy customization means real trade-offs about what to surface.
• What does your Salesforce permission model look like? Users with restricted profiles will see less than expected.
• Does your company also use Dynamics 365 for ERP or operations? If so, the connector alone does not give Copilot a complete view of the customer.
• Are there plans to synchronize Salesforce and Dynamics 365 data? Without synchronization, the cross-system gap will persist regardless of which AI tools are in use.

If your Salesforce instance has significant customization, audit what Copilot can actually see before rolling it out to your sales team. The gap between what users expect and what appears in Outlook is one of the most common frustrations with Copilot for Sales, and it is avoidable.

If Copilot is part of your sales stack, the place to begin is not the AI settings but the connection between Salesforce and Dynamics 365 underneath them. See what that integration involves.

Frequently Asked Questions

Is Copilot for Sales the same as Microsoft 365 Copilot?

No. Copilot for Sales, which Microsoft now also calls the Sales agent, is a role-based experience that surfaces CRM data in Outlook and Teams, and it is licensed as part of Microsoft 365 Copilot rather than sold separately. Microsoft 365 Copilot is the broader assistant that works across Word, Excel, Outlook, and Teams.

Does Copilot for Sales work with Salesforce or only Dynamics 365?

It works with either, one CRM at a time. Copilot for Sales connects to Salesforce Sales Cloud or Microsoft Dynamics 365 Sales. It does not connect to Dynamics 365 ERP systems such as Finance or Business Central.

Can Copilot for Sales show Salesforce custom objects and fields?

Yes, but not by default. An administrator can add custom objects, up to a total of 10 record types, and up to 40 fields per form, including custom fields. Anything beyond those limits will not appear in Outlook or Teams.

Why does Copilot still give incomplete answers about a customer?

Two reasons. It only sees the CRM side of the business, so operational data in Dynamics 365 stays invisible unless the two systems are integrated. And it can only reflect the CRM data that exists; when records are thin or inaccurate, the AI inherits those gaps.

Beate Thomsen is co-founder of Rapidi, which has specialized in Salesforce and Microsoft Dynamics 365 data integration for more than two decades. If you are weighing the cost of the manual reconciliation described here, Rapidi offers a free AI integration ROI calculator to help you put a number on it.

The post What Copilot for Sales Shows From Salesforce, and What It Misses appeared first on CRM Software Blog | Dynamics 365.