To integrate tables created in Dataverse into Fabric Lakehouse on OneLake and have them show up as valid Shortcut options, what must you do first?

To integrate tables created in Dataverse into Fabric Lakehouse on OneLake and have them show up as valid Shortcut options, what must you do first?

• A. Use the Link to Microsoft Fabric feature from the PowerApps maker portal.
• B. Enable Dataverse integration with Fabric through the Fabric admin portal.
• C. In the Fabric admin portal ensure M365 Dynamics environment is in the same tenant and region as your Fabric tenant.
• D. Develop a data pipeline to move the data into OneLake.

Answer: (A)

The key idea is to explicitly create a bridge between Dataverse and Fabric so the Dataverse tables appear as Fabric Shortcuts. Using the Link to Microsoft Fabric feature from the PowerApps maker portal establishes a Fabric Shortcut that points to a specific Dataverse table. Once this link is in place, the table shows up in Fabric Lakehouse on OneLake as a valid Shortcut option, with live data from Dataverse available without moving the data. Other approaches don’t perform that bridge step: simply enabling integration in a Fabric admin portal doesn’t create the Shortcut itself; ensuring tenant and region alignment may be a deployment consideration but doesn’t by itself create a Shortcut; and building a data pipeline to move data into OneLake goes against the purpose of Shortcuts, which is to reference live data without duplicating it.

The key idea is to explicitly create a bridge between Dataverse and Fabric so the Dataverse tables appear as Fabric Shortcuts. Using the Link to Microsoft Fabric feature from the PowerApps maker portal establishes a Fabric Shortcut that points to a specific Dataverse table. Once this link is in place, the table shows up in Fabric Lakehouse on OneLake as a valid Shortcut option, with live data from Dataverse available without moving the data.

Other approaches don’t perform that bridge step: simply enabling integration in a Fabric admin portal doesn’t create the Shortcut itself; ensuring tenant and region alignment may be a deployment consideration but doesn’t by itself create a Shortcut; and building a data pipeline to move data into OneLake goes against the purpose of Shortcuts, which is to reference live data without duplicating it.