Join Azure-SSIS integration runtime to a virtual network

  • Commodity
  • 5 minutes to read

APPLIES TO: Azure Data Factory Azure Synapse Analytics (Preview)

When using SQL Server Integration Services (SSIS) in Azure Data Factory (ADF), you should bring together your Azure-SSIS integration runtime (IR) to a virtual network in the post-obit scenarios:

  • You want to access on-premises data stores/resources from SSIS packages that run on your Azure-SSIS IR without configuring and managing a self-hosted IR equally proxy.

  • You want to utilize Azure SQL Database server configured with a individual endpoint/IP firewall rule/virtual network service endpoint or Azure SQL Managed Case that joins a virtual network to host SSIS catalog database (SSISDB).

  • You want to access Azure data stores/resource configured with a private endpoint/IP firewall rule/virtual network service endpoint from SSIS packages that run on your Azure-SSIS IR.

  • You want to access other cloud data stores/resource configured with an IP firewall rule from SSIS packages that run on your Azure-SSIS IR.

ADF lets you join your Azure-SSIS IR to a virtual network created through Azure Resources Managing director or archetype deployment model.

Important

The classic virtual network is existence deprecated, so use the Azure Resource Managing director virtual network instead. If you already employ the classic virtual network, switch to the Azure Resource Manager virtual network every bit soon as possible.

The Configure Azure-SSIS IR to join a virtual network tutorial shows the minimum steps with express virtual network injection method via Azure portal/ADF UI. This commodity and other ones like the Configure a virtual network to inject Azure-SSIS IR commodity expand on the tutorial and depict all optional steps:

  • If you use the standard virtual network injection method.
  • If you use the classic virtual network.
  • If you bring your own static public IP (BYOIP) addresses for Azure-SSIS IR.
  • If you use your own domain proper name system (DNS) server.
  • If yous use a network security group (NSG).
  • If y'all use user-defined routes (UDRs).
  • If yous apply customized Azure-SSIS IR.
  • If y'all employ Azure PowerShell to provision your Azure-SSIS IR.

Access to on-bounds information stores

If your SSIS packages admission on-premises data stores, you can join your Azure-SSIS IR to a virtual network that is connected to the on-premises network. Alternatively, yous can configure and manage a cocky-hosted IR as proxy for your Azure-SSIS IR. For more than data, see Configure a self-hosted IR as proxy for Azure-SSIS IR.

When joining your Azure-SSIS IR to a virtual network, remember these important points:

  • If no virtual network is continued to your on-bounds network, showtime create an Azure Resource Manager virtual network for your Azure-SSIS IR to join. And then configure a site-to-site VPN gateway connexion or Azure ExpressRoute connection from that virtual network to your on-premises network.

  • If an Azure Resource Manager virtual network is already connected to your on-premises network in the same location as your Azure-SSIS IR, you tin can join your IR to that virtual network.

  • If a classic virtual network is already connected to your on-bounds network in a unlike location from your Azure-SSIS IR, you tin can create an Azure Resource Managing director virtual network for your Azure-SSIS IR to bring together. Then configure a classic-to-Azure Resource Manager virtual network connection.

  • If an Azure Resource Manager virtual network is already continued to your on-bounds network in a different location from your Azure-SSIS IR, you can first create an Azure Resource Director virtual network for your Azure-SSIS IR to join. Then configure an Azure Resource Manager-to-Azure Resource Manager virtual network connexion.

Hosting SSISDB in Azure SQL Database server or Managed Instance

If you host SSISDB in Azure SQL Database server configured with a virtual network service endpoint, make certain that you join your Azure-SSIS IR to the same virtual network and subnet.

If yous host SSISDB in Azure SQL Managed Instance that joins a virtual network, make certain that you bring together your Azure-SSIS IR to the same virtual network, but in a unlike subnet than the managed instance. To bring together your Azure-SSIS IR to a different virtual network than the managed instance, we recommend either virtual network peering (which is express to the same region) or virtual network-to-virtual network connexion. For more than data, come across Connect your application to Azure SQL Managed Instance.

Admission to Azure data stores

If your SSIS packages admission Azure data stores/resource that support virtual network service endpoints and you desire to secure access to those resource from Azure-SSIS IR, you tin join your Azure-SSIS IR to a virtual network subnet configured for virtual network service endpoints and then add a virtual network rule on the firewall of relevant resources to permit admission from the same subnet.

Admission to other cloud information stores

If your SSIS packages access other deject data stores/resource that allow merely specific static public IP addresses and you desire to secure access to those resources from Azure-SSIS IR, yous tin associate public IP addresses with your Azure-SSIS IR while joining information technology to a virtual network and and so add an IP firewall dominion on the firewall of relevant resource to let access from those IP addresses. There are two options to do this:

  • When creating Azure-SSIS IR, yous tin can bring your ain static public IP addresses and associate them with your Azure-SSIS IR via ADF UI or Azure PowerShell. Only the outbound net connectivity from your Azure-SSIS IR will use these public IP addresses and other resources in the subnet won't use them.

  • Y'all can besides configure a virtual network network address translation (NAT) in the subnet that your Azure-SSIS IR joins and all outbound internet connectivity from this subnet will use a specified public IP address.

In all cases, the virtual network can only be deployed through Azure Resource Manager deployment model.

Next steps

  • Configure a virtual network to inject Azure-SSIS IR
  • Express virtual network injection method
  • Standard virtual network injection method
  • Join Azure-SSIS IR to a virtual network via ADF UI
  • Join Azure-SSIS IR to a virtual network via Azure PowerShell

For more data about Azure-SSIS IR, see the following articles:

  • Azure-SSIS IR. This article provides full general conceptual information about IRs, including Azure-SSIS IR.
  • Tutorial: Deploy SSIS packages to Azure. This tutorial provides step-past-step instructions to create your Azure-SSIS IR. It uses Azure SQL Database server to host SSISDB.
  • Create an Azure-SSIS IR. This article expands on the tutorial. It provides instructions on using Azure SQL Database server configured with a virtual network service endpoint/IP firewall rule/individual endpoint or Azure SQL Managed Instance that joins a virtual network to host SSISDB. It shows you how to join your Azure-SSIS IR to a virtual network.
  • Monitor an Azure-SSIS IR. This article shows you how to retrieve and understand information about your Azure-SSIS IR.
  • Manage an Azure-SSIS IR. This article shows you how to stop, get-go, or delete your Azure-SSIS IR. It also shows yous how to scale out your Azure-SSIS IR past calculation more nodes.