Connect to your Microsoft Fabric tenant from Microsoft Purview in a different tenant (Preview)

This article outlines how to register a Microsoft Fabric tenant that's in a different tenant from your Microsoft Purview resource, and how to authenticate and interact with the Fabric source in Microsoft Purview. For more information about Microsoft Purview in general, read the introductory article.

Supported capabilities

Supported scenarios for Fabric scans

Known limitations

• Currently for all Fabric items besides Power BI, only item level metadata and lineage will be scanned, scanning metadata and lineage of sub level items like Lakehouse tables or files isn't supported.
• For self-hosted integration runtime, the standard self-hosted integration runtime with minimal version 5.40.8836.1 or Kubernetes supported self-hosted integration runtime is supported.
• Empty workspaces are skipped.

Prerequisites

Before you start, make sure you have the following:

• An Azure account with an active subscription. Create an account for free.

• An active Microsoft Purview account.

Authentication options

• Service Principal
• Delegated Authentication

Deployment checklist

The deployment checklist is a summary of all the steps you'll need to take to set up a cross-tenant Fabric source. You can use it during setup or for troubleshooting, to confirm you've followed all the necessary steps to connect.

Register the Fabric tenant

1. From the options on the left, select Data Map.

2. Select Register, and then select Fabric as your data source.

   

3. Give your Fabric instance a friendly name. The name must be 3 to 63 characters long, and must contain only letters, numbers, underscores, and hyphens. Spaces aren't allowed.

4. Edit the Tenant ID field, to replace with the tenant for the cross-tenant Fabric that you want to register and scan. By default, Microsoft Purview's tenant ID is populated.

   

Authentication to scan

To be able to scan your Microsoft Fabric tenant and review its metadata, you'll first need to create a way to authenticate with the Fabric tenant, and then give Microsoft Purview the authentication information.

Authenticate to Fabric tenant

In Microsoft Entra tenant, where Fabric tenant is located:

1. In the Azure portal, search for Microsoft Entra ID.

2. Create a new security group in your Microsoft Entra ID, by following Create a basic group and add members using Microsoft Entra ID.

   Tip

   You can skip this step if you already have a security group you want to use.

3. Select Security as the Group Type.

   

4. Select Members, then select + Add members.

5. Search for your Microsoft Purview managed identity or service principal and select it.

   

   You should see a success notification showing you that it was added.

   

Associate the security group with Fabric tenant

1. Log into the Fabric admin portal.

2. Select the Tenant settings page.

   Important

   You need to be a Fabric Admin to see the tenant settings page.

3. Select Admin API settings > Allow service principals to use read-only admin APIs.

4. Select Specific security groups.

5. Select Admin API settings > Enhance admin APIs responses with detailed metadata and Enhance admin APIs responses with DAX and mashup expressions > Enable the toggle to allow Microsoft Purview Data Map automatically discover the detailed metadata of Fabric datasets as part of its scans.

   Important

   After you update the Admin API settings on your Fabric tenant, wait around 15 minutes before registering a scan and test connection.

   Caution

   When you allow the security group you created to use read-only admin APIs, you also allow it to access the metadata (e.g. dashboard and report names, owners, descriptions, etc.) for all of your Fabric artifacts in this tenant. Once the metadata has been pulled into the Microsoft Purview, Microsoft Purview's permissions, not Fabric permissions, determine who can see that metadata.

   Note

   You can remove the security group from your developer settings, but the metadata previously extracted won't be removed from the Microsoft Purview account. You can delete it separately, if you wish.

Configure credentials for scans in Microsoft Purview

Service principal

1. Create an app registration in your Microsoft Entra tenant where Fabric is located. Provide a web URL in the Redirect URI.

   

2. Take note of the client ID (app ID).

   

3. From the Microsoft Entra dashboard, select the newly created application, and then select App permissions. Assign the application the following delegated permissions:

   • Microsoft Graph openid
   • Microsoft Graph User.Read

   

4. From the Microsoft Entra dashboard, select the newly created application, and then select Authentication. Under Supported account types, select Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant).

   

5. Under Implicit grant and hybrid flows, select ID tokens (used for implicit and hybrid flows).

   

6. Under Advanced settings, enable Allow Public client flows.

7. In the tenant where Microsoft Purview is created go to the instance of Azure Key Vault.

8. Select Settings > Secrets, and then select + Generate/Import.

   

9. Enter a name for the secret. For Value, type the newly created secret for the App registration. Select Create to complete.

10. Under Certificates & secrets, create a new secret and save it securely for next steps.

11. In Azure portal, navigate to your Azure key vault.

12. Select Settings > Secrets and select + Generate/Import.

    

13. Enter a name for the secret and for Value, type the newly created secret for the App registration. Select Create to complete.

    

14. If your key vault isn't connected to Microsoft Purview yet, you need to create a new key vault connection.

