Microsoft Copilot
Microsoft Copilot is an AI-powered assistant that helps users with productivity tasks, content generation, and information retrieval across Microsoft 365 applications and services.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Microsoft Copilot the way a machine reads it — 146 machine-readable artifacts across 7 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 Copilot scores 68.5/100 (strong), with a separate agent-readiness read of 55/100 (agent ready). 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.
How we profile Microsoft Copilot
Each block below is one kind of artifact we hold for Microsoft Copilot. 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 7
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 365 Copilot Connectors API
API for building custom connectors that bring external data into Microsoft Graph to enhance Microsoft 365 Copilot experiences including search and retrieval augmented generation.
Microsoft Copilot Studio API
APIs for building, publishing, and integrating custom agents and copilots using Microsoft Copilot Studio, including Direct Line API for connecting web and custom applications.
Microsoft Copilot Change Notifications API
Subscribe to change notifications for Copilot interactions across Microsoft 365.
Microsoft Copilot Chat API
Programmatically start and continue conversations with Microsoft 365 Copilot using enterprise search and web search grounding. Preview API.
Microsoft Copilot Interaction Export API
Export and archive user interactions with Copilot across Microsoft 365 applications for compliance and auditing.
Microsoft Copilot Retrieval API
Retrieve relevant text chunks from SharePoint, OneDrive, and Copilot connectors content for Retrieval Augmented Generation (RAG) scenarios.
Microsoft Copilot Search API
Perform hybrid search (semantic and lexical) across OneDrive for work or school content using natural language queries. Preview API.
Scroll within the panel for all 7 ·
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 Copilot Microsoft 365 Copilot APIs
OPEN COLLECTIONPricing 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 Copilot 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 Copilot Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Retrieval API
Retrieve relevant enterprise content from Microsoft 365 using AI-powered retrieval augmented generation with permissions and sensitivity label awareness.
Search API
Perform semantic search across Microsoft 365 content including SharePoint, OneDrive, and Exchange with AI-enhanced ranking.
Chat API
Programmatically start and continue conversations with Microsoft 365 Copilot grounded in enterprise and web search data.
Interaction Export
Export and audit Copilot interaction history across the organization for compliance and governance purposes.
Change Notifications
Subscribe to real-time notifications for Copilot interactions and events across Microsoft 365.
Copilot Studio
Low-code platform for building custom agents, copilots, and conversational AI experiences.
Connectors
Bring external data into Microsoft Graph to enhance Copilot search and retrieval capabilities.
Extensibility
Extend Copilot with custom plugins, agents, and API integrations using declarative or code-first approaches.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Microsoft Copilot Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Microsoft Copilot API Rules
SPECTRALMicrosoft Copilot API Rules
SPECTRALJSON Schema 52
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AiInteractionAttachment
JSON SCHEMAAiInteractionCollectionResponse
JSON SCHEMAAiInteractionContext
JSON SCHEMAAiInteractionLink
JSON SCHEMAAiInteractionMention
JSON SCHEMAAiInteraction
JSON SCHEMAAiInteraction
JSON SCHEMAAiInteractionAttachment
JSON SCHEMAAiInteractionCollectionResponse
JSON SCHEMAAiInteractionContext
JSON SCHEMAAiInteractionLink
JSON SCHEMAAiInteractionMention
JSON SCHEMAChatConversationRequest
JSON SCHEMAChatConversationResponse
JSON SCHEMAChatMessageRequest
JSON SCHEMAChatMessageResponse
JSON SCHEMAChatMessage
JSON SCHEMAChatConversationRequest
JSON SCHEMAChatConversationResponse
JSON SCHEMAChatMessage
JSON SCHEMAChatMessageRequest
JSON SCHEMAChatMessageResponse
JSON SCHEMACopilotSearchDataSourcesConfiguration
JSON SCHEMACopilotSearchDataSourcesConfiguration
JSON SCHEMADataSourceConfiguration
JSON SCHEMADataSourceConfiguration
JSON SCHEMAIdentitySet
JSON SCHEMAIdentitySet
JSON SCHEMAMicrosoft 365 Copilot Interaction
JSON SCHEMAItemBody
JSON SCHEMAItemBody
JSON SCHEMAODataError
JSON SCHEMAODataError
JSON SCHEMARetrievalExtract
JSON SCHEMARetrievalHit
JSON SCHEMARetrievalRequest
JSON SCHEMARetrievalResponse
JSON SCHEMARetrievalExtract
JSON SCHEMARetrievalHit
JSON SCHEMARetrievalRequest
JSON SCHEMARetrievalResponse
JSON SCHEMASearchHit
JSON SCHEMASearchRequest
JSON SCHEMASearchResponse
JSON SCHEMASearchHit
JSON SCHEMASearchRequest
JSON SCHEMASearchResponse
JSON SCHEMASensitivityLabel
JSON SCHEMASensitivityLabel
JSON SCHEMASubscriptionRequest
JSON SCHEMASubscription
JSON SCHEMASubscriptionRequest
JSON SCHEMAScroll within the panel for all 52 ·
JSON Structure 27
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Microsoft Copilot Ai Interaction Attachment Structure
JSON STRUCTUREMicrosoft Copilot Ai Interaction Context Structure
JSON STRUCTUREMicrosoft Copilot Ai Interaction Link Structure
JSON STRUCTUREMicrosoft Copilot Ai Interaction Mention Structure
JSON STRUCTUREMicrosoft Copilot Ai Interaction Structure
JSON STRUCTUREMicrosoft Copilot Chat Conversation Request Structure
JSON STRUCTUREMicrosoft Copilot Chat Conversation Response Structure
JSON STRUCTUREMicrosoft Copilot Chat Message Request Structure
JSON STRUCTUREMicrosoft Copilot Chat Message Response Structure
JSON STRUCTUREMicrosoft Copilot Chat Message Structure
JSON STRUCTUREMicrosoft Copilot Data Source Configuration Structure
JSON STRUCTUREMicrosoft Copilot Identity Set Structure
JSON STRUCTUREMicrosoft Copilot Item Body Structure
JSON STRUCTUREMicrosoft Copilot O Data Error Structure
JSON STRUCTUREMicrosoft Copilot Retrieval Extract Structure
JSON STRUCTUREMicrosoft Copilot Retrieval Hit Structure
JSON STRUCTUREMicrosoft Copilot Retrieval Request Structure
JSON STRUCTUREMicrosoft Copilot Retrieval Response Structure
JSON STRUCTUREMicrosoft Copilot Search Hit Structure
JSON STRUCTUREMicrosoft Copilot Search Request Structure
JSON STRUCTUREMicrosoft Copilot Search Response Structure
JSON STRUCTUREMicrosoft Copilot Sensitivity Label Structure
JSON STRUCTUREMicrosoft Copilot Structure
JSON STRUCTUREMicrosoft Copilot Subscription Request Structure
JSON STRUCTUREMicrosoft Copilot Subscription Structure
JSON STRUCTUREScroll within the panel for all 27 ·
Examples 32
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 32 ·
Security Posture 3
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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Enterprise Knowledge Retrieval
Build applications that retrieve relevant enterprise content from Microsoft 365 while respecting permissions and compliance controls.
AI-Assisted Productivity
Integrate Copilot capabilities into line-of-business applications for document summarization, drafting, and data analysis.
Custom Agent Development
Create domain-specific AI agents using Copilot Studio that automate workflows and answer questions from custom data sources.
Compliance and Governance
Monitor and audit Copilot usage across the organization with interaction history export and change notifications.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Microsoft 365
Deep integration with Word, Excel, PowerPoint, Outlook, Teams, and other Microsoft 365 applications.
Microsoft Graph
Access organizational data through the Microsoft Graph API for retrieval, search, and chat capabilities.
Azure Active Directory
Enterprise authentication and authorization using Azure AD with OAuth 2.0 and OIDC.
Power Platform
Connect Copilot with Power Automate, Power Apps, and Power BI for end-to-end workflow automation.
Resources
Every other property we hold for Microsoft Copilot — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
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-copilot · machine-readable index on apis.io