Use your own Azure Data Lake Storage account

Dynamics 365 Customer Insights - Data gives you the option to store your customer data in Azure Data Lake Storage. Customer data includes data that you import and the output data like unified profiles and segments. Some of the output data is also stored as tables in Microsoft Dataverse along with metadata like match rules or segment configuration, and search index. By saving data to Data Lake Storage, you agree that data will be transferred to and stored in the appropriate geographic location for that Azure storage account. For more information, see Microsoft Trust Center.

Administrators in Customer Insights - Data can create environments and specify the data storage option in the process.

Prerequisites

• Azure Data Lake Storage accounts must be in the same Azure region that you selected when creating the Customer Insights - Data environment. To know the region of the environment, go to Settings > System > About.
• The Data Lake Storage account must have hierarchical namespace enabled.
• The administrator setting up the Customer Insights - Data environment needs the Storage Blob Data Contributor or Storage Blob Data Owner role on the storage account or the customerinsights container. For more information on assigning permission in a storage account, see Create a storage account.

Connect Customer Insights - Data with your storage account

When you create a new environment, make sure the Data Lake Storage account exists and all prerequisites are met.

1. In the Data storage step during environment creation, set Save output data to Azure Data Lake Storage Gen2.
2. Choose how to Connect your storage. You can choose between a resource-based option and a subscription-based option for authentication. For more information, see Connect to an Azure Data Lake Storage account by using a Microsoft Entra service principal.
   • For Azure subscription, choose the Subscription, Resource group, and Storage account that contains the customerinsights container.
   • For Account key, provide the Account name and the Account key for the Data Lake Storage account. Using this authentication method implies that you're informed if your organization rotates the keys. You must update the environment configuration with the new key when it's rotated.
3. If your storage account is behind a firewall, select Enable private link to connect to the account using Azure private links

When system processes like data ingestion complete, the system creates corresponding folders in the storage account. Data files and model.json files are created and added to folders based on the process name.

If you create multiple environments and choose to save the output tables from those environments to your storage account, the system creates separate folders for each environment with ci_environmentID in the container.

Enable data sharing with Dataverse from your own Azure Data Lake Storage (preview)

[This article is prerelease documentation and is subject to change.]

Dynamics 365 Customer Insights - Data writes output data like unified profiles and segments to your Azure Data Lake Storage. You can enable data sharing to make output data in your Azure Data Lake Storage available to your Microsoft Dataverse environment. The user who sets up the Customer Insights - Data environment needs at least Storage Blob Data Reader permissions on the customerinsights container in the storage account.

Important

• This is a preview feature.
• Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.

Limitations

• A single one-to-one mapping between a Dataverse organization and an Azure Data Lake Storage account is supported.
• The target storage account can't be changed.
• Data sharing doesn't work if your Azure Data Lake Storage account is behind a firewall.
• Automatic linking of customer profiles in Dataverse isn't supported when using your own Azure Data Lake Storage. Customer Insights storage is recommended.

Set up security groups on your own Azure Data Lake Storage

1. Create two security groups on your Azure subscription - one Reader security group and one Contributor security group and set the Microsoft Dataverse service as the owner for both security groups.

2. Manage the Access Control List (ACL) on the customerinsights container in your storage account through these security groups.

   1. Add the Microsoft Dataverse service and any Dataverse-based business applications like Dynamics 365 Sales to the Reader security group with read-only permissions.
   2. Add only the Customers Insights application to the Contributor security group to grant both read and write permissions to write profiles and insights.

Set up PowerShell

Set up PowerShell to execute PowerShell scripts.

1. Install the latest version of Azure Active Directory PowerShell for Graph.

   1. On your PC, select the Windows key on your keyboard and search for Windows PowerShell and select Run as administrator.
   2. In the PowerShell window that opens, enter Install-Module AzureAD.

2. Import three modules.

   1. In the PowerShell window, enter Install-Module -Name Az.Accounts and follow the steps.
   2. Repeat for Install-Module -Name Az.Resources and Install-Module -Name Az.Storage.

Execute PowerShell scripts and obtain the Permission Identifier

1. Download the two PowerShell scripts you need to run from our engineer's GitHub repo.

   • CreateSecurityGroups.ps1: Requires tenant admin permissions.
   • ByolSetup.ps1: Requires Storage Blob Data Owner permissions at the storage account/container level. This script creates the permission for you. Your role assignment can be removed manually after successfully running the script.

2. Execute CreateSecurityGroups.ps1 in Windows PowerShell by providing the Azure subscription ID containing your Azure Data Lake Storage. Open the PowerShell script in an editor to review additional information and the implemented logic.

   This script creates two security groups on your Azure subscription: one for the Reader group and another for the Contributor group. Microsoft Dataverse service is the owner for both these security groups.

3. Save both the security group ID values generated by this script to use in the ByolSetup.ps1 script.

   Note

   Security group creation can be disabled on your tenant. In that case, a manual setup would be needed and your Azure AD admin would have to enable security group creation.

4. Execute ByolSetup.ps1 in Windows PowerShell by providing the Azure subscription ID containing your Azure Data Lake Storage, storage account name, resource group name, and the Reader and Contributor security group ID values. Open the PowerShell script in an editor to review additional information and the implemented logic.

   This script adds the required role-based access control for the Microsoft Dataverse service and any Dataverse-based business applications. It also updates the Access Control List (ACL) on the customerinsights container for the security groups created with the CreateSecurityGroups.ps1 script. The Contributor group is given rwx permission and Readers group is given r-x permission only.

5. Copy the output string that looks like: https://DVBYODLDemo/customerinsights?rg=285f5727-a2ae-4afd-9549-64343a0gbabc&cg=720d2dae-4ac8-59f8-9e96-2fa675dbdabc

6. Enter the copied output string into the Permissions identifier field during environment configuration for Microsoft Dataverse.