Microsoft Learn
By Microsoft. How it meets the 23 requirements of MCP Authorization.
- Supported
- 0
- Unsupported
- 0
- Unknown, recorded
- 0
- Not observed yet
- 23
- Endpoint
https://learn.microsoft.com/api/mcp- Transport
- Streamable HTTP
- Access
- Public Anyone can connect; where an account is needed, anyone can create one by self-service sign-up. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · Publicly available at no charge.
- Auth
- No authentication The listed endpoint accepts requests without any credential. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · No authentication is required to access the server.
- Why it is listed
- Added by the atlas maintainer from the vendor's own documentation. Source
- Homepage
- https://learn.microsoft.com
Against MCP Authorization 2026-07-28current
- Unknown 23
Passive scanno OAuth to check · Why
Older revisions of the matrix: 2025-11-25
MCP server features 13
| Feature | Level | Status | Observed | Evidence |
|---|---|---|---|---|
| Protected Resource Metadata served | MUST | Unknown no observation | no observation yet | |
| PRM lists an authorization server | MUST | Unknown no observation | no observation yet | |
| PRM lists scopes_supported | MAY | Unknown no observation | no observation yet | |
| PRM reachable at a well-known URI | MUST | Unknown no observation | no observation yet | |
| resource_metadata in the 401 challenge | MUST | Unknown no observation | no observation yet | |
| 403 insufficient_scope for step-up | SHOULD | Unknown no observation | no observation yet | |
| Scope in the WWW-Authenticate challenge | SHOULD | Unknown no observation | no observation yet | |
| No offline_access in advertised scopes | SHOULD | Unknown no observation | no observation yet | |
| 401 for missing or invalid tokens | MUST | Unknown no observation | no observation yet | |
| Audience validation | MUST | Unknown no observation | no observation yet | |
| Bearer token only in the Authorization header | MUST | Unknown no observation | no observation yet | |
| No token passthrough to upstream APIs | MUST | Unknown no observation | no observation yet | |
| Per-client consent on proxy servers | MUST | Unknown no observation | no observation yet |
Authorization server features 10
| Feature | Level | Status | Observed | Evidence |
|---|---|---|---|---|
| Metadata issuer matches the discovery URL | MUST | Unknown no observation | no observation yet | |
| Authorization server metadata discoverable | MUST | Unknown no observation | no observation yet | |
| Client ID Metadata Documents supported | SHOULD | Unknown no observation | no observation yet | |
| Dynamic Client Registration offered | MAY | Unknown no observation | no observation yet | |
| Documented pre-registration path | SHOULD | Unknown no observation | no observation yet | |
| Issuer identifier in authorization responses | SHOULD | Unknown no observation | no observation yet | |
| PKCE with S256 advertised | MUST | Unknown no observation | no observation yet | |
| Refresh token rotation for public clients | MUST | Unknown no observation | no observation yet | |
| Resource indicators honoured | MUST | Unknown no observation | no observation yet | |
| All endpoints served over HTTPS | MUST | Unknown no observation | no observation yet |
This server's ledger
No status change on recordEvery cell of this server still shows the status of its first observation.
What the scanner asked
Auth class no authentication: there is no OAuth authorization to check.
letsauth-scanner/0.4.0 · reproduce with pnpm scan microsoft-learn · scan JSON · data file · how the scanner works