Integration Service Environment – Part 2


A quick recap related to my last blog post – As you can see the ISE is injected into your Virtual network/VNet. You can either connect to the resources within your Virtual network, use service endpoints to connect to SQL, service bus etc or connect to any on-premise service like SQL, SAP, FTP via express route.

In today’s blog post we are going to perform the below 2 activities –

  1. Create an Integration Service Environment within your VNet.
  2. Add Logic App to Integration Service Environment.

As a pre-requisite – I have already created a Virtual Network well in advance. Also please note while creating an Integration Service environment, I noticed it requires 4 Subnets within your VNet or else it throws below Error message.



Login to your Azure portal, navigate to resources and click on Integration Service Environment.


Fill in all the appropriate values as below and click on Review + Create.

Some Key points to Note below –

  • Additional Capacity – The no of additional processing units  to use for this ISE resource. Can range from ( 0-10 ).
  • Access endpoints
    • Internal – Allows logic app to be called from within the VNET
    • External – Allows logic app to be called from public endpoints
  • Virtual Network


Please note it takes around 40 to 45 minutes for your ISE environment to be deployed. Now lets focus on the final part. Injecting your Logic App within the Integration Service Environment.


You can also add Integration accounts to your ISE. In case you want to use Integration Accounts along with Logic Apps both must exists in the same Integration Service Environment.



Navigate to Azure Portal and click on resource and select Logic App. As you can see below in the Location drop-down. Rather than selecting any  Azure Regions we select the Integration Service environment created above and click on Create. Once created this logic-app will now run in its own isolated environment.


Couple of things that can help. As you see the image below for few built-in triggers and action there is a word [CORE] associated with it. It depicts that these triggers and actions will run in the same Integration Service Environment.


Also you will noticed there are few connectors which has 2 versions.


  1. LEFT – Running in Global Logic App service environment.
  2. RIGHT – Running in Integration Service Environment as your Logic App.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s