I am seeking guidance on how to configure and use the LinkToFabric function across different tenants.

Cross-tenant use of Link to Fabric from Dataverse/Power Apps to a Fabric workspace in another tenant is not documented as a supported scenario in the provided content. The documented guidance assumes that the Dataverse/Power Platform environment and the target Fabric workspace are in the same Azure AD tenant.

From the available documentation:

• Link to Fabric is configured from Dataverse/Power Apps by creating a data connection to a Fabric workspace and then enabling the link so that Dataverse tables (and, by extension, D365FO data exposed via Dataverse) are synchronized into a Fabric lakehouse.
• When creating or managing the connection, the authentication options are:
  • Workspace identity
  • OAuth 2.0 / Organizational account
  • Service principal (application user in Dataverse)
• For the service principal option, the required parameters are:
  • Tenant ID: Azure tenant identifier
  • Client ID: Application (client) ID of the service principal
  • Key: Client secret or certificate
• The documentation describes adding the service principal as an application user in Dataverse and then using that identity to connect to the Fabric workspace. This flow is described only for a single-tenant setup.

Because there is no explicit cross-tenant pattern for Link to Fabric in the provided content, the following can be stated based on what is documented:

1. Support status
   • Only same-tenant Link to Fabric is described. Cross-tenant Link to Fabric (Dataverse/D365FO in one tenant, Fabric workspace in another tenant) is not documented as supported.
2. Configuration guidance (within a single tenant)
   • To configure Link to Fabric in a supported way:
     1. Ensure the Fabric workspace is in the same tenant as the Dataverse environment.
     2. Create an application user (service principal) in Dataverse and assign the appropriate business unit and System Administrator role.
     3. In the Link to Fabric wizard, choose Service Principal and provide:
        • Tenant ID (Azure tenant ID for the shared tenant)
        • Client ID (application ID of the service principal)
        • Key (client secret or certificate)
     4. Complete the wizard so that shortcuts to Dataverse tables are created in the Fabric lakehouse.
     5. Manage the connection later via Manage link to Fabric, where the authentication method can be switched (for example, to Workspace identity) and the connection can be shared with other users.
3. Alternatives / workarounds (based on documented patterns)
   • The documentation in scope does not provide an official workaround for cross-tenant Link to Fabric. It only covers:
     • Standard Link to Fabric between Dataverse and a Fabric workspace in the same tenant.
     • General cross-tenant connectivity patterns for Fabric using workspace-level private links (for secure access between tenants), but not specifically tied to Link to Fabric.
   • Any cross-tenant solution would therefore need to follow general cross-tenant Fabric connectivity patterns (for example, workspace-level private links) and then use supported, tenant-aligned Link to Fabric or other ingestion mechanisms within that architecture, but this is not described as a supported Link to Fabric configuration in the provided content.

Given the documentation available here, the only clearly supported and documented configuration for Link to Fabric is within a single tenant. Cross-tenant Link to Fabric is not described as supported, and no official workaround is provided in the referenced material.

References:

• Link to Microsoft Fabric
• Cross-tenant connections using workspace-level private links
• Connect to your Microsoft Fabric tenant from Microsoft Purview in a different tenant