Head to head · Decision models · October 2026 research run

Microsoft-Decision-1 vs Microsoft-Decision-1.1

Microsoft-Decision-1.1 scores 44.8 (E) on agent readiness against Microsoft-Decision-1's 42.1 (E), and leads in 2 of 7 scored categories. Both do decision models. Microsoft-Decision-1 is cheaper for decision models, $0 against $0 per 1M tokens.

Best decision models for AI agents · All 263 decisions comparisons

Which one, for what

Microsoft-Decision-1 E

Best for Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.

Also in its favour

  • Cheaper for decision models, $0 against $0 per 1M tokens

Watch for

Public preview only. Microsoft's post gives no general availability date and states no licence for the hosted model

Microsoft-Decision-1.1 E

Best for Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.

Ahead on

  • Reliability, 50 against 40
  • Maintenance & community, 44 against 34

Also in its favour

  • Cheaper for decision models, $0 against $0 per 1M tokens

Watch for

No machine-readable contract or reference page with the request schema was found

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Microsoft-Decision-1.1 +10

Microsoft-Decision-1 40

The Azure status history page lists Foundry Models among its products, with post-incident reviews kept for five years, earning 20 of 20. It's a shared component, not a page for this model. In the 90 days from 12 August, re-read on 10 November 2026, the one review naming Foundry Models is 29 September 2026 in Sweden Central, 10:03 to 15:58 UTC, with intermittent request failures and latency. That is one region and a share of requests, so partial and minor, as the Azure OpenAI fine-tuning, Speech, Translator and Document Intelligence listings read it. The 30 September gateway review doesn't name Foundry Models, and nothing is posted after it (20 of 30, was 10). No rate limit, 429 guidance or SLA for this model was found (0, 0 and 0). The model is still in public preview per the Tech Community post, so there is no general availability award (0). Total 40.

Microsoft-Decision-1.1 50

Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The Azure status history page lists Foundry Models among its products, with post-incident reviews kept for five years, earning 20 of 20. It's a shared component, not a page for this model. In the 90 days from 12 August, re-read on 10 November 2026, the one review naming Foundry Models is 29 September 2026 in Sweden Central, 10:03 to 15:58 UTC, with intermittent request failures and latency. That is one region and a share of requests, so partial and minor, as the Azure OpenAI fine-tuning, Speech, Translator and Document Intelligence listings read it. The 30 September gateway review doesn't name Foundry Models, and nothing is posted after it (20 of 30, was 10). No rate limit, 429 guidance or SLA for this model was found (0, 0 and 0). The model is still in public preview per the Tech Community post, so there is no general availability award (0). Total 40. For 1.1: Foundry's model list marks Microsoft-Decision-1.1 generally available, and Microsoft calls it ready for enterprise production, so the GA line earns 10 where Decision-1 had 0 in preview. 40 + 10 = 50.

Maintenance & community Microsoft-Decision-1.1 +10

Microsoft-Decision-1 34

Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (30 + 0 + 0 + 10 + 0 = 40). The model was released on 9 October 2026, 32 days before this check, and no later dated change was found; the Command Line post was last modified on 10 October to add benchmarks (20 of 30, cause time). No deprecation policy or notice period for the model was found (0 of 12). No model or version has been removed, but OpenRouter says the weights are updated continually with no version names, per the 10 October check (4 of 8). No changelog (0 of 15). The one reader question under the Tech Community post, of 15 October, has no reply (0 of 10). OpenRouter's SDK lists the Decisions method in Python, TypeScript and Go as alpha, per the 10 October check; openrouter.ai isn't read in this run (10 of 15). No supported runtimes stated (0 of 10). 20 + 0 + 4 + 0 + 0 + 10 + 0 = 34.

