Manage logic app workflows in the Azure portal

1. In the Azure portal, find and open your logic app resource.

2. From the logic app menu, under Workflows, select Connections.

3. 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

1. In the Azure portal, find and open your logic app resource.

2. From the logic app menu, under Development tools, select API Connections.

3. On the API Connections page, select a specific connection instance, which shows more information about that connection. To view the underlying connection resource definition, select JSON View.

You can stop or start a single or multiple Standard logic app. You can also restart a single logic app without first stopping. Your single-tenant based logic app can include multiple workflows, so you can either stop the entire logic app or disable only Standard workflows.

Considerations for stopping Standard logic apps

Stopping a Standard logic app at the resource level affects workflow instances in the following ways:

• Single-tenant Azure Logic Apps cancels all in-progress and pending runs immediately.

• Single-tenant Azure Logic Apps doesn't create or run new workflow instances.

• Triggers won't fire the next time that their conditions are met. However, trigger states remember the points where the logic app was stopped. So, if you restart the logic app, the triggers fire for all unprocessed items since the last run.

  To stop each workflow from triggering on unprocessed items since the last run, clear the trigger state before you restart the logic app by following these steps:

  1. In the Azure portal, open your logic app.
  2. On the logic app menu, under Workflows, select Workflows.
  3. Open a workflow, and edit any part of that workflow's trigger.
  4. Save your changes. This step resets the trigger's current state.
  5. Repeat for each workflow.
  6. When you're done, restart your Standard logic app.

Disable or enable Standard logic apps

You can stop or start multiple Standard logic apps at the same time, but you can't restart multiple Standard logic apps without stopping them first.

1. In the Azure portal search box, enter logic apps, and select Logic apps.

2. On the Logic apps page, view only the Standard logic apps using the Plan filter.

3. View only the Enabled or Disabled logic apps using the Status filter, which you can add if necessary.

4. In the checkbox column, select the logic apps that you want to stop or start.

   • To stop the selected running logic apps, select Disable/Stop. Confirm your selection.
   • To start the selected stopped logic apps, select Enable/Start.

5. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).

Restart a Standard logic app without stopping

You can restart a Standard logic app anytime.

1. In the Azure portal, open your Standard logic app resource.

2. On the logic app menu, select Overview.

3. On the Overview page toolbar, select Restart.

4. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).

Stop or start Standard workflows

To stop the trigger from firing the next time when the trigger condition is met, disable your workflow.

Considerations for disabling a Standard workflow

Disabling a workflow affects workflow instances in the following ways:

• Single-tenant 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 instances. For this task, you have to add the following settings to your Standard logic app resource's host settings.

  Important: Make sure to use the 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.

• Single-tenant Azure Logic Apps doesn't create or run new workflow instances.

• The trigger won't fire the next time that its conditions are met. However, the trigger state remembers the point at which the workflow was disabled. So, if you re-enable the workflow, the trigger fires for all the unprocessed items since the last run.

  To stop the trigger from firing on unprocessed items since the last run, clear the trigger's state before you reactivate the workflow:

  1. In the workflow, edit any part of the workflow's trigger.
  2. Save your changes. This step resets your trigger's current state.
  3. Reactivate your workflow.

• When a workflow is disabled, you can still resubmit runs.

Disable or enable Standard workflows

1. In the Azure portal, open your Standard logic app resource.

2. On the logic app menu, under Workflows, select Workflows.

3. In the checkbox column, select the workflow to disable or enable.

4. On the Workflows pane toolbar, select Disable or Enable.

5. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).

You can stop or start a single or multiple Consumption logic apps at the same time. A Consumption logic app has only one workflow, so stopping or starting the logic app resource affects all associated workflow instances.

Considerations for stopping Consumption logic apps

Stopping a Consumption logic app affects workflow instances in the following ways:

• Azure Logic Apps continues all in-progress and pending runs until they finish. Based on the volume or backlog, this process might take time to complete.

• Azure Logic Apps doesn't create or run new workflow instances.

• The trigger won't fire the next time that its conditions are met. However, the trigger state remembers the point at which the logic app was stopped. So, if you reactivate the logic app, the trigger fires for all the unprocessed items since the last run.

  To stop the trigger from triggering on unprocessed items since the last run, clear the trigger's state before you reactivate the logic app:

  1. In the logic app, edit any part of the workflow's trigger.
  2. Save your changes. This step resets your trigger's current state.
  3. Reactivate your logic app.

• When a workflow is disabled, you can still resubmit runs.

Disable or enable Consumption logic apps

1. In the Azure portal search box, enter logic apps, and select Logic apps.

2. On the Logic apps page, view only the Consumption logic apps using the Plan filter.

3. View only the Enabled or Disabled logic apps using the Status filter, which you can add if necessary.

