Blog Post

Azure Integration Services Blog
7 MIN READ

Tune your Logic Apps Standard runtime from the portal

WSilveira's avatar
WSilveira
Icon for Microsoft rankMicrosoft
Nov 17, 2026

You've hit a limit. An HTTP action gives up at exactly 3 minutes 45 seconds. A For each loop works through 20 items at a time when you expected more. A trigger stops starting new runs at 100 and queues the rest. You know there's a setting for it. You don't know which one, where it lives, or what it's set to right now.

Until now, the answer lived in host.json. To change a value in Azure, you opened Advanced Tools, went into Kudu, stopped your logic app, hand-edited JSON with a key you copied from the docs, saved, and restarted. Nothing on screen told you the default, or whether someone had already changed it.

That's the gap the new Workflow runtime settings tab closes.

What is the new configuration experience

Workflow runtime settings is a new tab on the Configuration page of every Logic Apps Standard app in the Azure portal. It sits next to General settings, Health check, and Path mappings, and it's generally available today.

The tab turns the host and app settings we document for Standard into a form. You get 11 collapsible areas, each with labeled fields that show the value in effect. Every field has an info tooltip with a plain-language description, the exact setting key, and the default. Change one or more values, select Apply, and the portal writes the right setting to host.json or app settings for you, then restarts the host so the new value is live immediately.

No Kudu. No hand-edited JSON. No guessing the key.

Why it is important

Standard gives you a single-tenant runtime, and with it the ability to tune throughput, limits, and retries for your workload. But a setting you can't find is a setting you don't use.

The first problem was discoverability. The settings that govern scaling, throttling, and concurrency lived in a long reference table in the docs, with nothing in the portal pointing to them. The second was context: a key like Runtime.FlowTriggerDispatchingJob.MessageProcessingConcurrencyLimit doesn't tell you which behavior it changes or what a sensible value looks like. The third was the baseline. If you didn't know the default, you couldn't tell whether a value had been tuned, or how to put it back.

The new tab deals with all three, and it doesn't add new settings to learn. It's a distillation of the settings already published in our docs, presented where you manage the app.

Before and after

TaskBeforeNow
Find the right settingSearch the host settings reference in the docsExpand the matching area on the Workflow runtime settings tab
See the current valueOpen host.json in Kudu; a missing key means the default appliesThe field shows the value in effect
Know the defaultLook it up in the reference tableHover the info icon next to the field
Change a valueStop the app, edit host.json in Kudu, save, restartEdit the field and select Apply
Back out an editEdit the JSON againSelect Discard before applying, or enter the default shown in the tooltip

Walkthrough

You will find the new configuration settings under Configuration> Workflow runtime settings tab 

Follow the steps below to start exploring it:

  1. In the Azure portal, open your Standard logic app.
  2. On the resource menu, under Settings, select Configuration.
  3. Select the Workflow runtime settings tab. The 11 configuration areas appear, collapsed.
  4. Expand an area, for example Built-in operations, to see its settings grouped by operation type.
  5. Hover the info icon next to any field to read what it does, its setting key, and its default.
  6. Change the values you need, then select Apply. Select Discard to drop unsaved edits, or Refresh to reload the current values.

You can explore each configuration using the tooltip button. It explains the setting, notes that the default values and also the any range or possible values. It will also provide you the configuration entry this value is adding to your host.json. For example for the HTTP Request Timeout, it gives you Runtime.Backend.HttpOperation.RequestTimeout as the key.

 

The configuration areas

AreaWhat it controlsExamples (default)
Built-in operationsRetries, timeouts, and request size for built-in HTTP, HTTP Webhook, and Azure Functions operationsHTTP Request Timeout (00:03:45), HTTP Default Retry Count (4)
Connectors - ManagedAuthentication audience, timeouts, retries, and webhook intervals for managed (Azure-hosted) connectorsConnector Request Timeout (00:02:00), Connector Webhook Wake-Up Interval (01:00:00)
Connectors - Service ProviderSettings for the built-in service provider connectors your workflows useService Bus Message Sender Pool Size Per Processor Count (64), Key Vault Max Secrets To Return (25)
Content & message limitsChunking, pagination, input and output size, and when content moves from table storage to blob storageMaximum content size per input or output (104,857,600 bytes), Maximum page count (1,000)
Job orchestration & throughputJob dispatchers per processor core and job queue partitioningWorkers per processor count (192)
Loops & variablesFor each and Until limits, For each parallelism, and variable sizeFor each degree of parallelism (20), Until limit for stateful workflows (5,000)
Retry policyUpper and lower bounds for retry policies on workflow operationsMaximum retry count (90), Minimum retry interval (00:00:05)
Run lifecycle & historyAction and function timeouts, run duration, and history cleanupAction job execution timeout (00:10:00), Flow run timeout (90 days)
ScalingRuntime scale monitoringRuntime scale monitoring (On or Off)
StorageRetries and timeouts for blob, table, and queue requests from the runtimeBlob server timeout (00:00:30), Table and queue server timeout (00:00:16)
TriggersFunction-based trigger listeners and drain mode, recurrence-based trigger state, and trigger concurrencyMaximum Run Concurrency (100), Maximum Waiting Runs (200)

