Manage your integration service environment (ISE) in Azure Logic Apps
This article shows how to perform management tasks for your integration service environment (ISE), for example:
Manage the resources such as multi-tenant based logic apps, connections, integration accounts, and connectors in your ISE.
Check your ISE's network health.
Add capacity, restart your ISE, or delete your ISE, follow the steps in this topic. To add these artifacts to your ISE, see Add artifacts to your integration service environment.
View your ISE
Sign in to the Azure portal.
In the portal's search box, enter "integration service environments", and then select Integration Service Environments.
From the results list, select your integration service environment.
Continue to the next sections to find logic apps, connections, connectors, or integration accounts in your ISE.
Check network health
On your ISE menu, under Settings, select Network health. This pane shows the health status for your subnets and outbound dependencies on other services.
If your ISE's network becomes unhealthy, the internal App Service Environment (ASE) that's used by your ISE can also become unhealthy. If the ASE is unhealthy for more than seven days, the ASE is suspended. To resolve this state, check your virtual network setup. Resolve any problems that you find, and then restart your ISE. Otherwise, after 90 days, the suspended ASE is deleted, and your ISE becomes unusable. So, make sure that you keep your ISE healthy to permit the necessary traffic.
For more information, see these topics:
Manage your logic apps
You can view and manage the logic apps that are in your ISE.
On your ISE menu, under Settings, select Logic apps.
To remove logic apps that you no longer need in your ISE, select those logic apps, and then select Delete. To confirm that you want to delete, select Yes.
If you delete and recreate a child logic app, you must resave the parent logic app. The recreated child app will have different metadata. If you don't resave the parent logic app after recreating its child, your calls to the child logic app will fail with an error of "unauthorized." This behavior applies to parent-child logic apps, for example, those that use artifacts in integration accounts or call Azure functions.
Manage API connections
You can view and manage the connections that were created by the logic apps running in your ISE.
On your ISE menu, under Settings, select API connections.
To remove connections that you no longer need in your ISE, select those connections, and then select Delete. To confirm that you want to delete, select Yes.
Manage ISE connectors
You can view and manage the API connectors that are deployed to your ISE.
On your ISE menu, under Settings, select Managed connectors.
To remove connectors that you don't want available in your ISE, select those connectors, and then select Delete. To confirm that you want to delete, select Yes.
Manage custom connectors
You can view and manage the custom connectors that you deployed to your ISE.
On your ISE menu, under Settings, select Custom connectors.
To remove custom connectors that you no longer need in your ISE, select those connectors, and then select Delete. To confirm that you want to delete, select Yes.
Manage integration accounts
On your ISE menu, under Settings, select Integration accounts.
To remove integration accounts from your ISE when no longer needed, select those integration accounts, and then select Delete.
Add ISE capacity
The Premium ISE base unit has fixed capacity, so if you need more throughput, you can add more scale units, either during creation or afterwards. The Developer SKU doesn't include the capability to add scale units.
In the Azure portal, go to your ISE.
To review usage and performance metrics for your ISE, on your ISE menu, select Overview.
Under Settings, select Scale out. On the Configure pane, select from these options:
- Manual scale: Scale based on the number of processing units that you want to use.
- Custom autoscale: Scale based on performance metrics by selecting from various criteria and specifying the threshold conditions for meeting that criteria.
After you select Manual scale, for Additional capacity, select the number of scaling units that you want to use.
When you're done, select Save.
After you select Custom autoscale, for Autoscale setting name, provide a name for your setting and optionally, select the Azure resource group where the setting belongs.
For the Default condition, select either Scale based on a metric or Scale to a specific instance count.
If you choose instance-based, enter the number for the processing units, which is a value from 0 to 10.
If you choose metric-based, follow these steps:
In the Rules section, select Add a rule.
On the Scale rule pane, set up your criteria and action to take when the rule triggers.
For Instance limits, specify these values:
- Minimum: The minimum number of processing units to use
- Maximum: The maximum number of processing units to use
- Default: If any problems happen while reading the resource metrics, and the current capacity is below the default capacity, autoscaling scales out to the default number of processing units. However, if the current capacity exceeds the default capacity, autoscaling doesn't scale in.
To add another condition, select Add scale condition.
When you're finished with your autoscale settings, save your changes.
If you change your DNS server or DNS server settings, you have to restart your ISE so that the ISE can pick up those changes. Restarting a Premium SKU ISE doesn't result in downtime due to redundancy and components that restart one at a time during recycling. However, a Developer SKU ISE experiences downtime because no redundancy exists. For more information, see ISE SKUs.
In the Azure portal, go to your ISE.
On the ISE menu, select Overview. On the Overview toolbar, Restart.
Before you delete an ISE that you no longer need or an Azure resource group that contains an ISE, check that you have no policies or locks on the Azure resource group that contains these resources or on your Azure virtual network because these items can block deletion.
After you delete your ISE, you might have to wait up to 9 hours before you try to delete your Azure virtual network or subnets.