AgentsReady
Verified deep dive · India & cloud

Microsoft Azure

Run the agent liveReport a change
30 minTime to key
NoNo-human path
4Human gates
7/10Onboarding score
Card before first callEmail verificationMandatory 2FAPhone OTP

Fastest path to a key

  1. Create/sign in to a Microsoft account
  2. Phone OTP
    Create an Azure free account: phone verification (SMS/call) + credit/debit card identity check (temporary ~$1 hold; virtual/prepaid cards rejected), accept agreement
  3. `az login` (browser, or `az login --use-device-code`)
  4. `az group create` then `az cognitiveservices account create --kind OpenAI` (or a Foundry/AIServices resource) in a supported region
  5. `az cognitiveservices account deployment create` to deploy a model (e.g. a GPT model) with SKU/capacity. Quota may need a request for some models
  6. `az cognitiveservices account keys list` to get key1/key2 + endpoint (or use keyless Entra ID via DefaultAzureCredential, which Microsoft recommends)
  7. Working API key

Biggest gap

No llms.txt, a heavy signup gate (card + phone), and a 'deploy a model before you can call it' step that agents often miss

Worth copying

Keyless Entra ID auth is the recommended default, and the Azure MCP ships as a first-party Claude Code plugin and IDE extensions

Sources (7) · checked 2026-10-11
31Readiness score / 100
L1 Agent-readableBeats 36% of 1,846 companies
Access20/20
Context3/20
Interfaces8/32
Onboarding0/19
Trust0/9

Biggest gains

  1. +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
  2. +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
  3. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • FAILllms.txt exists8
  • FAILllms-full.txt exists3
  • FAILDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • FAILRemote MCP server for the product12
  • FAILDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • FAILOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • FAILFree tier or test mode3
  • FAILAgent manifests4
  • FAILsecurity.txt2
  • FAILPublic status page3

Your fix pack: 14 changes, up to +69 points

Each change is ready to paste, filled in for azure.microsoft.com, with a command to check it worked. Or hand the whole list to your coding agent.

A remote MCP server lets Claude, ChatGPT and Cursor act on your product in one click, with no glue code.

Where: https://mcp.azure.microsoft.com/mcp (Streamable HTTP)
// npm i @modelcontextprotocol/sdk zod  — minimal remote MCP server (Streamable HTTP, stateless)
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";
import express from "express";
import { z } from "zod";

const app = express();
app.use(express.json());

app.post("/mcp", async (req, res) => {
  const server = new McpServer({ name: "azure.microsoft.com", version: "1.0.0" });
  // One tool per core job. Clear verbs, typed inputs, small outputs.
  server.tool("create_<thing>", "Create a <thing> for the signed-in user.", { name: z.string() },
    async ({ name }) => {
      const key = req.headers.authorization?.replace("Bearer ", ""); // scoped API key or OAuth token
      const r = await fetch("https://azure.microsoft.com/v1/<things>", { method: "POST", headers: { Authorization: `Bearer ${key}` }, body: JSON.stringify({ name }) });
      return { content: [{ type: "text", text: await r.text() }] };
    });
  const transport = new StreamableHTTPServerTransport({ sessionIdGenerator: undefined });
  res.on("close", () => transport.close());
  await server.connect(transport);
  await transport.handleRequest(req, res, req.body);
});
app.listen(3000);
Check it worked:curl -s -X POST https://mcp.azure.microsoft.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' -i | head -15

Add the badge to your README

AgentsReady badge for azure.microsoft.com
[![AgentsReady](https://agentsready.dev/badge/azure.microsoft.com)](https://agentsready.dev/c/azure.microsoft.com)