A1 ratingsAzure OpenAI / AI Foundry

Azure OpenAI / AI Foundry

· platform · Any industry Provisional
B
BGrade
58Score
±1795% range
≈#295Rank of 1134
0%From fleets
FR-CAT-01278Catalog no.
Provisional: the range is wide because some facts are thin or not yet known. It narrows as research and fleets fill in.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Cloud billing export (Cost Management Exports API (incl. FOCUS) and Cost Details APIs; Foundry portal cost analysis per deployment)
64±27
Desk research 70 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.

Can you see how much it's used?

Azure Monitor metrics: Input/Output/Total Tokens per deployment; Log Analytics RequestResponse logs
86±27
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

By project
64±27
Desk research 70 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.

Can an agent on it report out?

50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.

Can you control spend and access?

50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).

Does it work on small plans?

Small plans don't get the data
14±27
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.

Where the evidence comes from

Independent fleets0%Desk research46%Neutral starting point54%

Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.

Controls on record

Being researched now. Spend caps, per-agent keys, audit logs, revoking and SSO land here as the research writes them.

History

11-12 B 5811-13 B 5811-14 B 5811-15 B 5811-16 B 5811-17 B 5811-18 B 5811-19 B 58
Rated since 2026-10-02. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
Cloud billing export Declared
medium confidence
2026-10-02 [1][2][3] Correct
Usage API
Usage
Azure Monitor metrics: Input/Output/Total Tokens per deployment; Log Analytics RequestResponse logs Declared
medium confidence
2026-10-02 [1][2][3] Correct
Cost per agent
Per agent
By project Declared
medium confidence
2026-10-02 [1][2][3] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-02 [1][2][3] Correct

Prices · Per-token pay-as-you-go or Provisioned Throughput (PTU) by model (not captured).

Notes · Attribute per agent via a separate deployment/resource or tag. FOCUS export support is confirmed by a Microsoft Q&A answer rather than the main reference page.

Scored with the rubric for Platforms and APIs (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Run agents on Azure OpenAI / AI Foundry?

Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.