A1 ratingsMicrosoftMicrosoft Foundry Agent Service

Microsoft Foundry Agent Service

Microsoft · platform · Any industry
B
BGrade
63Score
±1195% range
#199Rank of 1134
0%From fleets
FR-CAT-00076Catalog no.

The six pillars

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

Can you see what it costs?

Cloud billing export (Azure Cost Management Query API)
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 Cost Management Query API (meter-level usage)
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?

Admin API · Cost by project/resource via Cost Management; per-agent requires separate resources or tags.
57±27
Desk research 60 · 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?

Spend cap: Alerts only · Per-agent keys: Scoped · Audit log: Console only · Revoke: By API
70±27
Desk research 78 · 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 research71%Neutral starting point29%

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

Spend capAlerts only
Per-agent keysScoped
Audit logConsole only
RevokeBy API
SSONot known
PricesNot known

Same service as Azure AI Foundry Agent Service under the new name: per-agent Entra identities with RBAC, alert-only Azure budgets.

History

11-12 B 6311-13 B 6311-14 B 6311-15 B 6311-16 B 6311-17 B 6311-18 B 6311-19 B 63
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-24
1 earlier
[1] Correct
Usage API
Usage
Azure Cost Management Query API (meter-level usage) Declared
medium confidence
2026-10-24
1 earlier
[1] Correct
Cost per agent
Per agent
By project Declared
medium confidence
2026-10-24
1 earlier
[1] Correct
How an agent reports out
Reports out
Admin API Declared
medium confidence
2026-10-24
1 earlier
[1] Correct
Per-agent keys
Controls
Scoped Declared
medium confidence
2026-10-24
1 earlier
[1][2] Correct
Audit log
Controls
Console only Declared
medium confidence
2026-10-24
1 earlier
[1][2] Correct
Revoke access
Controls
By API Declared
medium confidence
2026-10-24
1 earlier
[1][2] Correct
Spend cap
Controls
Alerts only Verified 2026-10-26
2 earlier
[1][2][3] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-24
1 earlier
[1] Correct

Prices · Pay-as-you-go: model tokens plus tool charges (e.g. Grounding with Bing, search)

Notes · Re-checked 2026-10-24: priced by the models and tools each agent uses; hosted agents autoscale with zero idle cost; no per-agent fee stated; no spend controls on the product 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

Corrections

1 awaiting review. Accepted corrections are published in the corrections register with an FR-C number.

Run agents on Microsoft Foundry Agent Service?

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.