Microsoft Applications
A collection of APIs for Microsoft's suite of applications and services.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Microsoft Applications the way a machine reads it — 12 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 Applications scores 27.7/100 (emerging), with a separate agent-readiness read of 24/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 Applications
Each block below is one kind of artifact we hold for Microsoft Applications. 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 API endpoint for accessing Microsoft 365, Windows 10, and Enterprise Mobility + Security services.
Office 365 API
APIs for Office 365 services including Outlook, OneDrive, and SharePoint.
Microsoft Teams API
Build apps and bots for Microsoft Teams collaboration platform.
OneDrive API
Access and manage files stored in OneDrive and SharePoint.
Outlook Mail API
Access and manage email, calendar, and contacts in Outlook.
SharePoint REST API
Programmatic access to SharePoint sites, lists, and content.
Power BI REST API
Embed Power BI content and manage Power BI resources.
Microsoft To Do API
Manage tasks and to-do lists via Microsoft To Do.
Microsoft Planner API
Create and manage plans, tasks, and team collaboration.
Scroll within the panel for all 9 ·
Pricing 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 Applications 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.
← All providers · Data indexed from github.com/api-evangelist/microsoft-applications · machine-readable index on apis.io