This is a collection of notes and links to resources about Azure Self-Hosted Integration Runtime (SHIR).
Azure Integration Runtime (Azure IR): This is the default and most widely used integration runtime in Azure Data Factory. It is a fully managed service that runs on Azure infrastructure and provides a secure and elastic compute environment for executing data movement and transformation activities. It supports connecting to a wide range of data sources, including Azure Storage, Azure SQL Database, and on-premises data sources. Azure IR is a good choice for scenarios that require high performance, scalability, and low maintenance overhead. However, it can only be used to connect to data sources that are accessible from the public cloud.
Self-Hosted Integration Runtime (Self-Hosted IR): This integration runtime is installed and managed on your own on-premises or Azure virtual machines (VMs). It is a good choice for scenarios where you need to connect to data sources that are not accessible from the public cloud, such as on-premises databases or file shares. Self-Hosted IR can also be used to run data integration tasks that require higher levels of security or that are sensitive to latency.
Azure-SSIS Integration Runtime (Azure-SSIS IR): This integration runtime utilizes SQL Server Integration Services (SSIS) packages to perform data integration tasks. It is a good choice for scenarios where you have existing SSIS packages that you want to run in Azure Data Factory. Azure-SSIS IR can also be used to integrate with on-premises SSIS environments.
There are also two types of Azure Data factories, Data Factory and Data Factory Managed Virtual Network. The latter is used when you want to connect to private endpoints in your Azure Virtual Network (VNet) from Azure Data Factory. This is a good choice for scenarios where you need to connect to data sources that are not accessible from the public cloud. For example, you can use Data Factory Managed Virtual Network to connect to Azure SQL Database Managed Instance, Azure Synapse Analytics, and Azure Storage accounts that are secured with VNet service endpoints.
The Self-Hosted Integration Runtime is a component that can be installed on an on-premises machine or a virtual machine (VM) in a private network. It allows you to access data sources that are inside a private network. It also allows you to copy data to and from data sources that are not supported by the Azure Integration Runtime. The Self-Hosted Integration Runtime can be used in the following scenarios:
While using self-hosted IR, you can connect to data source both on premise and in azure is an option there is also a second option to use managed virtual network to connect using private endpoints. example B shows the difference between the two options.
The third option and last option is to connect using the public interface of the data source. This the least secure option and should be avoided if possible. Due to the nature of public being possible for external access, it is also the most vulnerable option.
