Skip to content

From canvas to run: a better Logic Apps Automation experience

Building a workflow is only the beginning. A few weeks later, someone needs to add an approval, change a condition, or understand why an order took an unexpected path. Those changes should be as approachable as creating the workflow in the first place.


During the preview, you’ve told us where that experience could be simpler. Sometimes the problem was seeing the shape of a large workflow. Sometimes it was finding an individual property from a Parse JSON action. We’ve taken a closer look at those moments across Logic Apps Automation: from finding a starting point and configuring an agent to testing a draft and investigating a run.


In this post



  • Find a starting point: Navigate apps and connections, or begin with a template.

  • Build and change workflows: Follow the redesigned canvas, configure agents and inputs, and reuse steps.

  • Try changes before publishing: Prepare draft settings, use test data, and run supported drafts.

  • Understand what happened: Inspect runs and action details in Monitoring, then look for patterns in Analytics.


The examples below come from different workflows.


Find your way around an app


The first step isn’t always a blank canvas. You might be looking for a workflow someone else built, setting up a connection, or finding a pattern to start from.


Navigation and search help you move between environments, apps, and workflows. Workflow lists can be sorted, and the creation experience brings templates and a blank workflow together. If you have the right permissions, you can also create and edit supported connections from the app’s Connections page, before opening a workflow. For supported connections, the portal can show what’s still missing after you reload.


We’ve also reduced unnecessary work behind some common lookups, including template setup and automatic workflow naming. It’s one of several changes intended to make the portal feel more responsive as you move between tasks.


Start from a template and make it your own


The public template gallery lets you explore workflows before you sign in. Find a starting point, then choose an environment, app, and workflow name to create a draft. You can inspect the steps, connect your accounts, and make the workflow your own before you run or publish it.


Browse the gallery before choosing a workflow to make your own.

You can also turn a successful run into a template. Review the workflow, sample data, and metadata, then download it for someone else to import. Remove any sensitive information before sharing; generating a template doesn’t publish it to the gallery.


An easier designer experience


The designer brings the steps, agents, and data in your workflow together. Here’s how the changes help you see the flow, make an edit, and try it out.


A redesigned canvas that makes workflows easier to follow


Consider an order-routing workflow: an order arrives, its details are parsed, and a condition sends it down an approval or rejection path. You should be able to understand that flow without opening every step.


The redesigned canvas gives triggers, actions, conditions, loops, and agents a more consistent visual language. Clearer icons, borders, and backgrounds help distinguish the steps in both light and dark themes.


Branches are easier to follow too:



  • A condition shows labeled True and False paths, with populated paths inside their own frames.

  • A Switch shows a labeled path for each case. Populated case frames show the case name and the value it matches.

  • Populated branches can be collapsed, so you can focus on one part of the workflow and expand the rest when needed.


In our example, each response sits inside its own branch frame. You can see which response belongs to which outcome without tracing a line across the canvas.


In the order-routing example, each response has a clearly labeled path.

Loops keep their repeating actions together, so it’s clear which steps run on each pass.


Choose a horizontal or vertical layout to suit the workflow; the designer remembers your orientation preference for that workflow. Canvas search helps you find a step in a larger flow. And when you move to Monitoring and back during the same session, the designer restores your canvas position.


Behind the scenes, the canvas does less repeated rendering and layout work as you pan, select, and move steps. The goal is to keep a growing workflow comfortable to work with, not just easier to look at.


Agents and their tools, in one view


An agent rarely works alone. In an invoice workflow, it might look up an order, retrieve vendor details, and send a notification before the workflow decides what to do next.


The redesigned agent node brings the agent and its tools together on the canvas, alongside the rest of the workflow. You can see which tools belong to it, then select the agent or a tool to configure it without losing sight of the surrounding flow.


The selected model can appear on the agent card too. Available choices come from your app’s model catalog, so they can vary between apps.


An invoice-validation agent appears alongside its model and tools.

Choose a Microsoft-managed model


For a Workflow or Managed agent, a Microsoft-managed model can take care of the model deployment and connection for you. When the option is available to your app, select Microsoft-managed and choose a supported model in the agent configuration.