Microsoft-Decision-1.1 44

Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (30 + 0 + 0 + 10 + 0 = 40). The model was released on 9 October 2026, 32 days before this check, and no later dated change was found; the Command Line post was last modified on 10 October to add benchmarks (20 of 30, cause time). No deprecation policy or notice period for the model was found (0 of 12). No model or version has been removed, but OpenRouter says the weights are updated continually with no version names, per the 10 October check (4 of 8). No changelog (0 of 15). The one reader question under the Tech Community post, of 15 October, has no reply (0 of 10). OpenRouter's SDK lists the Decisions method in Python, TypeScript and Go as alpha, per the 10 October check; openrouter.ai isn't read in this run (10 of 15). No supported runtimes stated (0 of 10). 20 + 0 + 4 + 0 + 0 + 10 + 0 = 34. For 1.1: released 17 November 2026, the day before this check, so recency earns 30 where Decision-1 had 20. 34 + 10 = 44.

Score by category

CategoryWeightMicrosoft-Decision-1Microsoft-Decision-1.1Edge
Reliability16%4050Microsoft-Decision-1.1 +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4343even
Agent ergonomics13%5050even
Security & auth14%5252even
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3444Microsoft-Decision-1.1 +10
Transparency & trust7%3634Microsoft-Decision-1 +2
Negative events≤1500
TotalE 42.1/100E 44.8/100

Facts side by side

FactMicrosoft-Decision-1Microsoft-Decision-1.1
KindModel APIModel API
VendorMicrosoftMicrosoft
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for decision modelsfreefree
x402nono
LicenceNot stated. The announcement and OpenRouter's model page name no licence, and no weights repository was found.Not stated. Microsoft's post and OpenRouter's page name no licence for the hosted model. It's built on Gemma 4 26B A4B, and no Microsoft weights were released.
Read-only variant documentednono
llms.txtnono
Last release2026-10-092026-11-17
Terms last updatedno document linkedno document linked
Privacy policy last updatednot read yetno date given
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Microsoft-Decision-1

Microsoft publishes $0.042 per million input tokens, with output free, and the model is callable through Microsoft Foundry and OpenRouter. It is in public preview. No licence, model-specific retention statement, rate limit or deprecation policy was found, and the Foundry route needs an Azure deployment and an Entra token. Latency and accuracy figures are Microsoft's claims.

Microsoft-Decision-1.1

A generally available decision model that returns a calibrated probability per option, now from images as well as text, at $0.042 per million input tokens with output free on Foundry and OpenRouter. No published schema, changelog, licence or deprecation policy was found.

Before you call either

Microsoft-Decision-1

  1. Use OpenRouter's Decisions method, not an OpenAI chat-completions SDK. OpenRouter says chat completions SDKs will not work with this model
  2. On Foundry, send the request to the deployment's /providers/microsoft/v1/systemone path with a Microsoft Entra token for https://cognitiveservices.azure.com/.default, not an API key
  3. Take the deployment name from the Foundry quickstart before the first call. Microsoft says to confirm the route and authentication header, and the pages reviewed do not give the name
  4. Keep each request within OpenRouter's 32,768-token context and send only fixed options, since the model is not intended for open-ended generation
  5. Measure latency and calibration on your own labelled cases before relying on Microsoft's latency and 'nine times out of 10' statements

Microsoft-Decision-1.1

  1. On Foundry, deploy Microsoft-Decision-1.1 in a Foundry resource and call it with a Microsoft Entra bearer token
  2. On OpenRouter, call microsoft/microsoft-decision-1.1 through the Decisions API, not chat completions
  3. Send fixed answer options and read the probabilities; it writes no explanation
  4. Set a confidence threshold and defer to a larger model below it

Questions

Which is better for AI agents, Microsoft-Decision-1 or Microsoft-Decision-1.1?

Microsoft-Decision-1.1 scores 44.8 (E) on agent readiness against Microsoft-Decision-1's 42.1 (E), and leads in 2 of 7 scored categories.

Which is cheaper for decision models, Microsoft-Decision-1 or Microsoft-Decision-1.1?

Microsoft-Decision-1, at free against free for Microsoft-Decision-1.1. These are the vendors' published prices for the job.

Do Microsoft-Decision-1 and Microsoft-Decision-1.1 need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Microsoft-Decision-1 and Microsoft-Decision-1.1 without installing anything?

No hosted endpoint is listed for Microsoft-Decision-1. No hosted endpoint is listed for Microsoft-Decision-1.1.

Other comparisons with Microsoft-Decision-1 or Microsoft-Decision-1.1

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.