An AI-powered document workflow extracts data, routes files into categories, updates a database, and flags items for human review.
Microsoft has put Decision actions in Azure Logic Apps Automation into public preview. They let a workflow ask an AI model one narrow question and get back a structured answer that later steps can act on. The Azure Updates listing carries a timestamp of November 17, 2026. The populated update record couldn't be retrieved, so the details below come from Microsoft's same-day Logic Apps announcement and its documentation.

An AI-powered document workflow extracts data, routes files into categories, updates a database, and flags items for human review. What Microsoft announced​

Microsoft announced the feature on November 17, 2026, in an Azure Integration Services blog post covering Logic Apps news from Ignite 2026. That post, per the source material, says Decision actions use Microsoft-Decision-1 for focused judgments such as classifying requests, routing tickets and assessing urgency. It names three action types, Yes/No, Choice and Score, which return structured results workflows can act on directly.

Microsoft's own framing is that these are for cases where an agent isn't needed. Workflows handle predictable tasks, Decision actions handle focused judgments, and agents handle more complex reasoning.

Preview status​

On Azure Updates, "In preview" means the feature is available to Azure customers for non-production use and testing. It is not a production launch. Microsoft Learn also marks Logic Apps Automation itself as a preview capability under the Supplemental Terms of Use for Microsoft Azure Previews.

Logic Apps Automation is available in public preview at auto.azure.com, according to InfoQ's coverage of the Build 2026 launch. That is a separate SKU from Logic Apps Standard and Consumption.

What the underlying model does​

Microsoft's Foundry documentation describes the Decision model as different from a chat model. It doesn't write free-form text or a rationale. It returns a typed, numerical decision about text, JSON or images.

  • Yes/No-style gates answer a true/false condition, such as whether a document contains a prompt injection.
  • Choice picks one option from a fixed list and gives a probability for every option.
  • Score places an item on an ordered scale. The score is a probability-weighted average of the level indexes, so it can fall between levels.

The Foundry documentation says to use a low top probability on a Choice result as a signal to escalate to a person or another model. It also says to prefer scores for relative ordering and thresholds, not as absolute, calibrated ratings. One caveat: that documentation covers the Foundry model (version 1.1 on the page captured here). The announcement doesn't say the Logic Apps designer exposes every option the same way.

Where it fits​

Microsoft's Learn overview says Logic Apps Automation suits variable, decision-heavy processes. It points stable, repeatable processes to Logic Apps Standard or Consumption. The two share the same runtime, connectors and management plane, so the Learn overview calls them siblings.

A sensible pattern, which is my own illustration and not a Microsoft sample, is to let a Decision action classify or score an incoming item and then use ordinary branches, approvals and connectors to handle each result. A support intake flow could route among defined teams. An operations flow could assign severity and send uncertain cases to review.

Cautions before you build on it​

Microsoft's Foundry documentation lists these known limitations:

  • The model may reflect biases from its base model and training data, so its scores shouldn't be the sole basis for decisions about individuals.
  • Scores can change with how questions and options are worded or ordered.
  • It gives no explanation for a decision.
  • Used as a safety filter, it can miss subtle harmful content or flag benign content.

Its best-practice advice is to validate on representative labeled data and to set thresholds based on the cost of false positives and false negatives. It also suggests including an abstention option such as "cannot tell." For decisions about people, such as credit, employment, housing, healthcare or legal matters, it calls for meaningful human review.

Practical checklist for a pilot:

  1. Pick one bounded decision and give it a business owner.
  2. Collect labeled examples from your real workload.
  3. Measure errors and latency, not just correct routes.
  4. Set a confidence threshold and send low-confidence cases to a human.
  5. Keep normal authorization on any action that changes state.

What's still unknown​

The available sources don't establish regions for the Decision actions, pricing, input limits, data-handling details, designer configuration or a general-availability date. Reviewers of the earlier Logic Apps Automation preview have also asked Microsoft for a published model support matrix and clearer VNet and private endpoint guidance. Until those details appear, treat this as something to test, not something to put in front of production workloads.

For admins, the useful takeaway is that Microsoft is splitting automation into three tiers. Deterministic workflows handle the routine steps, cheap structured decisions handle the judgment calls, and full agents handle open-ended reasoning. Whether the middle tier proves reliable enough to run without a human in the loop is what a pilot should find out.

 

References

  1. (In preview) Public Preview: Decision actions in Azure Logic Apps Automation Azure Updates 2026-11-17T20:00:32Z
  2. Microsoft Launches Logic Apps Automation at Build 2026 - InfoQ infoq.com
  3. Overview - Azure Logic Apps Automation | Microsoft Learn learn.microsoft.com