Connect to Azure virtual networks from Azure Logic Apps by using an integration service environment (ISE)

For scenarios where your logic apps and integration accounts need access to an Azure virtual network, create an integration service environment (ISE). An ISE is a private and isolated environment that uses dedicated storage and other resources that are kept separate from the public or "global" Logic Apps service. This separation also reduces any impact that other Azure tenants might have on your apps' performance. Your ISE is injected into to your Azure virtual network, which then deploys the Logic Apps service into your virtual network. When you create a logic app or integration account, select this ISE as their location. Your logic app or integration account can then directly access resources, such as virtual machines (VMs), servers, systems, and services, in your virtual network.

Select integration service environment

This article shows how to complete these tasks:

  • Make sure any necessary ports on a virtual network are open so that traffic can travel through your integration service environment (ISE) across the subnets in that virtual network.

  • Create your integration service environment (ISE).

  • Create a logic app that can run in your ISE.

  • Create an integration account for your logic apps in your ISE.

For more information about integration service environments, see Access to Azure Virtual Network resources from Azure Logic Apps.


  • An Azure subscription. If you don't have an Azure subscription, sign up for a free Azure account.


    Logic apps, built-in triggers, built-in actions, and connectors that run in your ISE use a pricing plan different from the consumption-based pricing plan. For more information, see Logic Apps pricing.

  • An Azure virtual network. If you don't have a virtual network, learn how to create an Azure virtual network.

    • Your virtual network must have four empty subnets for deploying and creating resources in your ISE. You can create these subnets in advance, or you can wait until you create your ISE where you can create subnets at the same time. Learn more about subnet requirements.


      If you use ExpressRoute, which provides a private connection to Microsoft cloud services, you must create a route table that has the following route and link that table with each subnet used by your ISE:

      Name: <route-name>
      Address prefix:
      Next hop: Internet

    • Make sure that your virtual network makes these ports available so your ISE works correctly and stays accessible.

  • If you want to use custom DNS servers for your Azure virtual network, set up those servers by following these steps before you deploy your ISE to your virtual network. Otherwise, each time you change your DNS server, you also have to restart your ISE, which is a capability that's available with ISE public preview.

  • Basic knowledge about how to create logic apps

Check network ports

When you use an integration service environment (ISE) with a virtual network, a common setup problem is having one or more blocked ports. The connectors that you use for creating connections between your ISE and the destination system might also have their own port requirements. For example, if you communicate with an FTP system by using the FTP connector, make sure the port you use on that FTP system, such as port 21 for sending commands, is available.

To control the traffic across the virtual network's subnets where you deploy your ISE, you can optionally set up network security groups (NSGs) in your virtual network by filtering network traffic across subnets. If you choose this route, make sure that your ISE opens specific ports, as described in the following table, on the virtual network that uses the NSGs. If you have existing NSGs or firewalls in your virtual network, make sure that they open these ports. That way, your ISE stays accessible and can work correctly so that you don't lose access to your ISE. Otherwise, if any required ports are unavailable, your ISE stops working.

These tables describe the ports in your virtual network that your ISE uses and where those ports get used. The Resource Manager service tags represents a group of IP address prefixes that help minimize complexity when creating security rules.


For internal communication inside your subnets, ISE requires that you open all ports within those subnets.

Purpose Direction Ports Source service tag Destination service tag Notes
Communication from Azure Logic Apps Outbound 80 & 443 VirtualNetwork Internet The port depends on the external service with which the Logic Apps service communicates
Azure Active Directory Outbound 80 & 443 VirtualNetwork AzureActiveDirectory
Azure Storage dependency Outbound 80 & 443 VirtualNetwork Storage
Intersubnet communication Inbound & Outbound 80 & 443 VirtualNetwork VirtualNetwork For communication between subnets
Communication to Azure Logic Apps Inbound 443 Internet VirtualNetwork The IP address for the computer or service that calls any request trigger or webhook that exists in your logic app. Closing or blocking this port prevents HTTP calls to logic apps with request triggers.
Logic app run history Inbound 443 Internet VirtualNetwork The IP address for the computer from which you view the logic app's run history. Although closing or blocking this port doesn't prevent you from viewing the run history, you can't view the inputs and outputs for each step in that run history.
Connection management Outbound 443 VirtualNetwork Internet
Publish Diagnostic Logs & Metrics Outbound 443 VirtualNetwork AzureMonitor
Communication from Azure Traffic Manager Inbound 443 AzureTrafficManager VirtualNetwork
Logic Apps Designer - dynamic properties Inbound 454 Internet VirtualNetwork Requests come from the Logic Apps access endpoint inbound IP addresses in that region.
App Service Management dependency Inbound 454 & 455 AppServiceManagement VirtualNetwork
Connector deployment Inbound 454 & 3443 Internet VirtualNetwork Necessary for deploying and updating connectors. Closing or blocking this port causes ISE deployments to fail and prevents connector updates or fixes.
Azure SQL dependency Outbound 1433 VirtualNetwork SQL
Azure Resource Health Outbound 1886 VirtualNetwork Internet For publishing health status to Resource Health
API Management - management endpoint Inbound 3443 APIManagement VirtualNetwork
Dependency from Log to Event Hub policy and monitoring agent Outbound 5672 VirtualNetwork EventHub
Access Azure Cache for Redis Instances between Role Instances Inbound
6379-6383 VirtualNetwork VirtualNetwork Also, for ISE to work with Azure Cache for Redis, you must open these outbound and inbound ports described in the Azure Cache for Redis FAQ.
Azure Load Balancer Inbound * AzureLoadBalancer VirtualNetwork

