Create an Azure-SSIS integration runtime via Azure portal

APPLIES TO: Azure Data Factory Azure Synapse Analytics

This article shows you how to create an Azure-SQL Server Integration Services (SSIS) integration runtime (IR) in Azure Data Factory (ADF) or Synapse Pipelines via Azure portal.

Provision an Azure-SSIS integration runtime

General settings page

On the General settings page of Integration runtime setup pane, complete the following steps.

1. For Name, enter the name of your integration runtime.

2. For Description, enter the description of your integration runtime.

3. For Location, select the location of your integration runtime. Only supported locations are displayed. We recommend that you select the same location of your database server to host SSISDB.

4. For Node Size, select the size of the node in your integration runtime cluster. Only supported node sizes are displayed. Select a large node size (scale up) if you want to run many compute-intensive or memory-intensive packages.

5. For Node Number, select the number of nodes in your integration runtime cluster. Only supported node numbers are displayed. Select a large cluster with many nodes (scale out) if you want to run many packages in parallel.

6. For Edition/License, select the SQL Server edition for your integration runtime: Standard or Enterprise. Select Enterprise if you want to use advanced features on your integration runtime.

7. For Save Money, select the Azure Hybrid Benefit option for your integration runtime: Yes or No. Select Yes if you want to bring your own SQL Server license with Software Assurance to benefit from cost savings with hybrid use.

8. Select Continue.

Deployment settings page

On the Deployment settings page of Integration runtime setup pane, you have the options to create SSISDB and or Azure-SSIS IR package stores.

Creating SSISDB

On the Deployment settings page of Integration runtime setup pane, if you want to deploy your packages into SSISDB (Project Deployment Model), select the Create SSIS catalog (SSISDB) hosted by Azure SQL Database server/Managed Instance to store your projects/packages/environments/execution logs check box. Alternatively, if you want to deploy your packages into file system, Azure Files, or SQL Server database (MSDB) hosted by Azure SQL Managed Instance (Package Deployment Model), no need to create SSISDB nor select the check box.

Regardless of your deployment model, if you want to use SQL Server Agent hosted by Azure SQL Managed Instance to orchestrate/schedule your package executions, it's enabled by SSISDB, so select the check box anyway. For more information, see Schedule SSIS package executions via Azure SQL Managed Instance Agent.

If you select the check box, complete the following steps to bring your own database server to host SSISDB that we'll create and manage on your behalf.

1. For Subscription, select the Azure subscription that has your database server to host SSISDB.

2. For Location, select the location of your database server to host SSISDB. We recommend that you select the same location of your integration runtime.

3. For Catalog Database Server Endpoint, select the endpoint of your database server to host SSISDB.

   Based on the selected database server, the SSISDB instance can be created on your behalf as a single database, as part of an elastic pool, or in a managed instance. It can be accessible in a public network or by joining a virtual network. For guidance in choosing the type of database server to host SSISDB, see Compare SQL Database and SQL Managed Instance.

   If you select an Azure SQL Database server with IP firewall rules/virtual network service endpoints or a managed instance with private endpoint to host SSISDB, or if you require access to on-premises data without configuring a self-hosted IR, you need to join your Azure-SSIS IR to a virtual network. For more information, see Join an Azure-SSIS IR to a virtual network.

4. Select either the Use Microsoft Entra authentication with the system managed identity for Data Factory or Use Microsoft Entra authentication with a user-assigned managed identity for Data Factory check box to choose Microsoft Entra authentication method for Azure-SSIS IR to access your database server that hosts SSISDB. Don't select any of the check boxes to choose SQL authentication method instead.

   If you select any of the check boxes, you'll need to add the specified system/user-assigned managed identity for your data factory into a Microsoft Entra group with access permissions to your database server. If you select the Use Microsoft Entra authentication with a user-assigned managed identity for Data Factory check box, you can then select any existing credentials created using your specified user-assigned managed identities or create new ones. For more information, see Enable Microsoft Entra authentication for an Azure-SSIS IR.

5. For Admin Username, enter the SQL authentication username for your database server that hosts SSISDB.

6. For Admin Password, enter the SQL authentication password for your database server that hosts SSISDB.

7. Select the Use dual standby Azure-SSIS Integration Runtime pair with SSISDB failover check box to configure a dual standby Azure SSIS IR pair that works in sync with Azure SQL Database/Managed Instance failover group for business continuity and disaster recovery (BCDR).

   If you select the check box, enter a name to identify your pair of primary and secondary Azure-SSIS IRs in the Dual standby pair name text box. You need to enter the same pair name when creating your primary and secondary Azure-SSIS IRs.

   For more information, see Configure your Azure-SSIS IR for BCDR.

8. For Catalog Database Service Tier, select the service tier for your database server to host SSISDB. Select the Basic, Standard, or Premium tier, or select an elastic pool name.

Select Test connection when applicable, and if it's successful, select Continue.

Creating Azure-SSIS IR package stores

