Salesforce Data 360 integration with OneLake (Preview)

A customer reports a missing delivery. The service case is in Salesforce, while the shipping and returns records are in Microsoft Fabric. Before a team can decide what to do next, it needs to connect those two views of the same customer experience.

For many organizations, answering questions like this still means exporting customer data, building ingestion pipelines, and maintaining another copy for analytics. Every additional handoff adds work for data teams and another dataset to secure and reconcile. Business teams wait for a complete picture while customer decisions move ahead. 

Zero-copy file sharing offers a different approach by making source data available where it is needed for analysis, without first building a separate ingestion copy. The data is always current. This makes it easier to connect customer context with the financial, operational, and product information that gives it meaning. 

Introducing Salesforce Data 360 integration with OneLake 

Salesforce Data 360 Integration with OneLake is now available in preview. Using OneLake Shortcuts, organizations can make Salesforce Data 360 data available in a Fabric and query them alongside enterprise data. Salesforce Data 360 remains the source, while Microsoft OneLake brings the analysis together. 

Those shortcuts reference the data in Salesforce Data 360 rather than importing a separate copy into the lakehouse. Further, the data is always current without requiring you to do any additional refresh. Teams can use the lakehouse, warehouse, and other Fabric Engines to explore customer data, join it with other enterprise tables, and develop analytics using familiar Fabric experiences, including SQL and Spark. Key benefits include: 

• Less integration work. Reference shared Salesforce data without building and maintaining a separate ingestion pipeline just to make it available in Fabric. 
• More complete business insight in real time. Bring customer cases, accounts, and opportunities represented in shared Data Lake Objects into analysis with orders, financial transactions, and operational records in real time. As data is available in Data 360, it is immediately available in OneLake. 

Once you have the data in OneLake, you can target the following use cases: 

• Customer retention analysis using Spark. Use Fabric notebooks to prepare features from shared customer data and operational history for churn or propensity models, subject to the organization's data-use and access policies. 
• Customer profitability Dashboards. Combine shared customer and account Data Lake Objects with financial data in OneLake to examine revenue, service costs, and margin together. Build Power BI reporting on an appropriately configured semantic model. 
• Churn Prediction. OneLake is integrated with Microsoft Foundry. Salesforce Data 360 data can be used with Microsoft Foundry to build ML models to predict churn. 
• Ask questions about your data. Build Ontologies with Salesforce Data 360 and ask questions using Data Agents that will respond to context established with Ontologies. 

Getting started 

Prerequisites 

You need Salesforce Data 360 access with the Data Cloud Architect permission set and an edition that supports data sharing. Identify the Data Lake Objects to share and prepare a Fabric workspace with a lakehouse and permission to create table shortcuts. 

Decide on an authentication method supported by the connection: Use organizational account for testing and prototyping. Use Service principal method for production applications. If you use a service principal, register the application in Microsoft Entra ID and prepare the required credential. 

Configure Salesforce Data 360 shortcuts 

Prepare the Salesforce share in Salesforce Data 360: Create a data share containing the required Data Lake Objects. Create a Microsoft OneLake data share target using the Microsoft Entra tenant ID and the appropriate identity's object ID, then link the share to that target. 

Figure: Creating a data share in Salesforce Data 360

Create a Shortcut in Fabric: In the destination lakehouse, select Get data > New table shortcut > Salesforce Data 360. Use the target's Tenant Endpoint as the Salesforce instance URL and its Core Tenant ID as the Salesforce org ID, then configure authentication. Choose the shared Data Lake Objects, save the shortcuts, and query a selected object. Confirm that the target is linked in Salesforce and test access with the intended Fabric users and workloads. 

Figure: Creating a Salesforce Data 360 shortcut using the share

During preview, only Data Lake Objects with the _dll extension is supported. Data Model Objects, Calculated Insight Objects, and schema-level shortcuts are not supported. 

We are excited to see what you build 

Salesforce Data 360 Integration with OneLake brings customer context closer to the enterprise data that helps teams act on it. By replacing a separate ingestion step with shared access through shortcuts, organizations can simplify the path from a business question to analysis while making access boundaries explicit. This integration advances the Microsoft Fabric and OneLake vision: make data easier to use together without requiring every source to move into one place. Salesforce Data 360 Shortcuts documentation provides you detailed information to get started.

Share your feedback and use cases in the Microsoft Fabric Community. Your experience will help shape what comes next as we continue connecting customer data with enterprise analytics.