30 minTime to key
NoNo-human path
4Human gates
7/10Onboarding score
Card before first callEmail verificationMandatory 2FAPhone OTP
Fastest path to a key
- Create/sign in to a Microsoft account
- Phone OTPCreate an Azure free account: phone verification (SMS/call) + credit/debit card identity check (temporary ~$1 hold; virtual/prepaid cards rejected), accept agreement
- `az login` (browser, or `az login --use-device-code`)
- `az group create` then `az cognitiveservices account create --kind OpenAI` (or a Foundry/AIServices resource) in a supported region
- `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
- `az cognitiveservices account keys list` to get key1/key2 + endpoint (or use keyless Entra ID via DefaultAzureCredential, which Microsoft recommends)
- 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
- https://learn.microsoft.com/api/mcp
- https://raw.githubusercontent.com/microsoft/mcp/main/servers/Azure.Mcp.Server/README.md
- https://learn.microsoft.com/en-us/azure/developer/azure-mcp-server/get-started
- https://learn.microsoft.com/en-us/azure/developer/azure-mcp-server/how-to/deploy-remote-mcp-server-microsoft-foundry
- https://azure.microsoft.com/free/free-account-faq
- https://learn.microsoft.com/cli/azure/cognitiveservices/account/keys
- https://devops.com/azure-devops-remote-mcp-server-lands-in-microsoft-foundry-giving-ai-agents-direct-access-to-your-devops-data/
31Readiness score / 100
L1 Agent-readableBeats 36% of 1,846 companies
Access20/20
Context3/20
Interfaces8/32
Onboarding0/19
Trust0/9
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
- +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.
Add the badge to your README
[](https://agentsready.dev/c/azure.microsoft.com)