Based on doc at…
- User
Based on doc at https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-select-fno-data#enable-finance-and-operations-virtual-entities-in-power-apps Can Azure Synapse Link be used to ingest finance and operations data to data lake without dataverse at all?
Assistant
Azure Synapse Link can be used to ingest Finance and Operations (F&O) data into Azure Data Lake Storage Gen2 and Azure Synapse Analytics, but it cannot be used entirely without Dataverse. Here’s why:
Key Points from Documentation
-
Integration with Dataverse Required:
The process for exporting F&O data to Azure Synapse Analytics or Data Lake is managed through the Power Platform (Power Apps), specifically via the Azure Synapse Link for Dataverse interface. The F&O environment must be linked with Microsoft Power Platform, which means Dataverse acts as the orchestration and management layer for the data movement[1]. -
No Direct F&O-to-Lake Export:
You cannot set up Azure Synapse Link directly from F&O to Data Lake without involving Dataverse. The documentation explicitly states that the F&O environment must be linked to Power Platform, and all configuration is done via the Power Apps portal (make.powerapps.com), which is Dataverse-centric[1]. -
Dataverse as the Control Plane, Not Data Copy:
While the data itself does not have to be copied into Dataverse tables (i.e., you do not need to use dual-write or virtual entities), the Dataverse environment is still required as the control plane for managing the link, selecting tables, and orchestrating the export[1][2][3]. -
Exported Data Format:
The data from F&O is exported in the Common Data Model format, typically as Parquet Delta files, directly into your Azure Data Lake or Synapse workspace. The data does not reside in Dataverse storage, but the linkage and management require Dataverse[1][2]. -
No Need for Dual-Write or Virtual Entities:
You do not need to set up dual-write or make F&O tables visible as virtual tables in Dataverse. The export is managed independently of these features[1].
Summary Table
Requirement Needed for Azure Synapse Link F&O Export? Dataverse environment (control) Yes Dataverse as data storage No (data goes to Data Lake/Synapse) Dual-write/virtual entities No Power Platform integration Yes Direct F&O to Data Lake (no Dataverse) No Conclusion
You cannot use Azure Synapse Link to export Finance and Operations data to a data lake without Dataverse at all.
Dataverse is required as the management and orchestration layer, even though the data itself does not reside in Dataverse and is exported directly to Azure Data Lake or Synapse Analytics[1][2][3]. The setup, table selection, and ongoing management all occur via the Power Platform (Dataverse) interface.> "The finance and operations apps environment must be linked with Microsoft Power Platform. ... You can enable both finance and operations tables and finance and operations entities in Azure Synapse Link for Dataverse. ... Makers can't see them in the Tables area in Power Apps (make.powerapps.com). You don't have to define finance and operations apps tables as virtual tables, and you don't have to enable change tracking for each table."[1]
In summary:
- Dataverse is mandatory for orchestration, but not as a data storage intermediary.
- The data lands directly in your Azure Data Lake or Synapse workspace.
- No dual-write or virtual entities are needed, but Dataverse must be present and linked to F&O for Azure Synapse Link to function[1][2][3].
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.