Microsoft Office
A collection of APIs for Microsoft Office applications and services, providing programmatic access to Word, Excel, PowerPoint, Outlook, OneDrive, and Teams through Microsoft Graph and Office JavaScript APIs.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Microsoft Office the way a machine reads it — 28 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 Office scores 55.8/100 (developing), with a separate agent-readiness read of 71/100 (agent native). 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 Office
Each block below is one kind of artifact we hold for Microsoft Office. 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.
Word API
API for interacting with Microsoft Word documents, including reading, writing, and formatting content.
Excel API
API for working with Excel workbooks, worksheets, ranges, charts, and tables.
PowerPoint API
API for creating and manipulating PowerPoint presentations, slides, and content.
Outlook Mail API
API for accessing and managing email, calendar, contacts, and tasks in Outlook.
OneDrive API
API for accessing files and folders stored in OneDrive and SharePoint.
Teams API
API for integrating with Microsoft Teams, including messaging, channels, and collaboration features.
Microsoft Office Drive API
The Drive API from Microsoft Office — 4 operation(s) for drive.
Microsoft Office Mail API
The Mail API from Microsoft Office — 4 operation(s) for mail.
Microsoft Office Teams API
The Teams API from Microsoft Office — 4 operation(s) for teams.
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 Graph API (Office 365 subset)
OPEN COLLECTIONArazzo Workflows 8
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Microsoft Office Discover and Download a OneDrive File
Resolve the user's drive, browse the root, inspect an item, and download its content.
ARAZZOMicrosoft Office Announce a New OneDrive File in a Teams Channel
Find a file in the drive root, confirm its metadata, and post it to a Teams channel.
ARAZZOMicrosoft Office Update a OneDrive File and Verify the Write
Read a file's metadata, back up its current bytes, upload new content, and read the item back.
ARAZZOMicrosoft Office Inventory Mail Folders and Export Messages
Enumerate mail folders, page a filtered message list, and read one message in full.
ARAZZOMicrosoft Office Escalate an Inbox Message to a Teams Channel
Match an inbox message against a filter, read it in full, and raise it as a Teams channel alert.
ARAZZOMicrosoft Office Triage Inbox Messages and Respond
List filtered inbox messages, read the top match in full, and send a reply.
ARAZZOMicrosoft Office Build a Teams Channel Message Digest
Walk the user's joined teams, enumerate a team's channels, and pull a channel's recent messages.
ARAZZOMicrosoft Office Provision a Teams Channel and Announce It
Resolve a joined team, check for an existing channel, create it when missing, and post a kickoff message.
ARAZZOScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
microsoft-office-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Microsoft Office Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Microsoft Office Finops
FINOPSSecurity 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.
Microsoft Office Trust Center
SOC 1, SOC 2, SOC 3, ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, ISO/IEC 27701, ISO/IEC 22301, FedRAMP High, HIPAA / HITECH, PCI DSS, GDPR, CSA STAR, FIPS 140-2
SECURITYScopes 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 Office — 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 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 14
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 14 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/microsoft-office · machine-readable index on apis.io