Skip to content
TheChatArchiveThe Chat Archive
gpt-4.1-mini-2025-04-14· OpenAIAi2 WildChat-4.8M (AI2)

What is integration runtime in azure and how many types and what purpose they serve?

  1. User

    What is integration runtime in azure and how many types and what purpose they serve?

  2. Assistant

    Integration Runtime (IR) in Azure Data Factory (ADF) and Azure Synapse Analytics is the compute infrastructure used to provide data integration capabilities across different network environments. It basically acts as the bridge to move data between various data stores and compute activities in data pipelines.


    What is Integration Runtime?

    • It is the compute environment that provides the data movement, data transformation, and SSIS package execution capabilities.
    • It enables you to move data, dispatch activities, and transform data either within the cloud or on-premises.

    Types of Integration Runtime

    There are three types of Integration Runtime in Azure:

    1. Azure Integration Runtime (Azure IR)
    2. Self-hosted Integration Runtime (Self-hosted IR)
    3. Azure-SSIS Integration Runtime (Azure-SSIS IR)

    1. Azure Integration Runtime

    • Purpose: Used for cloud-based data movement, dispatching, and data flow execution.
    • It runs in Azure and manages the network traffic and data movement securely between cloud data stores.
    • Supports data movement between supported cloud data stores (e.g., Azure Blob Storage, Azure SQL Database).
    • Supports transformation via Mapping Data Flows.
    • Automatically scales out based on workload.

    Use cases:

    • Copy data between cloud data stores.
    • Execute Mapping Data Flows.
    • Use when source and sink data stores are cloud-based.

    2. Self-hosted Integration Runtime

    • Purpose: Enables movement of data between on-premises (or private network) data stores and cloud, or among on-premises data stores.
    • Installed on a local machine or a virtual machine in your infrastructure.
    • Can act as a proxy to move data securely across firewalls.
    • Supports running activities on local machines, custom compute environments.
    • Supports hybrid data movement scenarios.

    Use cases:

    • Copy data from on-premises SQL Server, Oracle, file server, etc. to cloud.
    • Move data between on-premises data stores.
    • Access data in private network environments.
    • Run SSIS packages on-premises in hybrid mode (together with Azure-SSIS IR).

    3. Azure-SSIS Integration Runtime

    • Purpose: Dedicated runtime to lift & shift existing on-premises SSIS workloads to Azure.
    • Runs SSIS packages natively in a managed cluster in Azure.
    • Supports execution of SSIS packages within Azure Data Factory pipelines.
    • You can customize the cluster by installing additional components or scripts.

    Use cases:

    • Running SSIS packages migrated from on-premises SQL Server Integration Services.
    • Leveraging Azure scalability and flexibility for SSIS execution.
    • Hybrid running of SSIS packages with cloud storage.

    Summary Table

    Integration Runtime TypeLocationPurposeUse Cases
    Azure IRFully in Azure cloudCloud data movement and transformation (Mapping Data Flows)Cloud-to-cloud data movement, transformation
    Self-hosted IROn-premises or VMHybrid data movement, on-premises accessOn-premises to cloud, private network access
    Azure-SSIS Integration RuntimeAzure cloudRun SSIS packages natively in AzureMigrate and run SSIS packages on Azure

    In essence:

    • Use Azure IR for cloud-only data integration.
    • Use Self-hosted IR to bridge on-premises/private networks with Azure.
    • Use Azure-SSIS IR for executing SSIS packages in Azure.

    If you want, I can also provide details on how to set up these runtimes or considerations around security and performance!