Azure Logic App Workflow API Filtering Options

Question

Azure Logic App Workflow API Filtering Options

cloudteam 60

What are the filtering options available for the Azure Logic App workflow list API?

The API endpoint in question is:
https://management.azure.com/subscriptions/{{subscription id}}/resourceGroups/{{resource group}}/providers/Microsoft.Web/sites/{{standard logic app name}}/workflows?api-version=2024-04-01

Specifically, the following information is sought:

Is it possible to filter workflows based on their status (enabled/disabled) and health state (healthy, unhealthy, not specified, unknown)? If so, how can this be achieved?
When can 'not specified' and 'unknown' statuses be expected in a workflow?
Is filtering based on creation time feasible? If yes, what is the method?
Is it possible to limit the number of records returned (e.g., to only the top 100)?

Efforts have been made to implement the last two filters, but they were unsuccessful. If feasible, examples of how to achieve this would be appreciated.

Khadeer Ali 5,990 Reputation points Microsoft External Staff Moderator

2025-04-29T18:35:52.62+00:00
@cloudteam ,

Thank you for reaching out.

Filtering by Workflow Status (Enabled/Disabled)

You can filter workflows by their status using the $filter query parameter. For example, to filter workflows that are enabled, you can use the following API call:

https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroup}}/providers/Microsoft.Web/sites/{{logicAppName}}/workflows?api-version=2024-04-01&$filter=state eq 'Enabled'&$top=100

Filtering by Health State (Healthy, Unhealthy, NotSpecified, Unknown)

Direct filtering by health state is not supported via API parameters. However, you can monitor health states using Azure Monitor or Log Analytics with diagnostic logs enabled. Filtering by health would need to be done through KQL queries in Log Analytics. For example, you can use the following KQL query to filter by health state:

AzureDiagnostics | where ResourceType == "WORKFLOW" | where HealthState == "Healthy" or HealthState == "Unhealthy"

Understanding 'NotSpecified' and 'Unknown' Health States

These health states typically appear when health diagnostics are not configured or the system lacks sufficient telemetry to determine a health status.

Filtering by Creation Time

Filtering by creation time is not natively supported via API parameters. You need to retrieve the workflows first and then filter them client-side using the createdTime field from the API response.

Limiting Results (Pagination)

You can limit the number of results returned by using the $top parameter. For example, to limit the results to 100, you can use:

$top=100

Sample API Call

Here is a sample API call that combines filtering by state and limiting results:

https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroup}}/providers/Microsoft.Web/sites/{{logicAppName}}/workflows?api-version=2024-04-01&$filter=state eq 'Enabled'&$top=100

https://learn.microsoft.com/en-us/rest/api/logic/workflows/list-by-subscription?view=rest-logic-2016-06-01&utm_source=chatgpt.com&tabs=HTTP

View workflow health and performance metrics - Azure Logic Apps
cloudteam 60 Reputation points

2025-04-29T22:27:20.9433333+00:00
Hi,

Thanks for the quick response.

I have 3 workflows in a Standard Logic App:

2 workflows are enabled

1 workflow is disabled

I used the following API request with a filter to retrieve only the enabled workflows, limiting the result to 1 item:

https://management.azure.com/subscriptions/{{subscription id}}/resourceGroups/{{resource group}}/providers/Microsoft.Web/sites/{{standard logic app name}}/workflows?api-version=2024-04-01&$filter=state eq 'Enabled'&$top=1

Expected Result: Only 1 enabled workflow should be returned in the first response, along with a pagination link.

Actual Result: The response includes all 3 workflows, ignoring the filter condition

Could you please provide clarity on why this is happening?

Thanks!
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-05-01T10:43:36.4733333+00:00
@cloudteam ,Thanks for posting your question in Microsoft Q&A, apologize for any inconvenience caused on this.Based on the shared information, I understand that you want to list the workflows which are present in the standard logic app.

This Azure Management Rest API Workflows - List By Resource Group is for consumption logic apps not applicable for standard.

Whenever, you provision a standard logic app & workflows it will be deployed inside an app service plan you need to use the Workflow Azure Management Rest API's under the app service rather than using Rest API under Logic Apps to query the standard logic app workflow.

Here is the list of supported Rest API available to query run histories, actions in standard logic app workflows.

Unfortunately, there is no Rest API available to directly list the workflows within standard logic apps.

However, after conducting further investigation using the f12 browser trace, we found the following REST API that can be used to list workflows, and you need to pass bearer token for Authorization header. This API might not support filter option. If we found any API that lists standard logic app with filter option, we will update the documentation.