Feature highlights

Settings for the connectors your app uses

The Connectors - Service Provider area doesn't list every built-in connector in Logic Apps. It shows settings for the ones your workflows use. In the walkthrough app, that's Azure Tables, Key Vault, Service Bus, and Service Bus Peek Lock, followed by a short block of switches that apply to all service providers, such as Validate action and trigger operation IDs.

That changes what you're looking at. Instead of scanning SFTP or SQL settings in an app that never calls them, you see the settings that can affect your app: for example, Azure Tables Max Entities To Return (255) or Key Vault Max Secrets To Return (25).

Managed connectors get their own area, with the authentication audience, request timeout (00:02:00), retry count and intervals, and webhook wake-up interval.

Scaling, throttling, and concurrency, out of the config file

When a load test shows a bottleneck, these are the settings you reach for. They used to be the hardest to find. Now each one has a field, a default, and a description.

  • Job orchestration & throughput: 192 dispatcher workers per processor core for stateful runs and 192 for stateless runs, 4 partitions in the job definitions table, and 1 job triggers queue.
  • Triggers: Maximum Run Concurrency (100), Maximum Waiting Runs (200), and Message Processing Concurrency Limit (1). For function-based triggers, you also get the list of triggers with concurrency enabled (Service Bus and Event Hubs in the walkthrough app), plus drain mode and dynamic listener timings.
  • Loops & variables: For each degree of parallelism (20). Set it to 1 to run iterations one after another.
  • Scaling: an On or Off switch for runtime scale monitoring.

 

Defaults where you can see them

Every field shows the value in effect, and every tooltip shows the default and the setting key. That's three answers on one screen: what the app runs with, what it would run with if nobody had touched it, and the exact key to look for in your project.

The key matters if you deploy from source control. host.json travels with your deployment, so a value you change in the portal can be overwritten the next time your pipeline deploys. Once you've found the right value in the portal, copy the key from the tooltip into your project's host.json, under extensions.workflow.Settings:

{
    "version": "2.0",
    "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
        "version": "[1.*, 2.0.0)"
    },
    "extensions": {
        "workflow": {
            "Settings": {
                "Runtime.Trigger.MaximumWaitingRuns": "100"
            }
        }
    }
}

Those values will update the correct file locations (host.json and appsettings). Use the portal to find and test the correct values in the files and apply on your source controled files to keep it.

One value, every workflow

Before you change anything, keep scope in mind. These are app-level settings. A value you apply here becomes the runtime configuration for every workflow in the logic app, not only the one you're debugging.

Trigger concurrency is the clearest example. Set Maximum Run Concurrency to 1, and each qualifying trigger in the app can start one run at a time, with further runs waiting in line up to the Maximum Waiting Runs limit (200 by default). These trigger concurrency settings apply to workflows that start with a recurrence-based trigger for built-in, service provider-based connectors. If only one workflow needs to process one run at a time, configure concurrency on that workflow's trigger instead.

Selecting Apply restarts the host. Treat a change the way you'd treat any restart: try it in a nonproduction environment first, and apply it in production when a brief restart won't hurt.

Feedback

This tab started from a simple observation: the runtime settings were hard to find and easy to get wrong. It's our first pass at putting them where you work, and I want to know how close we got.

Which settings do you change most often? Which ones are missing? Which descriptions still leave you guessing? Open an issue on the Logic Apps UX GitHub repo and tell me. I read them, and they shape what we build next.

For the full reference behind every field, see Edit app and host settings for Standard logic apps.

Updated Nov 17, 2026
Version 1.0
No CommentsBe the first to comment