Edit and manage logic app workflows in the Azure portal
Applies to: Azure Logic Apps (Consumption + Standard)
This guide shows how to manage Consumption or Standard logic app workflows using the Azure portal and perform tasks such as edit, disable, enable, and delete workflows.
An Azure account and subscription. If you don't have an Azure subscription, sign up for a free Azure account.
An existing Consumption or Standard logic app workflow
In the Azure portal search box, enter logic apps, and select Logic apps.
From the logic apps list, find your logic app resource by either browsing or filtering the list.
To open your logic app resource, select the app that you want to manage.
In the Azure portal, find and open your logic app resource.
From your logic app's menu, under Settings, select Properties.
On the Properties pane, you can view and copy the following information about your logic app resource, for example:
Consumption
- Name
- Resource ID
- Resource group
- Location
- Type
- Subscription Name
- Subscription ID
- Access Endpoint
- Runtime outgoing IP addresses
- Access endpoint IP addresses
- Connector outgoing IP addresses
Standard
- Status
- URL
- Virtual IP address
- Mode
- Outbound IP address
- Additional Outbound IP Addresses
- FTP/deployment user
- FTP host name
- FTP diagnostic logs
- FTP host name
- FTPS diagnostic logs
- Resource ID
- Location
- Resource Group
- Subscription name
- Subscription ID
When you create connections in a workflow using connectors managed by Microsoft, these connections are separate Azure resources with their own resource definitions and are hosted in global, multitenant Azure. Standard logic app workflows can also use built-in service provider connectors that natively run and are powered by the single-tenant Azure Logic Apps runtime. To view and manage these connections, follow these steps, based on the logic app resource type:
In the Azure portal, find and open your logic app resource.
From the logic app menu, under Workflows, select Connections.
Based on the connection type that you want to view, select one of the following options:
Option Description API Connections Connections created by globally hosted, multitenant Azure connectors. To view the underlying connection resource definition, select JSON View. Service Provider Connections Connections created by built-in, service provider connectors, based on the service provider interface implementation. To view more information about a specific connection instance, in the View Details column, select the eye icon. To view the selected connection's underlying resource definition, select JSON View. Function Connections Connections to functions in an associated function app. To view more information about a function, in the View Details column, select the eye icon. JSON View The underlying resource definitions for all connections across workflows in the logic app resource
While a Consumption logic app can have only one workflow, a Standard logic app resource can have multiple workflows. You can add blank workflows to a deployed Standard logic app resource and continue building the workflow in the Azure portal.
In the Azure portal, select your deployed Standard logic app resource.
On the logic app resource menu, under Workflows, select Workflows.
On the Workflows page toolbar, select Add > Add.
In the New workflow pane, provide the workflow name. Select either Stateful or Stateless > Create.
After the new workflow appears on the Workflows page, select that workflow to open the designer so you can build your workflow.
Deployed Consumption and Standard logic apps have different ways to disable and enable their activity.
You can stop, start, or restart a Standard logic app, which affects all workflow instances. You can also restart a Standard logic app without first stopping its activity. Your Standard logic app can have multiple workflows, so you can either stop the entire logic app, or you can disable or enable individual workflows.
Stopping a Standard logic app versus disabling a child workflow have different effects, so review the following considerations before you continue:
Disabling a Standard logic app affects all its workflow instances in the following ways:
Azure Logic Apps immediately cancels all in-progress and pending workflow runs.
Azure Logic Apps doesn't create or run new workflow instances.
You can resubmit workflow runs while the logic app is disabled.
Workflow triggers don't fire while the logic app is disabled. However, the trigger states remember the point where you disabled the logic app. When you re-enable the logic app, the triggers fire for all unprocessed items since the last time that the corresponding workflows ran.
To stop the triggers from firing on all unprocessed items since the last time that the workflows ran, you must clear the trigger state for each workflow.
You can disable or enable one or multiple Standard logic apps at the same time.
In the Azure portal search box, enter logic apps, and select Logic apps.
On the Logic apps page, view only the Standard logic apps using the Plan filter.
Based on whether you're disabling or enabling your logic apps, view only the Enabled or Disabled logic apps using the Status filter.
In the checkbox column, select one or multiple logic apps.
- To stop the selected logic apps, select Disable/Stop.
- To restart the selected logic apps, select Enable/Start.
Confirm your selection.
To check whether your task succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).
You can restart a single Standard logic app at any time.
In the Azure portal, open your Standard logic app resource.
On the logic app menu, select Overview.
On the Overview page toolbar, select Restart.
To check whether your task succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).
Disabling a workflow affects all its workflow instances in the following ways:
Azure Logic Apps continues all in-progress and pending workflow runs until they finish. Based on the volume or backlog, this process might take time to complete.
Tip
To reduce costs resulting from resources and workflow instances that might otherwise take longer to scale down in nonproduction environments for load and performance testing, you can manually stop a workflow. This action cancels in-progress and pending workflow runs.
For this task, add the following settings to the host settings for your Standard logic app resource:
Important: Use following settings only in nonproduction environments. Follow each workflow ID with a colon (:), and separate workflow IDs with a semicolon (;):
"Jobs.SuspendedJobPartitionPrefixes": "<workflow-ID>:;<workflow-ID>:","Jobs.CleanupJobPartitionPrefixes": "<workflow-ID>:;<workflow-ID>:"For more information, see Edit host and app settings for Standard logic apps.
Azure Logic Apps doesn't create or run new workflow instances.
You can resubmit workflow runs while the workflow is disabled.
The workflow trigger doesn't fire while the logic app or workflow is disabled. However, the trigger state remembers the point where you disabled the workflow. When you restart the logic app or enable the workflow, the trigger fires for all unprocessed items since the last workflow run.
To stop the trigger from firing on all unprocessed items since the last workflow run, you must clear the trigger state.
To stop the trigger from firing the next time when the trigger condition is met, disable your workflow. You can disable or enable one or multiple Standard logic apps at the same time.
In the Azure portal, open your Standard logic app resource.
On the logic app menu, under Workflows, select Workflows.
In the checkbox column, select the workflow to disable or enable.
On the Workflows page toolbar, select Disable or Enable, based on the current activity state.
To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).
While a logic app is stopped or a workflow is disabled, the workflow trigger doesn't fire the next time that the trigger condition is met. However, the trigger state remembers the point at where you stopped the logic app or disabled the workflow. When you restart the logic app or re-enable the workflow, the trigger fires for all unprocessed items since the last workflow run.
To stop the trigger from firing on all unprocessed items since the last workflow run, you must clear the trigger state before you restart the logic app or re-enable the workflow.
In the Azure portal, open your Standard logic app workflow, and edit any part of the workflow trigger.
Save your changes. This step resets the trigger's current state.
Repeat for each existing workflow.
You can delete one or multiple Standard logic apps at the same time. A Standard logic app can have multiple workflows, so you can either delete the entire logic app or delete individual workflows.
Deleting a Standard logic app affects all its workflow instances in the following ways:
Azure Logic Apps immediately cancels any in-progress and pending workflow runs. However, the platform doesn't run cleanup tasks on the storage used by the logic app.
Azure Logic Apps doesn't create or run new workflow instances.
Although you can manually recover deleted Standard logic apps, using source control to manage your Standard logic apps makes recovery and redeployment much easier.
If you don't use source control, and you might have to later recover a deleted Standard logic app, make sure to save any custom settings that you need for recovery before you delete the logic app.
In the Azure portal, go to the Standard logic app.
On the logic app menu, under Settings, select Environment variables.
On the App settings tab, find, copy, and save any custom app settings and values that you need for later recovery.
On the logic app menu, under Settings, select Configuration.
On each settings tab, note any custom settings that you need for later recovery.
If you delete a logic app and its workflows, but you then recreate the same logic app and workflows, the recreated logic app and workflows don't have the same metadata as the deleted resources.
So, if you have another workflow that calls the deleted workflow, you must resave the caller workflow to refresh the metadata for the recreated workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an
Unauthorizederror. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.
In the Azure portal search box, enter logic apps, and select Logic apps.
On the Logic apps page, view only the Standard logic apps using the Plan filter.
In the checkbox column, select one or multiple logic apps to delete. On the toolbar, select Delete.
When the confirmation box appears, enter yes, and select Delete.
To check whether your task succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).
You can delete one or multiple Standard workflows at the same time. Deleting a Standard workflow affects its workflow instances in the following ways:
Azure Logic Apps immediately cancels any in-progress and pending workflow runs. The platform also performs cleanup tasks on the storage used by the workflow.
Azure Logic Apps doesn't create or run new workflow instances.
If you delete a workflow, but you then recreate the same workflow, the recreated workflow doesn't have the same metadata as the deleted workflow.
So, if you have another workflow that calls the deleted workflow, you must resave the caller workflow to refresh the metadata for the recreated workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an
Unauthorizederror. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.
In the Azure portal, open your Standard logic app resource.
On the logic app menu, under Workflows, select Workflows. In the checkbox column, select a single or multiple workflows to delete.
On the toolbar, select Delete.
To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).
The steps to recover a deleted Standard logic app vary based on whether you use source control and the hosting option for your logic app.
Before you try to recover a deleted logic app, review the following considerations:
The run history from the deleted logic app is unavailable in the recovered logic app.
If your workflow starts with the Request trigger, the callback URL for the recovered logic app differs from the URL for the deleted logic app.
If you use source control, you can recover a deleted Standard logic app resource, based on the hosting option:
| Hosting option | Prerequisites | Recovery steps |
|---|---|---|
| Workflow Service Plan | None | Redeploy your logic app. |
| App Service Environment V3 | Before you delete your app, download the Standard logic app from the Azure portal. For more information, see Download Standard logic app artifacts from portal. | Redeploy your logic app. |
To recover a deleted Standard logic app that uses the Workflow Service Plan hosting option and runs in single-tenant Azure Logic Apps, try the following steps:
In the Azure portal, confirm that the storage account used by your logic app still exists. If the storage account is deleted, you have to first recover the deleted storage account.
To identify the storage account name, open your logic app.
On the logic app menu, under Settings, select Environment variables.
On the Environment variables page, under App settings, find the app setting named AzureWebJobsStorage.
Go to the storage account. On the storage account menu, under Security + networking, select Access keys.
On the Access keys page, copy and save the primary connection string somewhere secure for later use in this guide.
The connection string uses the following format:
DefaultEndpointsProtocol=https;AccountName=<storage-account-name>;AccountKey=<access-key>;EndpointSuffix=core.windows.net
On the storage account menu, under Data storage, select File shares. Copy and save the file share name for later use in this guide.
Important
When you handle sensitive information, such as connection strings that include usernames, passwords, access keys, and so on, make sure that you use the most secure authentication flow available.
For example, Standard logic app workflows don't support secure data types, such as securestring
and secureobject, aren't supported. Microsoft recommends that you authenticate access to Azure
resources with a managed identity
when possible, and assign a role with the least necessary privilege.
If the managed identity capability is unavailable, secure your connection strings through other measures, such as Azure Key Vault, which you can use with app settings in your Standard logic app resource. You can then directly reference these secure strings.
Similar to ARM templates, where you can define environment variables at deployment time, you can define app settings in your logic app workflow definition. You can then capture dynamically generated infrastructure values, such as connection endpoints, storage strings, and so on. For more information, see Application types for the Microsoft identity platform.
In the Azure portal, create a new Standard logic app resource with the same hosting option and pricing tier. You can use either a new name or reuse the name from the deleted logic app.
Before you continue, disable the new logic app.
On the logic app menu, under Settings, select Environment variables. On the App settings tab, update the following values. Make sure to save your changes when you finish.
App setting Replacement value AzureWebJobsStorage Replace the existing value with the previously copied connection string from your storage account. WEBSITE_CONTENTAZUREFILECONNECTIONSTRING Replace the existing value with the previously copied connection string from your storage account. WEBSITE_CONTENTSHARE Replace the existing value with the previously copied file share name. On your logic app menu, under Workflows, select Connections.
Open each connection. On the connection menu, under Settings, select Access policies.
In the Action column, select Delete to delete the access policy for the deleted logic app.
On the Access policies toolbar, select Add so you can add a new access policy, and select your replacement logic app.
Return to your replacement logic app.
If you have custom settings to restore, on the logic app menu, under Settings, selects Environment variables or Configuration, based on the types of settings that you have.
When you're done, restart your logic app.
When you save changes to your Consumption logic app workflow, Azure saves the version before you made your changes, and your edited version becomes the current version. You can view these previous versions, select a previous version to promote over the current version, and edit the selected version before you finish the promotion process.
In the Azure portal, open your Consumption logic app.
On the logic app menu, under Development Tools, select Versions.
From the Version list, select the workflow version that you want.
To filter the list, in the Versions page search bar, enter the version ID, if you know the ID.
The History version page shows the selected version in read-only mode. You can change between the designer view and code view.
In the Azure portal, view the previous version that you want to promote.
On the History version toolbar, select Promote.
The workflow designer opens the selected workflow version.
Optionally make any edits that you want to the workflow.
You can change between Designer and Code view. You can also update the Parameters.
To save any updates and finish promotion, on the designer toolbar, select Save. To cancel your changes, select Discard.
When you view your logic app version history again, the promoted version now appears first in the list with a new identifier.