YAMLCopy

https://management.azure.com/subscriptions/{{SubscriptionId}}/resourcegroups/{{ResourceGroup}}/providers/Microsoft.Web/sites/{{LogicAppName}}/hostruntime/runtime/webhooks/workflow/api/management/workflows?api-version=2018-11-01

Here is the sample output for your reference:

Note: Make sure your service principal or user account from which you are generating the access token is assigned either with Website Contributor or Contributor RBAC role.
Khadeer Ali 5,990 Reputation points Microsoft External Staff Moderator

2025-05-02T14:41:37.5333333+00:00

@cloudteam ,

Just checking in to see if the response provided by Praveen Kumar Gudipudi addressed your query.
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-05-02T19:55:41.27+00:00

Hello @cloudteam ,

Could you please check my previous response and let us know with an update.

1 answer

Your answer

cloudteam 60 Reputation points

2025-04-29T22:27:20.9433333+00:00

Hi,

Thanks for the quick response.

I have 3 workflows in a Standard Logic App:

2 workflows are enabled

1 workflow is disabled

I used the following API request with a filter to retrieve only the enabled workflows, limiting the result to 1 item:

https://management.azure.com/subscriptions/{{subscription id}}/resourceGroups/{{resource group}}/providers/Microsoft.Web/sites/{{standard logic app name}}/workflows?api-version=2024-04-01&$filter=state eq 'Enabled'&$top=1

Expected Result: Only 1 enabled workflow should be returned in the first response, along with a pagination link.

Actual Result: The response includes all 3 workflows, ignoring the filter condition

Could you please provide clarity on why this is happening?

Thanks!
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-05-01T10:43:36.4733333+00:00

@cloudteam ,Thanks for posting your question in Microsoft Q&A, apologize for any inconvenience caused on this.Based on the shared information, I understand that you want to list the workflows which are present in the standard logic app.

This Azure Management Rest API Workflows - List By Resource Group is for consumption logic apps not applicable for standard.

Whenever, you provision a standard logic app & workflows it will be deployed inside an app service plan you need to use the Workflow Azure Management Rest API's under the app service rather than using Rest API under Logic Apps to query the standard logic app workflow.

Here is the list of supported Rest API available to query run histories, actions in standard logic app workflows.

Unfortunately, there is no Rest API available to directly list the workflows within standard logic apps.

However, after conducting further investigation using the f12 browser trace, we found the following REST API that can be used to list workflows, and you need to pass bearer token for Authorization header. This API might not support filter option. If we found any API that lists standard logic app with filter option, we will update the documentation.

YAMLCopy

https://management.azure.com/subscriptions/{{SubscriptionId}}/resourcegroups/{{ResourceGroup}}/providers/Microsoft.Web/sites/{{LogicAppName}}/hostruntime/runtime/webhooks/workflow/api/management/workflows?api-version=2018-11-01

Here is the sample output for your reference:

Note: Make sure your service principal or user account from which you are generating the access token is assigned either with Website Contributor or Contributor RBAC role.
Khadeer Ali 5,990 Reputation points Microsoft External Staff Moderator

2025-05-02T14:41:37.5333333+00:00

@cloudteam ,

Just checking in to see if the response provided by Praveen Kumar Gudipudi addressed your query.
Praveen Kumar Gudipudi 1,805 Reputation points Microsoft External Staff Moderator

2025-05-02T19:55:41.27+00:00

Hello @cloudteam ,

Could you please check my previous response and let us know with an update.

Answer 1

@cloudteam ,

There’s been some confusion around the use of the $filter query in the Azure Logic Apps REST APIs. Based on our review of Microsoft’s documentation and direct testing, here’s what we found:

The API endpoint to list workflows at the subscription level (GET /subscriptions/{subscriptionId}/providers/Microsoft.Logic/workflows) does support basic $filter operations, but only on high-level properties like name, location, and tags. This is confirmed in Microsoft’s official REST API documentation.

However, for endpoints like /workflowRuns or /triggerHistories, which are often used to fetch execution data (e.g., filtering by run status or time range), $filter is either not supported or not fully functional — even under Logic App Standard or ISE (Premium). These endpoints typically return all runs, and any filtering has to be handled client-side.

If you need to filter runs by status, startTime, or other execution metadata, the recommended approach is to enable diagnostics to Log Analytics and query using Kusto (KQL).

Share via

Azure Logic App Workflow API Filtering Options

1 answer

Your answer