On the Deployment settings page of Integration runtime setup pane, if you want to manage your packages that are deployed into MSDB, file system, or Azure Files (Package Deployment Model) with Azure-SSIS IR package stores, select the Create package stores to manage your packages that are deployed into file system/Azure Files/SQL Server database (MSDB) hosted by Azure SQL Managed Instance check box.

Azure-SSIS IR package store allows you to import/export/delete/run packages and monitor/stop running packages via SSMS similar to the legacy SSIS package store. For more information, see Manage SSIS packages with Azure-SSIS IR package stores.

If you select this check box, you can add multiple package stores to your Azure-SSIS IR by selecting New. Conversely, one package store can be shared by multiple Azure-SSIS IRs.

On the Add package store pane, complete the following steps.

1. For Package store name, enter the name of your package store.

2. For Package store linked service, select your existing linked service that stores the access information for file system/Azure Files/Azure SQL Managed Instance where your packages are deployed or create a new one by selecting New. On the New linked service pane, complete the following steps.

   Note

   You can use either Azure File Storage or File System linked services to access Azure Files. If you use Azure File Storage linked service, Azure-SSIS IR package store supports only Basic (not Account key nor SAS URI) authentication method for now.

   

   1. For Name, enter the name of your linked service.

   2. For Description, enter the description of your linked service.

   3. For Type, select Azure File Storage, Azure SQL Managed Instance, or File System.

   4. You can ignore Connect via integration runtime, since we always use your Azure-SSIS IR to fetch the access information for package stores.

   5. If you select Azure File Storage, for Authentication method, select Basic, and then complete the following steps.

      1. For Account selection method, select From Azure subscription or Enter manually.

      2. If you select From Azure subscription, select the relevant Azure subscription, Storage account name, and File share.

      3. If you select Enter manually, enter \\<storage account name>.file.core.chinacloudapi.cn\<file share name> for Host, Azure\<storage account name> for Username, and <storage account key> for Password or select your Azure Key Vault where it's stored as a secret.

   6. If you select Azure SQL Managed Instance, complete the following steps.

      1. Select Connection string or your Azure Key Vault where it's stored as a secret.

      2. If you select Connection string, complete the following steps.

         1. For Account selection method, if you choose From Azure subscription, select the relevant Azure subscription, Server name, Endpoint type and Database name. If you choose Enter manually, complete the following steps.

            1. For Fully qualified domain name, enter <server name>.<dns prefix>.database.chinacloudapi.cn or <server name>.public.<dns prefix>.database.chinacloudapi.cn,3342 as the private or public endpoint of your Azure SQL Managed Instance, respectively. If you enter the private endpoint, Test connection isn't applicable, since ADF UI can't reach it.

            2. For Database name, enter msdb.

         2. For Authentication type, select SQL Authentication, Managed Identity, Service Principal, or User-Assigned Managed Identity.

            • If you select SQL Authentication, enter the relevant Username and Password or select your Azure Key Vault where it's stored as a secret.

            • If you select Managed Identity, grant the system managed identity for your ADF access to your Azure SQL Managed Instance.

            • If you select Service Principal, enter the relevant Service principal ID and Service principal key or select your Azure Key Vault where it's stored as a secret.

            • If you select User-Assigned Managed Identity, grant the specified user-assigned managed identity for your ADF access to your Azure SQL Managed Instance. You can then select any existing credentials created using your specified user-assigned managed identities or create new ones.

   7. If you select File system, enter the UNC path of folder where your packages are deployed for Host, as well as the relevant Username and Password or select your Azure Key Vault where it's stored as a secret.

   8. Select Test connection when applicable and if it's successful, select Create.

3. Your added package stores will appear on the Deployment settings page. To remove them, select their check boxes, and then select Delete.

Select Test connection when applicable and if it's successful, select Continue.

Advanced settings page

On the Advanced settings page of Integration runtime setup pane, complete the following steps.

1. For Maximum Parallel Executions Per Node, select the maximum number of packages to run concurrently per node in your integration runtime cluster. Only supported package numbers are displayed. Select a low number if you want to use more than one core to run a single large package that's compute or memory intensive. Select a high number if you want to run one or more small packages in a single core.

2. Select the Customize your Azure-SSIS Integration Runtime with additional system configurations/component installations check box to choose whether you want to add standard/express custom setups on your Azure-SSIS IR. For more information, see Custom setup for an Azure-SSIS IR.

   If you select the check box, complete the following steps.

   

   1. For Custom setup container SAS URI, enter the SAS URI of your container where you store scripts and associated files for standard custom setups.

   2. For Express custom setup, select New to open the Add express custom setup panel and then select any types under the Express custom setup type dropdown menu, e.g. Run cmdkey command, Add environment variable, Install licensed component, etc.

      If you select the Install licensed component type, you can then select any integrated components from our ISV partners under the Component name dropdown menu and if required, enter the product license key/upload the product license file that you purchased from them into the License key/License file box.

      Your added express custom setups will appear on the Advanced settings page. To remove them, you can select their check boxes and then select Delete.

