Microsoft Office 365
A collection of APIs provided by Microsoft Office 365 for productivity, collaboration, and enterprise services.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Microsoft Office 365 the way a machine reads it — 256 machine-readable artifacts across 12 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 365 scores 71.9/100 (exemplar), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Microsoft Office 365
Each block below is one kind of artifact we hold for Microsoft Office 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 12
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.
Outlook Contacts API
Access to Outlook personal contacts for managing contact information, creating contact folders, and organizing people data.
OneNote API
Access to OneNote notebooks, sections, and pages for creating and managing notes and structured content.
Excel Workbooks and Charts API
Read and modify Excel workbooks stored in OneDrive and SharePoint, including managing worksheets, tables, charts, ranges, and sessions.
Microsoft To Do API
Manage tasks and task lists across To Do clients, Outlook, and Teams for personal task management and day planning.
Microsoft Bookings API
Manage customer bookings, appointment scheduling, business services, and staff information for enterprise and small business owners.
Microsoft Graph Security API
Connect security products, services, and partners to streamline security operations and improve threat protection, detection, and response.
Microsoft Graph Communications API
Create and join online meetings, manage call records, and enable cloud communications capabilities for applications.
Office Add-ins Platform
Platform for building solutions that extend Office applications including Excel, Outlook, Word, PowerPoint, and OneNote using web technologies and the Office JavaScript API.
Microsoft Office 365 Calendar API
Access and manage Outlook calendar events, calendars, and calendar groups. Supports scheduling, meeting management, and free/busy lookups.
Microsoft Office 365 Groups API
Manage Microsoft 365 groups and security groups. Groups provide shared access to resources such as SharePoint sites, shared mailboxes, Planner plans, OneNote notebooks, and conv...
Microsoft Office 365 Mail API
Access and manage Outlook mail messages, mail folders, and message attachments. Supports reading, creating, sending, replying, forwarding, and organizing email.
Microsoft Office 365 Users API
Manage users in Azure Active Directory. Users are the core identity resource representing a person, including their profile, organizational relationships, and access to services.
Scroll within the panel for all 12 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
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 Office 365 Microsoft Graph API
OPEN COLLECTIONArazzo Workflows 19
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 365 Cancel Event
Create an event, read it back to confirm, then delete it from the calendar.
ARAZZOMicrosoft Office 365 Cleanup Draft Message
Create a draft, read it back, then delete it from the mailbox.
ARAZZOMicrosoft Office 365 Create Group With Members
Create a Microsoft 365 group, add a member, then list members to confirm.
ARAZZOMicrosoft Office 365 Deprovision User
Disable a user account, confirm the change, then delete the user.
ARAZZOMicrosoft Office 365 Draft and Send Mail
Create a draft message, read it back, then send it from the mailbox.
ARAZZOMicrosoft Office 365 Find Event in Window
Query a calendar view for a time window, then read the first event found.
ARAZZOMicrosoft Office 365 Find or Create Group
Look up a group by display name and create it only if it does not exist.
ARAZZOMicrosoft Office 365 Notify New User
Create a user, then send a welcome email to their new mailbox address.
ARAZZOMicrosoft Office 365 Onboard User to Group
Create a user, add them to an existing group, then confirm membership.
ARAZZOMicrosoft Office 365 Provision User
Create a new user, then read it back to confirm provisioning.
ARAZZOMicrosoft Office 365 Reschedule Event
Create an event, patch its start and end times, then read it back.
ARAZZOMicrosoft Office 365 Respond to Invitation
Read an event, then accept or decline it based on a desired response.
ARAZZOMicrosoft Office 365 Rotate Group Member
Remove one member from a group, add another, then list members to confirm.
ARAZZOMicrosoft Office 365 Schedule and Accept Event
Create an event, then accept it on behalf of the signed-in user.
ARAZZOMicrosoft Office 365 Schedule Event
Create a calendar event, then read it back to confirm the booking.
ARAZZOMicrosoft Office 365 Triage Inbox Message
Read the latest inbox message, then mark it as read and categorize it.
ARAZZOMicrosoft Office 365 Update Draft and Send
Create a draft, patch its subject and body, then send the updated message.
ARAZZOMicrosoft Office 365 Update Group and Verify
Patch a group's properties, then read it back to verify the change.
ARAZZOMicrosoft Office 365 Update User Profile
Patch a user's profile properties, then read the user back to verify.
ARAZZOScroll within the panel for all 19 ·
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 Office 365 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.
Features 9
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.
Unified API Endpoint
Access Microsoft 365 data through a single REST endpoint at graph.microsoft.com covering mail, calendar, files, users, and groups.
Real-Time Notifications
Subscribe to change notifications via webhooks to receive real-time updates when data changes across Microsoft 365 services.
Batch Requests
Combine multiple API requests into a single HTTP call to reduce network overhead and improve performance.
Delta Queries
Track incremental changes to resources efficiently using delta links without polling entire datasets.
Rich Mail Management
Read, send, reply, forward, and organize email messages with full attachment and folder support.
Calendar and Scheduling
Create events, manage calendars, check free/busy availability, and handle meeting responses programmatically.
File Storage and Sharing
Access OneDrive and SharePoint files with upload, download, sharing, and real-time collaboration capabilities.
Team Collaboration
Manage Microsoft Teams channels, messages, tabs, and apps for team communication and collaboration.
User and Group Management
Create, update, and manage users, groups, and organizational directory resources.
Scroll within the panel for all 9 ·
Semantic Vocabularies 2
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 Graph Context
JSON-LDMicrosoft Office 365 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 Office 365 API Rules
SPECTRALMicrosoft Office 365 API Rules
SPECTRALJSON Schema 82
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.
AssignedLicense
JSON SCHEMAAttendee
JSON SCHEMACalendarCollectionResponse
JSON SCHEMACalendar
JSON SCHEMADateTimeTimeZone
JSON SCHEMADirectoryObjectCollectionResponse
JSON SCHEMADirectoryObject
JSON SCHEMAEmailAddress
JSON SCHEMAEventCollectionResponse
JSON SCHEMAEventCreateRequest
JSON SCHEMAEvent
JSON SCHEMAEventUpdateRequest
JSON SCHEMAFollowupFlag
JSON SCHEMAGroupCollectionResponse
JSON SCHEMAGroupCreateRequest
JSON SCHEMAGroup
JSON SCHEMAGroupUpdateRequest
JSON SCHEMAItemBody
JSON SCHEMALocation
JSON SCHEMAMailFolderCollectionResponse
JSON SCHEMAMailFolder
JSON SCHEMAMessageCollectionResponse
JSON SCHEMAMessageCreateRequest
JSON SCHEMAMessage
JSON SCHEMAMessageUpdateRequest
JSON SCHEMAODataError
JSON SCHEMAObjectIdentity
JSON SCHEMAOnlineMeetingInfo
JSON SCHEMAOutlookGeoCoordinates
JSON SCHEMAPasswordProfile
JSON SCHEMAPatternedRecurrence
JSON SCHEMAPhysicalAddress
JSON SCHEMARecipient
JSON SCHEMARecurrencePattern
JSON SCHEMARecurrenceRange
JSON SCHEMAResponseStatus
JSON SCHEMATimeSlot
JSON SCHEMAUserCollectionResponse
JSON SCHEMAUserCreateRequest
JSON SCHEMAUser
JSON SCHEMAUserUpdateRequest
JSON SCHEMAAssignedLicense
JSON SCHEMAAttendee
JSON SCHEMACalendar
JSON SCHEMACalendarCollectionResponse
JSON SCHEMADateTimeTimeZone
JSON SCHEMADirectoryObject
JSON SCHEMADirectoryObjectCollectionResponse
JSON SCHEMAEmailAddress
JSON SCHEMAEvent
JSON SCHEMAEventCollectionResponse
JSON SCHEMAEventCreateRequest
JSON SCHEMAEventUpdateRequest
JSON SCHEMAFollowupFlag
JSON SCHEMAGroup
JSON SCHEMAGroupCollectionResponse
JSON SCHEMAGroupCreateRequest
JSON SCHEMAGroupUpdateRequest
JSON SCHEMAItemBody
JSON SCHEMALocation
JSON SCHEMAMailFolder
JSON SCHEMAMailFolderCollectionResponse
JSON SCHEMAMessage
JSON SCHEMAMessageCollectionResponse
JSON SCHEMAMessageCreateRequest
JSON SCHEMAMessageUpdateRequest
JSON SCHEMAObjectIdentity
JSON SCHEMAODataError
JSON SCHEMAOnlineMeetingInfo
JSON SCHEMAOutlookGeoCoordinates
JSON SCHEMAPasswordProfile
JSON SCHEMAPatternedRecurrence
JSON SCHEMAPhysicalAddress
JSON SCHEMARecipient
JSON SCHEMARecurrencePattern
JSON SCHEMARecurrenceRange
JSON SCHEMAResponseStatus
JSON SCHEMATimeSlot
JSON SCHEMAMicrosoft Office 365 User
JSON SCHEMAUserCollectionResponse
JSON SCHEMAUserCreateRequest
JSON SCHEMAUserUpdateRequest
JSON SCHEMAScroll within the panel for all 82 ·
JSON Structure 42
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 Graph Assigned License Structure
JSON STRUCTUREMicrosoft Graph Attendee Structure
JSON STRUCTUREMicrosoft Graph Calendar Collection Response Structure
JSON STRUCTUREMicrosoft Graph Calendar Structure
JSON STRUCTUREMicrosoft Graph Date Time Time Zone Structure
JSON STRUCTUREMicrosoft Graph Directory Object Structure
JSON STRUCTUREMicrosoft Graph Email Address Structure
JSON STRUCTUREMicrosoft Graph Event Collection Response Structure
JSON STRUCTUREMicrosoft Graph Event Create Request Structure
JSON STRUCTUREMicrosoft Graph Event Structure
JSON STRUCTUREMicrosoft Graph Event Update Request Structure
JSON STRUCTUREMicrosoft Graph Followup Flag Structure
JSON STRUCTUREMicrosoft Graph Group Collection Response Structure
JSON STRUCTUREMicrosoft Graph Group Create Request Structure
JSON STRUCTUREMicrosoft Graph Group Structure
JSON STRUCTUREMicrosoft Graph Group Update Request Structure
JSON STRUCTUREMicrosoft Graph Item Body Structure
JSON STRUCTUREMicrosoft Graph Location Structure
JSON STRUCTUREMicrosoft Graph Mail Folder Structure
JSON STRUCTUREMicrosoft Graph Message Collection Response Structure
JSON STRUCTUREMicrosoft Graph Message Create Request Structure
JSON STRUCTUREMicrosoft Graph Message Structure
JSON STRUCTUREMicrosoft Graph Message Update Request Structure
JSON STRUCTUREMicrosoft Graph O Data Error Structure
JSON STRUCTUREMicrosoft Graph Object Identity Structure
JSON STRUCTUREMicrosoft Graph Online Meeting Info Structure
JSON STRUCTUREMicrosoft Graph Outlook Geo Coordinates Structure
JSON STRUCTUREMicrosoft Graph Password Profile Structure
JSON STRUCTUREMicrosoft Graph Patterned Recurrence Structure
JSON STRUCTUREMicrosoft Graph Physical Address Structure
JSON STRUCTUREMicrosoft Graph Recipient Structure
JSON STRUCTUREMicrosoft Graph Recurrence Pattern Structure
JSON STRUCTUREMicrosoft Graph Recurrence Range Structure
JSON STRUCTUREMicrosoft Graph Response Status Structure
JSON STRUCTUREMicrosoft Graph Time Slot Structure
JSON STRUCTUREMicrosoft Graph User Collection Response Structure
JSON STRUCTUREMicrosoft Graph User Create Request Structure
JSON STRUCTUREMicrosoft Graph User Structure
JSON STRUCTUREMicrosoft Graph User Update Request Structure
JSON STRUCTUREMicrosoft Office 365 Structure
JSON STRUCTUREScroll within the panel for all 42 ·
Examples 67
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.
Microsoft Graph User Example
EXAMPLEScroll within the panel for all 67 ·
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 5
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 Productivity Integration
Build applications that integrate email, calendar, and file management into unified productivity workflows.
Automated Reporting
Generate automated reports by pulling data from mail, calendar, and user profiles across the organization.
Identity and Access Management
Manage user provisioning, group membership, and directory synchronization for enterprise identity workflows.
Team Communication Automation
Automate team notifications, channel management, and messaging workflows across Microsoft Teams.
Document Collaboration
Enable multi-user document editing, sharing, and version tracking through OneDrive and SharePoint APIs.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Azure Active Directory
Integrate with Azure AD for user authentication, authorization, and directory management.
Microsoft Teams
Build bots, tabs, and messaging extensions that integrate with Microsoft Teams collaboration platform.
Power Automate
Connect Microsoft Graph data to Power Automate flows for no-code/low-code automation.
Power BI
Feed Microsoft 365 data into Power BI dashboards for business intelligence and reporting.
SharePoint
Access SharePoint sites, lists, and document libraries for enterprise content management.
Outlook
Integrate with Outlook mail, calendar, and contacts for personal and shared mailbox management.
Resources
Every other property we hold for Microsoft Office 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 20
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 20 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
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-office-365 · machine-readable index on apis.io