Is azure.microsoft.com agent ready?
azure.microsoft.com is not yet agent ready: it scores 34/100 (grade D) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Agent Protocols (17), Structured Data (22).
Changed since last check
−6 points since the previous check (2026-09-16)
Regressed: Reachable as Google-Agent
Changed: Token efficiency (HTML-to-text ratio) (partial → fail)
Category scores
Technical
88
Agent Auth
0
Agent Discovery
0
Agent Protocols
17
Content Quality
65
Structured Data
22
Bot Accessibility
67
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✗XML sitemap existsfail
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ✓Heading hierarchypass
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✗Token efficiency (HTML-to-text ratio)fail
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✗Structured formsfail
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✗Reachable as Google-Agentfail
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Score history
- 34/100 · rubric v3.0
- 40/100 · rubric v3.0
- 46/100 · rubric v3.0
- 45/100 · rubric v2.0
- 45/100 · rubric v2.0
- 44/100 · rubric v2.0
- 44/100 · rubric v2.0
- 43/100 · rubric v2.0