Create an Azure Synapse Link for Dataverse with Azure Data Lake
You can use the Azure Synapse Link to connect your Microsoft Dataverse data to Azure Data Lake Storage Gen2 to enable various analytics scenarios. This article shows you how to perform the following tasks:
- Connect your Dataverse data to your Azure Data Lake Storage Gen2 account with the Azure Synapse Link service.
- Manage Dataverse tables included in the Azure Synapse Link.
- Monitor your Azure Synapse Link.
- Unlink your Azure Synapse Link.
- Relink your Azure Synapse Link.
- View your data in Azure Data Lake and understand the file structure.
Azure Synapse Link for Dataverse was formerly known as Export to data lake. The service was renamed effective May 2021 and will continue to export data to Azure Data Lake as well as Azure Synapse Analytics.
- Azure Data Lake Storage Gen2: You must have an Azure Data Lake Storage Gen2 account and Owner and Storage Blob Data Contributor role access. Your storage account must enable Hierarchical namespace and public network access for both initial setup and delta sync. Allow storage account key access is required only for the initial setup. We recommend that replication is set to read-access geo-redundant storage (RA-GRS).
- The storage account must be created in the same Azure Active Directory (Azure AD) tenant as your Power Apps tenant.
- The storage account must be created in the same region as the Power Apps environment you will use the feature in.
- You must have Reader role access to the resource group with the storage account.
- To link the environment to Azure Data Lake Storage Gen2, you must have the Dataverse system administrator security role.
- Only tables that have change tracking enabled can be exported.
Connect Dataverse to Azure Data Lake Storage Gen2
Sign in to Power Apps and select your preferred environment.
On the left navigation pane, select Azure Synapse Link. If the item isn’t in the left navigation pane, select …More and then select the item you want.
On the command bar, select + New link to data lake.
Select the Subscription, Resource group, and Storage account. Ensure that storage account meets the requirements specified in the Prerequisites section. Select Next.
As part of linking the environment to a data lake, you grant the Azure Synapse Link service access to your storage account. Ensure that you followed the prerequisites of creating and configuring the Azure data lake storage account, and granting yourself an owner role on the storage account. Additionally, you grant the Power Platform Dataflows service access to your storage account. More information: Self-service data prep with dataflows.
Add the tables you want to export, and then select Save. Only tables with change tracking enabled can be exported. More information: Enable change tracking.
You can follow the steps above to create a link from one environment to multiple Azure data lakes in your Azure subscription. Similarly, you could create a link from multiple environments to the same Azure Data Lake, all within the same tenant.
The data exported by Azure Synapse Link service is encrypted at transit using Transport Layer Security(TLS) 1.2 or higher and encrypted at rest in Azure Data Lake Storage Gen2. Additionally, transient data in the blob storage is also encrypted at rest. Encryption in Azure Data Lake Storage Gen2 helps you protect your data, implement enterprise security policies, and meet regulatory compliance requirements. More information: Azure Data Encryption-at-Rest
Currently, you can't provide public IPs for the Azure Synapse Link for Dataverse service that can be used in Azure Data Lake firewall settings. Public IP network rules have no effect on requests originating from the same Azure region as the storage account. Services deployed in the same region as the storage account use private Azure IP addresses for communication. Thus, you can't restrict access to specific Azure services based on their public outbound IP address range. More information: Configure Azure Storage firewalls and virtual networks
Manage table data to the data lake
After you have set up the Azure Synapse Link, you can manage the tables that are exported in one of two ways:
On the Power Apps maker portal Azure Synapse Link area, select Manage tables on the command bar to add or remove one or more linked tables.
On the Power Apps maker portal Tables area, select … next to a table, and then select the linked data lake where you want to export table data.
Monitor your Azure Synapse Link
After you have set up the Azure Synapse Link, you can monitor the Azure Synapse Link under the Tables tab.
- There will be a list of tables that are a part of the selected Azure Synapse Link.
- There are different stages the sync status will circulate through. NotStarted indicates that the table is waiting to be synced. Once the table initial sync has been Completed, there will be a post processing stage where incremental updates will not take place. This may take several hours depending on the size of your data. As the incremental updates start taking place, the date for the last sync will be regularly updated.
- The Count column shows the number rows written. When Append only is set to No, this is the total number of records. When Append Only is set to Yes, this is the total number of changes.
- The Append only and Partition strategy columns show the usage of different advanced configurations.
Unlinking an Azure Synapse Link
Select the desired Azure Synapse Link to unlink.
Select Unlink data lake from the command bar.
To delete both the data lake file system, select Delete data lake file system.
Select Yes, and allow a few minutes for everything to be unlinked and deleted.
Relinking an Azure Synapse Link
If you deleted the file system when unlinking, follow the steps above to relink the same data lake. If you did not delete the file system when unlinking, you must clear the data to relink:
Go to the Azure Data Lake.
Delete the Dataverse container.
Go to Power Apps, and relink the data lake.
View your data in Azure Data Lake Storage Gen2
Select the desired Azure Synapse Link, and then select Go to Azure data lake from the top panel.
Expand File Systems, and then select dataverse-environmentName-organizationUniqueName.
The model.json file, along with its name and version, provides a list of tables that have been exported to the data lake. The model.json file also includes the initial sync status and sync completion time.
A folder that includes snapshot comma-delimited (CSV format) files is displayed for each table exported to the data lake.
Link a Synapse workspace to an existing Synapse Link profile with data lake only
In web browsers address bar, append
?athena.updateLake=trueto the web address that ends with exporttodatalake.
Select an existing profile from the Synapse Link homepage and click extended option
Select Link to Azure Synapse Analytics Workspace and allow a few minutes for everything to be linked.
Continuous snapshot updates
Microsoft Dataverse data can continuously change through create, update, and delete transactions. Snapshots provide a read-only copy of data that's updated at regular intervals, in this case every hour. This ensures that at any given point, a data analytics consumer can reliably consume data in the lake.
When tables are added as part of the initial export, the table data is written to the table.csv files under the corresponding folders in the data lake. This is the T1 interval, where a snapshot read-only file named table-T1.csv—for example, Account-T1.csv or Contacts-T1.csv—is created. Additionally, the model.json file is updated to point to these snapshot files. Opening model.json, you can view the snapshot details.
Here's an example of an Account.csv partitioned file and snapshot folder in the data lake.
Changes in Dataverse are continuously pushed to the corresponding CSV files by using the trickle feed engine. This is the T2 interval, where another snapshot is taken. table-T2.csv—for example, Accounts-T2.csv or Contacts-T2.csv (assuming there are changes for the table) —and model.json are updated to the new snapshot files. Any new person who views snapshot data from T2 onward is directed to the newer snapshot files. This way, the original snapshot viewer can continue to work on the older snapshot T1 files while newer viewers can read the latest updates. This is useful in scenarios that have longer-running downstream processes.
A new snapshot file is created only if there is a data update. Only the latest five snapshot files will be retained. Stagnant data will be automatically removed from your Azure Data Lake Storage Gen 2 account.
Here's an example of the model.json file, which always points to the latest time-stamped account snapshot file.
After successfully using the Azure Synapse Link for Dataverse service, discover how you can analyze and consume your data with Discover Hub. To access Discover Hub, go to Power Apps > Azure Synapse Link. Select your linked service and then select the Discover Hub tab. Here you can find recommended tools and curated documentation to help you get the most value out of your data.
Analyze Dataverse data in the data lake with Power BI
Ingest Dataverse data in the data lake with Azure Data Factory
Azure Synapse Link for Dataverse Advanced Configuration
Submit and view feedback for