Choose an available Microsoft-managed model in the agent’s settings.

You still configure the agent’s instructions and tools, and a Managed agent may need harness and sandbox settings. You can use a supported provider connection instead when you need one. GitHub Copilot connections have their own sign-in flow; they’re separate from Microsoft-managed models.


Change the workflow without rebuilding it


Suppose the order process needs an extra check before returning an approval. Add it from the connection between existing steps, including inside a branch.


Placement matters: a step added inside a branch belongs to that path; a step added after the paths join belongs to the shared flow. If you drag a connection, visual cues show where it can go.


Select a step to copy, paste, or duplicate it within the same workflow. When you rename a step, supported downstream action references are updated too, so you don’t have to repair each of those references by hand.


Reuse a selected step within the same workflow.

For larger changes, use Shift-click or a selection box to work with multiple items:



  • Copy, cut, paste, duplicate, or delete supported selections within the workflow.

  • Group eligible sequences into a Condition, Switch, For each, or Until.

  • Duplicate a Switch case from the canvas when you need a similar path.


The available commands depend on your selection; not every set of steps can be grouped.


Select multiple steps to see the commands available for that selection.

That makes it easier to reshape the work you already have instead of recreating each step.


Configure inputs while keeping the workflow in view


Select a step and its configuration opens beside the canvas. You can change its inputs while checking which branch you’re in and where each value comes from.


Related settings stay together, with required fields brought forward within those groups. Search the optional-parameter picker to find and show the inputs you need. When a value comes from an earlier step, dynamic content lets you select it from a panel you can move out of the way. In supported inputs, a token or expression is inserted at the cursor or replaces selected text.


The controls reflect the input you’re editing. Supported fields offer a condition builder, a resource picker, or rich-text editing. Some dropdowns can bind directly to an agent parameter, and long agent instructions can be expanded for editing. When configuring a workflow call, you can select an eligible callable workflow instead of entering its target by hand.


App parameters have their own Form and JSON views. Use whichever is more comfortable to manage their values, then select available parameter tokens when configuring workflow inputs. These parameters are separate from the draft app settings described below.


Find individual Parse JSON properties


You told us it was difficult to find individual Parse JSON properties for later actions and agent tools. In supported downstream steps, those properties appear as dynamic content, including in nested tool configurations, subject to the workflow’s usual scope rules.


In the order example, you can select orderId, amount, or region individually instead of working with the entire parsed object.


Choose individual parsed order properties while configuring the response.

For eligible structured inputs, switch between a JSON editor and text. You can also inspect the workflow definition in a JSON view alongside the canvas.


Work with data using JavaScript expressions


Sometimes you need to do more than select a value. You might want a default when a property is missing, or a different result depending on the order. Supported inputs accept JavaScript expressions inside ${…}; the expression handler evaluates them using the workflow context.


For example, after parsing an order, this expression uses its region when available and falls back to unknown when it isn’t:


${body(‘ParseOrder’)?.[‘region’] ?? ‘unknown’}

The expressions picker helps you find available workflow functions, and supported fields can preview an expression using available data. Run the draft to check its behavior in the full workflow.


Find the right action


When you’re adding a step, an incomplete result list shouldn’t leave you wondering whether an action is missing or the search failed.


Searching for a connector or action brings relevant matches forward, including built-in actions. Results already on screen keep their place as more arrive. If a source can’t be loaded, the picker can explain the problem and offer a retry.


Search for an action without leaving the canvas.

Use action search to add a step; use canvas search to find one that’s already there.


Use test data in your draft


Some templates come with sample inputs and mock action outputs, called test data in the designer. You can also configure available action test data in a regular draft. It stays with the draft as you refine the workflow.


Turn on Run with test data to use the configured sample outputs in place of those actions’ live calls. A beaker on the canvas identifies steps using test data; open a step to review or edit its sample output.


In this invoice workflow, Create Ticket is configured to return test data. Other actions may still run live.