15. Next, in Microsoft Purview, go to the Credentials page under Management to create a new credential.

    Tip

    Alternatively, you can create a new credential during the scanning process.

16. Create your new Credential by selecting + New.

17. Provide required parameters:

    • Name: Provide a unique name for credential
    • Authentication method: Service principal
    • Tenant ID: Your Fabric tenant ID
    • Client ID: Use Service Principal Client ID (App ID) you created earlier
    • Key Vault Connection: the Microsoft Purview connection to the Key Vault where you created your secret earlier.
    • Secret name: the name of the secret you created earlier.

    

18. Once all the details have been filled in, select Create.

Delegated authentication

1. Create a user account in the Microsoft Entra tenant where the Fabric tenant is located, and assign the user to this role: Fabric Administrator. Take note of the username and sign in to change the password.

2. Go to the instance of Azure Key Vault in the tenant where Microsoft Purview is created.

3. Select Settings > Secrets, and then select + Generate/Import.

   

4. Enter a name for the secret. For Value, type the newly created password for the Microsoft Entra user. Select Create to complete.

   

5. If your key vault isn't connected to Microsoft Purview yet, you need to create a new key vault connection.

6. Create an app registration in your Microsoft Entra tenant where Fabric is located. Provide a web URL in the Redirect URI.

   

7. Take note of the client ID (app ID).

   

8. From the Microsoft Entra dashboard, select the newly created application, and then select App permissions. Assign the application the following delegated permissions, and grant admin consent for the tenant:

   • Fabric Service Tenant.Read.All
   • Microsoft Graph openid
   • Microsoft Graph User.Read

   

9. From the Microsoft Entra dashboard, select the newly created application, and then select Authentication. Under Supported account types, select Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant).

   

10. Under Implicit grant and hybrid flows, select ID tokens (used for implicit and hybrid flows).

    

11. Under Advanced settings, enable Allow Public client flows.

12. Next, in Microsoft Purview, go to the Credentials page under Management to create a new credential.

    Tip

    Alternatively, you can create a new credential during the scanning process.

13. Create your new Credential by selecting + New.

14. Provide required parameters:

    • Name: Provide a unique name for credential
    • Authentication method: Delegated auth
    • Client ID: Use Service Principal Client ID (App ID) you created earlier
    • User name: Provide the username of Fabric Administrator you created earlier
    • Key Vault Connection: the Microsoft Purview connection to the Key Vault where you created your secret earlier.
    • Secret name: the name of the secret you created earlier.

    

15. Once all the details have been filled in, select Create.

Create scan

1. In the Microsoft Purview Studio, go to the Data map in the left menu. Go to Sources.

2. Select the registered Fabric source from cross-tenant.

3. Select + New scan.

4. Give your scan a name. Then select the option to include or exclude the personal workspaces.

   Note

   If you switch the configuration of a scan to include or exclude a personal workspace, you trigger a full scan of the Fabric source.

5. Select Azure AutoResolveIntegrationRuntime from the dropdown list.

6. For the Credential, select the credential you created for your service principal or delegated authentication.

   

7. Select Test connection before continuing to the next steps.

   If the test fails, select View Report to see the detailed status and troubleshoot the problem:

   1. Access - Failed status means that the user authentication failed. Validate if the username and password are correct. Review if the credential contains the correct client (app) ID from the app registration.
   2. Assets (+ lineage) - Failed status means that the authorization between Microsoft Purview and Fabric has failed. Make sure that the user is added to the Fabric administrator role.
   3. Detailed metadata (Enhanced) - Failed status means that the Fabric admin portal is disabled for the following setting: Enhance admin APIs responses with detailed metadata.

   Tip

   For more troubleshooting, see the deployment checklist to make sure you've covered every step in your scenario.

8. Set up a scan trigger. Your options are Recurring or Once.

   

9. On Review new scan, select Save and run to launch your scan.

View your scans and scan runs

To view existing scans:

1. Go to the Microsoft Purview portal. On the left pane, select Data map.
2. Select the data source. You can view a list of existing scans on that data source under Recent scans, or you can view all scans on the Scans tab.
3. Select the scan that has results you want to view. The pane shows you all the previous scan runs, along with the status and metrics for each scan run.
4. Select the run ID to check the scan run details.

Manage your scans

To edit, cancel, or delete a scan:

1. Go to the Microsoft Purview portal. On the left pane, select Data Map.

2. Select the data source. You can view a list of existing scans on that data source under Recent scans, or you can view all scans on the Scans tab.

3. Select the scan that you want to manage. You can then:

   • Edit the scan by selecting Edit scan.
   • Cancel an in-progress scan by selecting Cancel scan run.
   • Delete your scan by selecting Delete scan.

Next steps

Now that you've registered your source, see the following guides to learn more about Microsoft Purview and your data.

• Data estate insights in Microsoft Purview
• Search data catalog