What feature should be used to connect Dataverse data to Fabric for integration into Lakehouse shortcuts?

What feature should be used to connect Dataverse data to Fabric for integration into Lakehouse shortcuts?

• A. Use the Link to Microsoft Fabric feature from the PowerApps maker portal.
• B. Enable Dataverse integration through the Fabric admin portal
• C. Data pipeline to move the data into OneLake
• D. In the Fabric admin portal, ensure M365 environment is same tenancy

Answer: (A)

Connecting Dataverse data to Fabric for Lakehouse shortcuts is about establishing a direct bridge that exposes Dataverse tables as Fabric Lakehouse shortcuts. The Link to Microsoft Fabric feature in the Power Apps maker portal is designed specifically for this, letting you pick a Dataverse table and create a shortcut that points to the Dataverse data. This enables analytics and AI workloads in Fabric without moving or duplicating data, keeping governance intact and avoiding extra data pipelines. Other options don’t provide the built-in, supported way to create that linkage: using an admin portal path isn’t the documented method for linking Dataverse to Fabric; moving data via a pipeline would copy data into OneLake and add unnecessary latency; and merely aligning tenancy in the Fabric admin portal doesn’t establish the actual connection to Dataverse.

Connecting Dataverse data to Fabric for Lakehouse shortcuts is about establishing a direct bridge that exposes Dataverse tables as Fabric Lakehouse shortcuts. The Link to Microsoft Fabric feature in the Power Apps maker portal is designed specifically for this, letting you pick a Dataverse table and create a shortcut that points to the Dataverse data. This enables analytics and AI workloads in Fabric without moving or duplicating data, keeping governance intact and avoiding extra data pipelines.

Other options don’t provide the built-in, supported way to create that linkage: using an admin portal path isn’t the documented method for linking Dataverse to Fabric; moving data via a pipeline would copy data into OneLake and add unnecessary latency; and merely aligning tenancy in the Fabric admin portal doesn’t establish the actual connection to Dataverse.