Only steps configured to use test data are simulated. Other actions can still call live services. Test data substitutes action outputs; it doesn’t create a simulated connection or validate credentials. Check the remaining actions and connections before you run.


Test a draft before publishing


Your draft gives you room to change a workflow without replacing its published version. For supported request-triggered and other manual-style workflows, you can provide sample input and run the draft before publishing.


Choose an autosave interval that suits you, or save manually. Saving a draft doesn’t publish it. If the published definition can’t be loaded but a valid draft exists, the designer can open that draft with a warning so you can continue working.


Prepare app settings alongside your draft


Changing a workflow can also mean changing a connection or an environment variable. Draft app settings give you a place to prepare those changes alongside the workflow.


Draft app settings are enabled by default and can’t be disabled. Draft environment-variable edits and new draft connection credentials use the draft slot. Publishing promotes the draft settings, so review their effect on your app before publishing.


Prepare draft environment variables separately from the settings used in production.

Try both paths before you publish


For the order-routing example, try one input that should be approved and another that should be rejected. Inspect the results, adjust the draft, and try again. The published workflow stays as it is until you publish the draft.


Provide sample trigger input for a draft run.

A draft test is not an isolated sandbox. Actions without test data can call real services and cause external side effects, even though you’re working in a draft. Check your actions and connections before each test.


Before publishing, the portal checks for missing required connection configuration and tells you what needs attention. Your draft is kept so you can fix the connection and try again. This checks configuration; it doesn’t guarantee that credentials are valid or that a downstream service will work at run time.


See what happened with Monitoring


When an order doesn’t take the path you expected, you need more than a failed or successful badge. You need to understand what happened.


Open Monitoring to see your workflow’s Runs, with status, time, and duration. Select a run for its Execution log, then select an operation to inspect its available inputs, outputs, and properties. You can expand action details for a closer look.


In this example run, a calculation step is selected to show its output.

You can also inspect a run on the designer canvas. When run data is available, a condition highlights the branch that was taken. For a condition inside a loop, select an iteration to see the decision on that particular pass.


For a For each loop, the selected iteration stays in sync across the execution log, the details panel, and the canvas. You can inspect the status and duration of the steps in that pass instead of relying only on the overall loop result. If an action has recorded retry attempts, Retry history shows the individual attempts and their available timing and response details.


Not every investigation begins with a run. Trigger history, next to Runs, helps you inspect trigger evaluations and follow a resulting run when one is available. Monitoring refreshes active-run status; a step that hasn’t reported yet can remain pending rather than appearing skipped. If some agent or tool details can’t be loaded, a warning appears by the affected execution instead of treating missing monitoring data as a workflow failure.


For supported managed agents, the Files view groups available input and output files. You can preview supported text, image, and PDF files or download them without working through a large JSON response.


For our order example, a practical place to start is:



  1. Check the incoming order data.

  2. Review the parsed values available to the condition.

  3. Follow the branch taken.

  4. Inspect the response step’s inputs and outputs where available.


When you need to recover, Monitoring offers retry for eligible runs and, where the runtime permits it and you have permission, Submit from this action for an eligible action in a completed published run. A whole-run retry uses saved trigger data with the current workflow definition; action resubmission uses the source run’s workflow version. Both can repeat external side effects, so check the impact before resubmitting.


Look beyond a single run


The app’s Analytics view helps you step back from one execution and look for patterns in run volume, failures, and workflow health. Where usage was recorded, agent charts can show token usage and tool calls for recent runs. The detailed agent breakdown uses a limited recent-run window; it’s not a complete usage history or a cost estimate.


Keep the feedback coming


Whether you’re starting from a template or revisiting a workflow that’s been running for months, we want the next change to feel manageable. Try the experience with a workflow you know and tell us where you still get stuck. The details you share—like the difficulty finding Parse JSON properties—help us decide what to improve next.


Explore the experience available to your app in the Logic Apps Automation portal, and visit the documentation, including the designer guide. Availability can vary by app, region, provider, and model catalog.

Microsoft Tech Community originally posted this article on 18 November 2026 at 4:16 AM.

Leave a Reply