Edit

Share via

Managed private endpoints in Microsoft Graph Data Connect

  • Article

This article describes how to enable Azure V-net Integration Runtime (IR) to manage private endpoints in Microsoft Graph Data Connect (Data Connect). We recommend that customers use Azure Synapse workspaces to enable Azure V-net IR in mapping data flow. Azure Data Factory (Data Factory) is compatible with Azure V-net IR.

With Azure V-Net IR, customers no longer need to add public IP addresses to an allow list, and customers can close their destination storage accounts to the public network to set up their data extraction over a private virtual network. This helps to ensure that data extraction from Data Connect to the customer's storage account is more secure.

Note

Managed private endpoints are only supported in Mapping Data Flows (MDF) within your Azure Synapse or Azure Data Factory (ADF) workspaces. Existing Azure Synapse or ADF workspaces with copy activity require you to allow list IP addresses to enable access through select protected networks.

Enable Azure V-net IR for Azure Synapse

Use the following steps to enable Azure V-net Integration Runtime (IR) to manage private endpoints within MDF in Data Connect:

  1. Create a Synapse (or ADF) workspace, and then sign in to the Azure portal to configure an existing storage account. Our example below demonstrates this capability in Synapse.

    Screenshot with the Basics tab highlighted, showing the first step to create a Synapse workspace.

  2. On the Networking tab, next to Managed virtual network, select Enable.

    Screenshot with the Networking tab highlighted and Managed virtual network option enabled, showing the second step to create a Synapse workspace.

  3. Open the Synapse workspace. Go to Manage > Managed private endpoints.

  • If you added a storage option when creating your Synapse workspace, the managed private endpoint connection to storage is already created in a Pending approval state.

    Screenshot showing a successfully created, managed private endpoint, with approval state pending.

  • If you're using existing storage, create a managed private endpoint. Select New, choose the storage type, then choose Continue.

    Screenshot showing the option to create a managed private endpoint with an existing storage option.

  • Provide the connection name and description, specify the storage account, then choose Create.

    Screenshot showing how to create and name a new managed private endpoint.

  • Note the initial state will be provisioning of a private IP address from within the Managed Virtual Network.

    Screenshot showing the provisioning state of a new managed private endpoint that is pending.

  • After the endpoint is successfully provisioned, the approval state is Pending. Continue to Step 4, and use the created name rather than the name generated in step 3.

    Screenshot showing the provisioning state of a new managed private endpoint.

  1. Approve the managed private endpoint from the storage account.

  • Go to Storage account > Networking > Private endpoint connections to view the private endpoint request in a pending state.

    Screenshot showing a new private endpoint request in a pending state.

  • Select the connection, then choose Approve.

    Screenshot showing a new private endpoint with Approval button highlighted, ready to be approved.

  • Provide a description when prompted, and verify that the connection state has changed to Approved.

    Screenshot showing a private endpoint with Approved state highlighted.

  1. In the storage account Networking blade, go to Firewalls and virtual networks. Under Public network access, select Enabled from selected virtual networks and IP addresses, and configure the network firewall according to your preference. Uncheck Allow Azure services on the trusted services list to access this storage account.

    Screenshot showing the Firewalls and virtual networks tab highlighted, and configuration settings for public network access, firewall, and network rule exceptions.

  2. Return to the previous Synapse workspace, and wait for the managed private endpoint to switch to Approved.

    Screenshot with the approved state of a managed private endpoint in a Synapse workspace, highlighted.

The managed private endpoint shows as successfully created and linked to the desired storage account from Synapse Analytics.

  1. Verify the available integration runtime is configured to Managed Virtual Network (configured by default).

    Screenshot with the Managed Virtual Network highlighted, successfully configured to available integration runtime.

After these steps, v-net IR in MDF should be enabled within your Synapse (or ADF) workspace. Please reach out to the Data Connect team for any questions!