Create your ISE

To create your integration service environment (ISE), follow these steps:

  1. In the Azure portal, on the main Azure menu, select Create a resource. In the search box, enter "integration service environment" as your filter.

    Create new resource

  2. On the Integration Service Environment creation pane, choose Create.

    Choose "Create"

  3. Provide these details for your environment, and then choose Review + create, for example:

    Provide environment details

    Property Required Value Description
    Subscription Yes <Azure-subscription-name> The Azure subscription to use for your environment
    Resource group Yes <Azure-resource-group-name> The Azure resource group where you want to create your environment
    Integration Service Environment Name Yes <environment-name> The name to give your environment
    Location Yes <Azure-datacenter-region> The Azure datacenter region where to deploy your environment
    Additional capacity Yes 0 to 10 The number of additional processing units to use for this ISE resource. To add capacity after creation, see Add ISE capacity.
    Virtual network Yes <Azure-virtual-network-name> The Azure virtual network where you want to inject your environment so logic apps in that environment can access your virtual network. If you don't have a network, create an Azure virtual network first.

    Important: You can only perform this injection when you create your ISE.

    Subnets Yes <subnet-resource-list> An ISE requires four empty subnets for creating resources in your environment. To create each subnet, follow the steps under this table.

    Create subnet

    To create resources in your environment, your ISE needs four empty subnets that aren't delegated to any service. You can't change these subnet addresses after you create your environment. Each subnet must meet these criteria:

    • Has a name that starts with an alphabetic character or an underscore, and doesn't have these characters: <, >, %, &, \\, ?, /

    • Uses the Classless Inter-Domain Routing (CIDR) format and a Class B address space.

    • Uses at least a /27 in the address space because each subnet must have 32 addresses as the minimum. For example:

      • has 32 addresses because 2(32-27) is 25 or 32.

      • has 256 addresses because 2(32-24) is 28 or 256.

      • has only 16 addresses and is too small because 2(32-28) is 24 or 16.

      To learn more about calculating addresses, see IPv4 CIDR blocks.

    • If you use ExpressRoute, remember to create a route table that has the following route and link that table with each subnet used by your ISE:

      Name: <route-name>
      Address prefix:
      Next hop: Internet

    1. Under the Subnets list, choose Manage subnet configuration.

      Manage subnet configuration

    2. On the Subnets pane, choose Subnet.

      Add subnet

    3. On the Add subnet pane, provide this information.

      • Name: The name for your subnet
      • Address range (CIDR block): Your subnet's range in your virtual network and in CIDR format

      Add subnet details

    4. When you're done, choose OK.

    5. Repeat these steps for three more subnets.


      If the subnets you try to create aren't valid, the Azure portal shows a message, but doesn't block your progress.

  4. After Azure successfully validates your ISE information, choose Create, for example:

    After successful validation, choose "Create"

    Azure starts deploying your environment, but this process might take up to two hours before finishing. To check deployment status, on your Azure toolbar, choose the notifications icon, which opens the notifications pane.

    Check deployment status

    If deployment finishes successfully, Azure shows this notification:

    Deployment succeeded

    Otherwise, follow the Azure portal instructions for troubleshooting deployment.


    If deployment fails or you delete your ISE, Azure might take up to an hour before releasing your subnets. This delay means means you might have to wait before reusing those subnets in another ISE.

    If you delete your virtual network, Azure generally takes up to two hours before releasing up your subnets, but this operation might take longer. When deleting virtual networks, make sure that no resources are still connected. See Delete virtual network.

  5. To view your environment, choose Go to resource if Azure doesn't automatically go to your environment after deployment finishes.

For more information about creating subnets, see Add a virtual network subnet.

Create logic app - ISE

To create logic apps that run in your integration service environment (ISE), create your logic apps in the usual way except when you set the Location property, select your ISE from the Integration service environments section, for example:

Select integration service environment

For differences in how triggers and actions work and how they're labeled when you use an ISE compared to the global Logic Apps service, see Isolated versus global in the ISE overview.

Create integration account - ISE

If you want to use an integration account with logic apps in an integration service environment (ISE), that integration account must use the same environment as the logic apps. Logic apps in an ISE can reference only integration accounts in the same ISE.

To create an integration account that uses an ISE, create your integration account in the usual way except when you set the Location property, select your ISE from the Integration service environments section, for example:

Select integration service environment

Add ISE capacity

Your ISE base unit has fixed capacity, so if you need more throughput, you can add more scale units. You can autoscale based on performance metrics or based on a number of additional processing units. If you choose autoscaling based on metrics, you can choose from various criteria and specify the threshold conditions for meeting that criteria.

  1. In the Azure portal, find your ISE.

  2. To review usage and performance metrics for your ISE, on your ISE's main menu, select Overview.

    View usage for ISE

  3. To set up autoscaling, under Settings, select Scale out. On the Configure tab, choose Enable autoscale.

    Turn on autoscaling

  4. For Autoscale setting name, provide a name for your setting.

  5. In the Default section, choose either Scale based on a metric or Scale to a specific instance count.

    • If you choose instance-based, enter the number of processing units between 0 and 10 inclusively.

    • If you choose metric-based, follow these steps:

      1. In the Rules section, choose Add a rule.

      2. On the Scale rule pane, set up your criteria and action to take when the rule triggers.

      3. When you're done, choose Add.

  6. When you're finished with your autoscale settings, save your changes.

Next steps