Export data to Azure Synapse Analytics (preview)
Azure Synapse is an analytics service that accelerates time to insight across data warehouses and big data systems. You can ingest and use your Customer Insights data in Azure Synapse.
Prerequisites
Note
Make sure to set all role assignments as described.
- In Customer Insights, your Azure Active Directory (AD) user account must have an Administrator role.
In Azure:
An active Azure subscription.
If using a new Azure Data Lake Storage Gen2 account, the service principal for Customer Insights has Storage Blob Data Contributor permissions. The Data Lake Storage Gen2 must have hierarchical namespace enabled.
On the resource group where the Azure Synapse workspace is located, the service principal and the Azure AD user with admin permissions in Customer Insights must be assigned at least Reader permissions.
The Azure AD user with admin permissions in Customer Insights has Storage Blob Data Contributor permissions on the Azure Data Lake Storage Gen2 account where the data is located and linked to the Azure Synapse workspace. Learn more about using the Azure portal to assign an Azure role for access to blob and queue data and Storage Blob Data Contributor permissions.
The Azure Synapse workspace managed identity has Storage Blob Data Contributor permissions on the Azure Data Lake Storage Gen2 account where the data is located and linked to the Azure Synapse workspace. Learn more on using the Azure portal to assign an Azure role for access to blob and queue data and Storage Blob Data Contributor permissions.
On the Azure Synapse workspace, the service principal for Customer Insights has Synapse Administrator role assigned.
If your Customer Insights environment stores data in your own Azure Data Lake Storage, the user who sets up the connection to Azure Synapse Analytics needs at least the built-in Reader role on the Data Lake Storage account. For more information, see Assign Azure roles using the Azure portal.
Set up connection to Azure Synapse
You must be an administrator in Customer Insights to add a connection.
Go to Admin > Connections.
Select Add connection and choose Azure Synapse Analytics.
Give your connection a recognizable name in the Display name field. The name and the type of the connection describes this connection. We recommend choosing a name that explains the purpose and target of the connection.
Choose who can use this connection. By default, it's only administrators. For more information, see Allow contributors to use a connection for exports.
Select or search for the subscription you want to use the Customer Insights data in. As soon as a subscription is selected, you can also select Workspace, Storage account, and Container.
Review the data privacy and compliance and select I agree.
Select Save to complete the connection.
Configure an export
To configure this export, you must have permission for this connection type. To configure the export with a shared connection, you need at least Contributor permissions in Customer Insights.
Go to Data > Exports.
Select Add export.
In the Connection for export field, choose a connection from the Azure Synapse Analytics section. Contact an administrator if no connection is available.
Provide a recognizable Display name for your export and a Database name. The export will create a new Azure Synapse lake database in the workspace defined in the connection.
Select which entities you want to export to Azure Synapse Analytics.
Note
Data sources based on a Common Data Model folder aren't supported.
Select Save.
Saving an export doesn't run the export immediately. The export runs with every scheduled refresh. You can also export data on demand.
To query data that was exported to Synapse Analytics, you need Storage Blob Data Reader access to the destination storage on the workspace of exports.
Update an export
Go to Data > Exports.
Select Edit on the export you want to update.
Add or Remove entities from the selection. If entities are removed from the selection, they aren't deleted from the Synapse Analytics database. However, future data refreshes won't update the removed entities in that database.
Changing the Database Name creates a new Synapse Analytics database. The database with the name that was configured before won't receive any updates in future refreshes.
Feedback
Submit and view feedback for