Microsoft 365
Microsoft 365 is Microsoft's productivity and collaboration suite, including Word, Excel, PowerPoint, Outlook, Teams, OneDrive, SharePoint, and OneNote, along with identity, security, and device management services. Developers access Microsoft 365 data and intelligence programmatically through Microsoft Graph, a unified REST API that exposes users, mail, calendar, files, Teams messages, sites, devices, and more across the Microsoft cloud.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Microsoft 365 the way a machine reads it — 17 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Microsoft 365 scores 34.0/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Microsoft 365
Each block below is one kind of artifact we hold for Microsoft 365. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Microsoft Graph API
Unified REST API providing a single endpoint to access data and intelligence across Microsoft 365, Microsoft Entra ID, Windows, and Enterprise Mobility + Security. Supports OAut...
Microsoft Graph Beta API
Beta endpoint of the Microsoft Graph API offering preview features and resources before they are promoted to v1.0, including additional insights, reporting, and management capab...
Microsoft 365 Calendar API
The Calendar API from Microsoft 365 — 1 operation(s) for calendar.
Microsoft 365 Files API
The Files API from Microsoft 365 — 1 operation(s) for files.
Microsoft 365 Groups API
The Groups API from Microsoft 365 — 3 operation(s) for groups.
Microsoft 365 Mail API
The Mail API from Microsoft 365 — 1 operation(s) for mail.
Microsoft 365 Me API
The Me API from Microsoft 365 — 3 operation(s) for me.
Microsoft 365 Teams API
The Teams API from Microsoft 365 — 2 operation(s) for teams.
Microsoft 365 Users API
The Users API from Microsoft 365 — 2 operation(s) for users.
Scroll within the panel for all 9 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Microsoft 365 (Microsoft Graph API)
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Microsoft 365 GraphQL Schema
This conceptual GraphQL schema represents the Microsoft 365 productivity suite APIs as exposed through Microsoft Graph, the unified REST API endpoint at `https://graph.microsoft...
GRAPHQLSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Microsoft 365 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/microsoft-365 · machine-readable index on apis.io