3. Select the Select a VNet for your Azure-SSIS Integration Runtime to join, allow ADF to create certain network resources, and optionally bring your own static public IP addresses check box to choose whether you want to join your Azure-SSIS IR to a virtual network.

   Select it if you use Azure SQL Database server configured with a virtual network service endpoint/IP firewall rule/private endpoint or Azure SQL Managed Instance that joins a virtual network to host SSISDB, or if you require access to on-premises data (that is, you have on-premises data sources/destinations in your SSIS packages) without configuring a self-hosted IR. For more information, see Join Azure-SSIS IR to a virtual network.

   If you select the check box, complete the following steps.

   

   1. For Subscription, select the Azure subscription that has your virtual network.

   2. For Location, the same location of your integration runtime is selected.

   3. For Type, select the type of your virtual network: Azure Resource Manager Virtual Network/classic virtual network. We recommend that you select Azure Resource Manager Virtual Network, because classic virtual network will be deprecated soon.

   4. For VNet Name, select the name of your virtual network. It should be the same one used to configure a virtual network service endpoint/private endpoint for your Azure SQL Database server that hosts SSISDB. Or it should be the same one joined by your Azure SQL Managed Instance that hosts SSISDB. Or it should be the same one connected to your on-premises network. Otherwise, it can be any virtual network to bring your own static public IP addresses for Azure-SSIS IR.

   5. For Subnet Name, select the name of subnet for your virtual network. It should be the same one used to configure a virtual network service endpoint for your Azure SQL Database server that hosts SSISDB. Or it should be a different subnet from the one joined by your Azure SQL Managed Instance that hosts SSISDB. Otherwise, it can be any subnet to bring your own static public IP addresses for Azure-SSIS IR.

   6. For VNet injection method, select the method of your virtual network injection: Express/Standard.

      To compare these methods, see the Compare the standard and express virtual network injection methods article.

      If you select Express, see the Express virtual network injection method article.

      If you select Standard, see the Standard virtual network injection method article. With this method, you can also:

      1. Select the Bring static public IP addresses for your Azure-SSIS Integration Runtime check box to choose whether you want to bring your own static public IP addresses for Azure-SSIS IR, so you can allow them on the firewall of your data stores.

         If you select the check box, complete the following steps.

         1. For First static public IP address, select the first static public IP address that meets the requirements for your Azure-SSIS IR. If you don't have any, click the Create new link to create static public IP addresses on Azure portal and then click the refresh button here, so you can select them.

         2. For Second static public IP address, select the second static public IP address that meets the requirements for your Azure-SSIS IR. If you don't have any, click the Create new link to create static public IP addresses on Azure portal and then click the refresh button here, so you can select them.

4. Select the Set up Self-Hosted Integration Runtime as a proxy for your Azure-SSIS Integration Runtime check box to choose whether you want to configure a self-hosted IR as proxy for your Azure-SSIS IR. For more information, see Set up a self-hosted IR as proxy.

   If you select the check box, complete the following steps.

   

   1. For Self-Hosted Integration Runtime, select your existing self-hosted IR as a proxy for Azure-SSIS IR.

   2. For Staging Storage Linked Service, select your existing Azure Blob storage linked service or create a new one for staging.

   3. For Staging Path, specify a blob container in your selected Azure Blob storage account or leave it empty to use a default one for staging.

5. Select VNet Validation. If the validation is successful, select Continue.

On the Summary page, review all settings for your Azure-SSIS IR, bookmark the recommended documentation links, and select Finish to start the creation of your integration runtime.

Connections pane

On the Connections pane of Manage hub, switch to the Integration runtimes page and select Refresh.

You can edit/reconfigure your Azure-SSIS IR by selecting its name. You can also select the relevant buttons to monitor/start/stop/delete your Azure-SSIS IR, auto-generate an ADF pipeline with Execute SSIS Package activity to run on your Azure-SSIS IR, and view the JSON code/payload of your Azure-SSIS IR. Editing/deleting your Azure-SSIS IR can only be done when it's stopped.

Azure SSIS integration runtimes in the portal

1. In the Azure Data Factory UI, switch to the Manage tab and then switch to the Integration runtimes tab on the Connections pane to view existing integration runtimes in your data factory.

   

2. Select New to create a new Azure-SSIS IR and open the Integration runtime setup pane.

   

3. In the Integration runtime setup pane, select the Lift-and-shift existing SSIS packages to execute in Azure tile, and then select Continue.

   

4. For the remaining steps to set up an Azure-SSIS IR, see the Provision an Azure SSIS integration runtime section.

Related content

• Create an Azure-SSIS IR via Azure PowerShell.
• Create an Azure-SSIS IR via Azure Resource Manager template.
• Deploy and run your SSIS packages on Azure-SSIS IR.

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

• Azure-SSIS IR. This article provides general conceptual information about IRs, including Azure-SSIS IR.
• 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, start, or delete your Azure-SSIS IR. It also shows you how to scale out your Azure-SSIS IR by adding more nodes.
• Deploy, run, and monitor SSIS packages in Azure
• Connect to SSISDB in Azure
• Connect to on-premises data stores with Windows authentication
• Schedule SSIS package executions in Azure