
In Short: What Was Announced?
On 17 November 2026, at Microsoft Ignite, Microsoft and Salesforce announced Copilotforce, a set of integrations that bring Salesforce customer data into Microsoft's data and AI tools, and Microsoft data into Salesforce. For data teams, two parts matter most:
- OneLake to Data 360 data federation: generally available. Salesforce Data 360 can query data in Microsoft Fabric's OneLake in place, without copying it.
- Salesforce Data 360 shortcut: public preview. Curated Data 360 customer data can be shared into OneLake for Power BI, Fabric and AI agents.
Two further parts sit on the Copilot and Teams side:
- Salesforce in Copilot: public preview (beta) from 17 November, with 38+ prebuilt sales skills
- Sales Cloud in Teams: pilot with enterprise customers, with open beta "later this year"
No pricing was announced.
Why This Matters
Most organisations that run Salesforce also keep finance, product, supply chain or service data somewhere else, and increasingly that somewhere is Microsoft Fabric. Until now, combining the two meant copying data: Salesforce extracts into a lakehouse for Power BI, or Fabric data loaded back into Salesforce for segmentation and service. Every copy is another pipeline to build, schedule, monitor and secure.
Copilotforce replaces some of that copying with sharing in place. Our earlier comparison, Salesforce Data Cloud vs Microsoft Fabric, argued the two were never a straight choice. This announcement makes that official: each platform can now read the other's data where it lives.
Direction 1: Fabric Data Into Salesforce (GA)
Data federation lets Salesforce Data 360 run queries against OneLake. The data stays in Fabric. Salesforce users can see, for example, a customer's invoices, contract margin or product usage from Fabric next to their CRM record.
This is the part you can use in production now. What to check before switching it on:
- Which OneLake tables you expose. Federate curated gold-layer tables, not raw landing data. Salesforce users will treat whatever appears as correct.
- Security on both sides. Fabric permissions control what the federated connection can read. Salesforce permissions then control who sees it in Data 360. Map them deliberately.
- Capacity. Queries from Data 360 still run against your Fabric data, so heavy federated use shows up on your Fabric capacity. Watch the Capacity Metrics app for the first few weeks.
Direction 2: Salesforce Data Into OneLake (Preview)
The Salesforce Data 360 shortcut works like other OneLake shortcuts: curated Data 360 customer data appears in OneLake without a copy pipeline. From there, Power BI semantic models, Fabric notebooks and Fabric data agents can use it.
Because it is in public preview, treat it as something to test, not to build your board pack on. For production reporting today, the routes in our Salesforce to Fabric integration guide still apply: the Fabric Salesforce connectors in pipelines, Copy job or Dataflow Gen2.
Salesforce in Copilot and Teams
The other half of Copilotforce is about where salespeople work. Salesforce in Copilot is a plugin with 38+ prebuilt sales skills, available in public preview (beta) from 17 November. Sales Cloud in Teams is in pilot with enterprise customers, with an open beta promised later this year.
These matter to data teams indirectly. If Copilot answers questions about pipeline and accounts using Salesforce, and about revenue and margin using Fabric IQ and Power BI semantic models, then both sources need consistent customer IDs and definitions. Copilot will happily put two conflicting numbers side by side.
What to Do Now
1. Agree the customer key. Federation and shortcuts both assume you can join Salesforce accounts to Fabric data. If your ERP and CRM customer IDs do not match cleanly, fix the mapping table first. 2. Pick one federated use case. A common first one is showing finance data, such as overdue invoices or margin, on the Salesforce account. 3. Test the shortcut in a non-production workspace. Compare it with your current Salesforce extract for freshness, completeness and capacity use. 4. Check governance. Salesforce data in OneLake is subject to your Fabric governance, so label it in the OneLake catalog and apply sensitivity labels. 5. Wait for GA before retiring pipelines. Keep your existing extracts running until the shortcut is generally available.
Sources and Further Reading
- Microsoft and Salesforce announce Copilotforce (press release, 17 November 2026)
- Microsoft Ignite 2026 Book of News
- Related: How to integrate Salesforce with Microsoft Fabric, Salesforce Data Cloud vs Microsoft Fabric, OneLake shortcuts
Frequently asked
Copilotforce is the name Microsoft and Salesforce gave to a set of integrations announced on 17 November 2026 at Microsoft Ignite. It covers data sharing between Salesforce Data 360 and Microsoft Fabric's OneLake, Salesforce in Microsoft Copilot, and Sales Cloud in Microsoft Teams.
Yes. Data federation from Microsoft OneLake into Salesforce Data 360 is generally available. Data 360 queries OneLake data in place, so finance, product or operational data held in Fabric can be used in Salesforce without copying it.
Yes, in preview. The Salesforce Data 360 shortcut, in public preview since November 2026, shares curated Data 360 customer data into OneLake, where Power BI, Fabric notebooks and data agents can use it. For production today, the established routes are Fabric connectors and pipelines from Salesforce.
Yes. Salesforce Data 360 is the current name for the product previously called Salesforce Data Cloud. Older Microsoft and Salesforce documentation still uses the Data Cloud name.
Microsoft and Salesforce did not announce pricing for Copilotforce. The press release says regional availability and customer access are governed by applicable customer agreements, so expect existing Salesforce and Microsoft licences to apply. Fabric queries still consume Fabric capacity.


