Changing Integration Runtime Sub-Type in ADF

Oleksandr K 20 Reputation points
2025-05-19T12:23:52.0733333+00:00

Hello,

We currently have several Integration Runtimes configured in our Azure Data Factory (ADF), all of which were initially created with the Public sub-type.

We are considering changing them to the Managed Virtual Network sub-type. Upon reviewing the definitions in our repository, the only apparent difference between the two configurations is an additional property for the Managed Virtual Network sub-type, for example:


"managedVirtualNetwork": {
  "type": "ManagedVirtualNetworkReference",
  "referenceName": "default"
}

Could you please confirm if it is possible to change the sub-type of an existing Integration Runtime from Public to Managed Virtual Network? If so, what is the recommended approach or best practice for performing this change?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
{count} votes

Answer accepted by question author
  1. Sina Salam 26,661 Reputation points Volunteer Moderator
    2025-05-19T22:45:56.7866667+00:00

    Hello Oleksandr K,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you would like to change Integration Runtime Sub-Type in ADF.

    Regarding your question:

    Can You Change the Sub-Type of an Existing IR?

    Yes, you can enable Managed Virtual Network on an existing Azure Integration Runtime, except for the default auto-resolve IR. You can enable it either on a new Azure integration runtime or an existing one THAT is not default auto-resolve IR. The AutoResolveIntegrationRuntime is the default Azure Integration Runtime provided by ADF. It automatically selects the region closest to the data source or sink and is **not customizable in terms of enabling Managed Virtual Network (Managed VNet). The link provides you step by steps on how you can achieve this: https://learn.microsoft.com/en-us/azure/data-factory/tutorial-managed-virtual-network-migrate

    To clear any iota of confusion:

    1. Your original question was about Azure IR, not SSIS or self-hosted.
    2. You can confirm if you're have Default AutoResolveIntegrationRuntime by the following using PowerShell command:
         Get-AzDataFactoryV2IntegrationRuntime `
           -ResourceGroupName "<your-rg>" `
           -DataFactoryName "<your-adf-name>" `
           -Name "AutoResolveIntegrationRuntime"
      
      Check the output:
      • If the type is "Azure" and location is "AutoResolve" or not explicitly set, it's the default IR.
      • There will be no managedVirtualNetwork property.
      • But if not, follow the link above with the steps to modify and migrate it or the below:
    3. Go to Azure Data Factory > Manage > Integration Runtimes
      • Select the Azure IR you want to modify.
      • Click “Edit” and enable the Managed Virtual Network option.
      • Save and publish the changes.
      • Update Linked Services if needed to use **Managed Private Endpoints.
      • Test connectivity to ensure private endpoints and firewall rules are correctly configured.
    4. There is complete solution to help you deploy a Managed Virtual Network (Managed VNet) Integration Runtime (IR) in Azure Data Factory using:
      • ARM Template
      • JSON Snippet
      • Bicep Script

    I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.