Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

leonardocanalit

Enable Cross-Tenant OneLake / Lakehouse Transfer with Microsoft-Supported Validation

Submitted by on ‎04-21-2026 12:00 PM

Summary

Currently, Microsoft Fabric Lakehouses store data in OneLake, logically centralized by region and capacity. However, there is no Microsoft-supported mechanism to transfer or migrate Lakehouse data across tenants, even when both tenants are owned or controlled by the same organization.

This idea proposes a Microsoft-managed, support-driven cross-tenant transfer capability, where access to both tenants can be validated and a secure migration can be performed.

Problem Statement

Many organizations operate multiple Microsoft Entra tenants due to:

  • Mergers and acquisitions
  • Regional or regulatory separation
  • Divestments or tenant consolidations
  • Managed services and partner-led implementations

Today, moving Fabric Lakehouses or OneLake data between tenants requires manual, unsupported, or fragile workarounds, such as:

  • Exporting and re-ingesting data
  • Custom pipelines with duplicated storage costs
  • Breaking lineage and governance metadata

Additionally:

  • Governance objects (lineage, shortcuts, permissions) are lost
  • Support cannot officially validate or assist with cross-tenant migrations
  • Large datasets make re-ingestion slow, risky, and expensive

Proposed Solution

Enable a Microsoft-supported cross-tenant OneLake transfer process, initiated via a support ticket or controlled workflow, with the following characteristics:

  • Validation of administrative access to both source and target tenants
  • Same-region or approved cross-region transfers
  • Secure, audited data movement at the OneLake level
  • Optional inclusion of:
    • Lakehouse metadata
    • Directory structure
    • Table definitions
    • Shortcuts and references (where applicable)

This could be implemented as:

  • A Microsoft Support-assisted operation
  • A Fabric Admin or Tenant-level migration workflow
  • Or a future Fabric-managed migration service

Business Value

  • Reduces risk and cost for tenant consolidation projects
  • Enables cleaner M&A and divestment scenarios
  • Preserves governance, lineage, and Fabric-native structures
  • Avoids data duplication and unnecessary storage costs
  • Aligns with OneLake’s vision as a unified, logical data lake

Who Would Benefit

  • Enterprises with multiple Entra tenants
  • Partners and MSPs managing Fabric for multiple customers
  • Organizations with M&A activity
  • Regulated industries needing structured tenant separation

Additional Notes

This feature would not need to be self-service initially.
A controlled, support-driven process would already deliver significant value while maintaining security, auditing, and governance guarantees.

Status: New
Comment