4. In the checkbox column, select a single or multiple logic apps that you want to stop or start.

   • To stop the selected running logic apps, select Disable/Stop. Confirm your selection.
   • To start the selected stopped logic apps, select Enable/Start.

5. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).

   Tip

   If the correct status doesn't appear, refresh the page.

You can delete a single or multiple Standard logic apps at the same time. Your single-tenant based logic app can include multiple workflows, so you can either delete the entire logic app or delete only workflows.

Delete Standard logic apps

Deleting a Standard logic app resource cancels in-progress and pending runs immediately, but doesn't run cleanup tasks on the storage used by the app.

1. In the Azure portal search box, enter logic apps, and select Logic apps.

2. On the Logic apps page, view only the Standard logic apps using the Plan filter.

3. In the checkbox column, select a single or multiple logic apps to delete. On the toolbar, select Delete.

4. When the confirmation box appears, enter yes, and select Delete.

5. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).

Delete Standard workflows

Deleting a Standard workflow affects workflow instances in the following ways:

• Azure Logic Apps cancels in-progress and pending runs immediately, but runs 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 and then recreate the same workflow, the recreated workflow won't have the same metadata as the deleted workflow. To refresh the metadata, you have to resave any workflow that called the deleted workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an Unauthorized error. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.

1. In the Azure portal, open your Standard logic app resource.

2. On the logic app menu, under Workflows, select Workflows. In the checkbox column, select a single or multiple workflows to delete.

3. On the toolbar, select Delete.

4. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).

Recover deleted Standard logic apps

If you use source control, you can seamlessly redeploy a deleted Standard logic app resource to single-tenant Azure Logic Apps. If you're not using source control, try the following steps to recover your deleted logic app:

Before you try to recover your deleted logic app, review the following considerations:

• You can recover only deleted Standard logic app resources that use the Workflow Standard hosting plan.

• 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.

1. Confirm that your logic app's storage account still exists.

2. On the storage account menu, under Security + networking, select Access keys.

3. On the Access keys page, copy the account's primary connection string, and save for later use, for example:

   DefaultEndpointsProtocol=https;AccountName=<storage-account-name>;AccountKey=<access-key>;EndpointSuffix=core.chinacloudapi.cn

4. On the storage account menu, under Data storage, select File shares, copy the name for the file share associated with your logic app, and save for later use.

5. Create a new Standard logic app resource using the same hosting plan and pricing tier. You can either use a new name or reuse the name from the deleted logic app.

6. Before you continue, stop the logic app. From the logic app menu, select Overview. On the Overview page toolbar, select Stop.

7. From the logic app menu, under Settings, select Configuration.

8. On the Configuration page, update the following application setting values, and remember to save your changes when finished.

   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 string from your storage account.
   WEBSITE_CONTENTSHARE	Replace the existing value with the previously copied file share name.

   Important

   When you have sensitive information, such as connection strings that include usernames and passwords, make sure to use the most secure authentication flow available. For example, in Standard logic app workflows, 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 that has the least privilege necessary.

   If this capability is unavailable, make sure to secure connection strings through other measures, such as Azure Key Vault, which you can use with app settings. You can then directly reference secure strings, such as connection strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define app settings within your logic app workflow definition. You can then capture dynamically generated infrastructure values, such as connection endpoints, storage strings, and more. For more information, see Application types for the Microsoft identity platform.

9. On your logic app menu, under Workflows, select Connections.

10. Open each connection and under Settings, select Access policies.

11. Delete the access policy for the deleted logic app, and then add a new access policy for the replacement logic app.

12. Return to the logic app's Configuration page, and add any custom settings that existed on the deleted logic app.

13. When you're done, restart your logic app.

You can delete a single or multiple Consumption logic apps at the same time.

Deleting a Consumption logic app affects workflow instances in the following ways:

• Azure Logic Apps makes a best effort to cancel any in-progress and pending runs.

  Even with a large volume or backlog, most runs are canceled before they finish or start. However, the cancellation process might take time to complete. Meanwhile, some runs might get picked up for execution while the service works through the cancellation process.

• Azure Logic Apps doesn't create or run new workflow instances.

• If you delete a workflow and then recreate the same workflow, the recreated workflow won't have the same metadata as the deleted workflow. You have to resave any workflow that called the deleted workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an Unauthorized error. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.

Delete Consumption logic apps

1. In the Azure portal search box, enter logic apps, and select Logic apps.

2. On the Logic apps page, view only the Consumption logic apps using the Plan filter.

3. In the checkbox column, select a single or multiple logic apps to delete. On the toolbar, select Delete.

4. When the confirmation box appears, enter yes, and select Delete.

5. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the Notifications list (bell icon).