Integration Service Environment Template

Last updated: 25/09/2019

Template that creates a virtual network, 4 subnets, and then an Integration Service Environment (ISE), including non-native connectors. Use as a base for templates that require a Logic Apps ISE.

This Azure Resource Manager (ARM) template was created by a member of the community and not by Microsoft. Each ARM template is licensed to you under a licence agreement by its owner, not Microsoft. Microsoft is not responsible for ARM templates provided and licensed by community members and does not screen for security, compatibility or performance. Community ARM templates are not supported under any Microsoft support programme or service, and are made available AS IS without warranty of any kind.


Parameter Name Description
integrationServiceEnvironmentName The name of the Integration Service Environment.
location Location for all resources.
integrationServiceEnvironmentSku The SKU for the Integration Service Environment, either Developer or Premium.
skuCapacity The number of scale units for the Integration Service Environment. 0 is the base unit.
accessEndpointType The type of access endpoint to use for the Integration Service Environment. The endpoint determine whether request or webhook triggers on logic apps in the Integration Service Environment can receive calls from outside the virtual network.
managedConnectors The list of managed connectors to deploy into the ISE in JSON array format (e.g. ["sql", "ftp" ...]). The values must be from this list: sql;ftp;azureblob;azurefile;azurequeues;azuretables;sftpwithssh;edifact;x12;servicebus;documentdb;eventhubs;mq;sqldw;db2;smtp;si3270
vnetName The name of the VNET for ISE to be deployed into.
vnetAddressPrefix The VNET address prefix. For example,
subnet1Prefix The prefix for the first ISE subnet. For example,
subnet1Name The name of the first ISE subnet.
subnet2Prefix The prefix for the second ISE subnet. For example,
subnet2Name The name of the second ISE subnet.
subnet3Prefix The prefix for the third ISE subnet. For example,
subnet3Name The name of the third ISE subnet.
subnet4Prefix The prefix for the fourth ISE subnet. For example,
subnet4Name The name of the fourth ISE subnet.
rebuildVNET After the first deployment, you don't need to recreate the VNET. When set to false this will skip the VNET and subnet deployment.

Use the template


New-AzResourceGroup -Name <resource-group-name> -Location <resource-group-location> #use this command when you need to create a new resource group for your deployment
New-AzResourceGroupDeployment -ResourceGroupName <resource-group-name> -TemplateUri
Installing and configuring Azure PowerShell

Command line

az group create --name <resource-group-name> --location <resource-group-location> #use this command when you need to create a new resource group for your deployment
az group deployment create --resource-group <my-resource-group> --template-uri
Installing and configuring the Azure cross-platform command-line interface

More templates by Thiago Almeida