Microsoft: the 360 agent-readiness check

Microsoft scores 62 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 1: OAuth. A login an agent can use, on a domain that points nowhere else.

On 9 November 2026 the public site at microsoft.com scored 62 of 100 on Ora's agent-readiness scan, a C, in Ora's Identity & Auth category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Microsoft offers strong developer resource discoverability and SDK packages, but lacks published OpenAPI specifications for agent integration.

The score

What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. 3 checks in this group do not apply to this site and are left out.

In the directory, Microsoft has an open MCP server with tools listed at https://learn.microsoft.com/api/mcp, 3 tools listed, no authentication; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents. One check in this group does not apply to this site and is left out.

What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. 2 checks in this group do not apply to this site and are left out.

Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.

Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies.

The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Microsoft, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.

• OpenAPI spec published: fail, 0 of 7, about 4.3 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.9 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• JSON error responses: fail, 0 of 4, about 3.1 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
• MCP Apps support: fail, 0 of 4, about 3.1 points to gain. Ora saw: No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render.
• Public API with reachable endpoints: partial, 3 of 7, about 3.1 points to gain. Ora saw: API described in documentation at https://developer.microsoft.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7.

Our read

Microsoft's corporate domain is read here as the identity and authentication provider it is, and on that reading the act layer is mostly elsewhere. developer.microsoft.com describes the APIs with no machine-verifiable surface, there is no OpenAPI specification on this domain, no CLI was found, and the MCP credit comes from @playwright/mcp on npm rather than a live endpoint; the OAuth endpoint at login.microsoft.com is the one surface that counts fully. SDKs are in npm, PyPI and rubygems. The reading side is weaker than the company's size suggests: no llms.txt at either location, a JSON-LD block with no identity type, and a home page that is 2.8 percent text, though it ranks first for its cloud platform and the door is open. One check, WebMCP, could read only 60 of 61 script bundles. The developer surfaces live on learn.microsoft.com and graph.microsoft.com; from microsoft.com an agent finds the login and little else.

Test your own surfaces

The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

npx ax@0.10 audit https://example.com --min-score 70

All 360 checks, one company a day. Corrections to the corrections page.