In this tutorial, you'll learn how to implement Cross-Tenant Delegated OneLake Shortcuts in Microsoft Fabric to securely access and share data between two different Microsoft Fabric tenants without physically copying or replicating the data.
Microsoft Fabric allows organizations to share data across tenants while maintaining control over their original data. Using cross-tenant delegated OneLake shortcuts, a consumer tenant can access selected data from a producer tenant through a shortcut in its own lakehouse.
We'll walk through the complete implementation, starting with the architecture and authentication model, followed by a practical demonstration using two separate Microsoft Fabric tenants.
What You'll Learn in This Tutorial
Introduction to Cross-Tenant Delegated OneLake Shortcuts.
Understanding the producer and consumer tenant architecture.
How delegated authentication works in Microsoft Fabric.
Difference between delegated authentication and pass-through authentication.
Creating two separate Microsoft Fabric tenants and workspaces.
Creating Lakehouses in producer and consumer tenants.
Uploading CSV files to the producer Lakehouse.
Registering an application in Microsoft Entra ID.
Creating a service principal and client secret.
Configuring service principal access to the producer workspace.
Setting up OneLake security roles and read permissions.
Creating a Cross-Tenant Microsoft OneLake Shortcut.
Configuring service principal authentication in the consumer tenant.
Connecting to data stored in another organization's OneLake.
Transforming CSV files into Delta tables.
Monitoring shortcut synchronization and transformation.
Creating a Power BI semantic model.
Changing column data types and creating calculated columns.
Building a Power BI report using cross-tenant data.
Understanding how newly uploaded files become available through the shortcut.
Architecture Overview
The implementation uses two Microsoft Fabric tenants:
Producer Tenant: Owns the original data, manages the Lakehouse, and controls access permissions.
Consumer Tenant: Connects to selected data from the producer tenant using a Cross-Tenant Delegated OneLake Shortcut.
The connection uses a service principal registered in Microsoft Entra ID. OneLake security permissions ensure that only the selected data is accessible to the consumer.
Who Should Watch This Video?
This tutorial is useful for:
Microsoft Fabric developers
Data engineers
Power BI developers
Azure cloud architects
Data architects
Enterprise data platform engineers
Professionals working with multi-tenant data architectures
If you're working with Microsoft Fabric and need to share data securely across organizational boundaries without maintaining duplicate datasets, this tutorial will help you understand the architecture and implementation.
Watch the complete demonstration to see how data moves from the producer tenant to the consumer tenant through a delegated OneLake shortcut.
If you find this tutorial helpful, please like, share, comment, and subscribe for more Microsoft Fabric, Power BI, Azure, and data engineering tutorials.
Join the conversation! Your thoughts help the community grow.