established · -0.7 capability schema

Microsoft

Score 24.4 / 100 81 providers +3 via APIs 3 APIs Search apis.io →

Providers using this tag (81)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 21 Complete, well-documented, and agent-ready
Strong 22 Solid coverage with minor gaps
Microsoft FabricData AnalyticsData EngineeringData PlatformLakehouse4 APIs66.4Azure Blob StorageMicrosoft AzureBlobsCloud Storage5 APIs66.3Microsoft XboxGamingPlayFabXbox2 APIs65.0Azure SQL DatabaseDatabaseSQLRelational DatabaseMicrosoft Azure148 APIs64.4ContraforceSecuritySoftware-as-a-ServiceCybersecurity1 API63.4Microsoft Power AppsBusiness ApplicationsCloudEnterpriseLow-Code1 API63.2Microsoft VivaEmployee ExperienceInsightsLearning1 API62.6Microsoft Power AutomateAutomationBusiness ProcessIntegrationLow-Code10 APIs62.1Microsoft SharePointCollaborationDocument ManagementEnterprise Content ManagementIntranet1 API60.9Microsoft PlaywrightBrowser AutomationEnd-to-End TestingTesting5 APIs60.1Microsoft Power PagesDataverseLow-CodeWeb Portals4 APIs58.2Microsoft To DoMicrosoft 365ProductivityTask2 APIs58.2Azure AI SpeechCloudArtificial IntelligenceSpeech6 APIs57.9Microsoft OneNoteMicrosoft 365NotebooksNotes2 APIs57.0Microsoft Power Virtual AgentsChatbotsConversational AICopilot Studio4 APIs56.9Microsoft YammerEnterprise SocialSocial NetworkViva Engage1 API56.8Microsoft ProjectBudgetingGantt ChartsProject Management21 APIs56.3Microsoft ExcelAutomationData AnalysisMicrosoft 3652 APIs55.8Microsoft EdgeBrowserChromiumDeveloper ToolsEdge8 APIs54.8Microsoft PackageAzure ArtifactsDeveloper ToolsNuGet8 APIs54.6Azure AI Document IntelligenceArtificial IntelligenceDocument AIMicrosoft AzureIntelligent Document Processing2 APIs54.5Azure Container InstancesMicrosoft AzureCloudContainer InstancesContainers2 APIs63.0
Developing 8 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 5 Almost no public developer surface
Unrated 3 Not yet scored

APIs with this tag (3)

Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →

Strong 1 Solid coverage with minor gaps
Developing 1 Usable, with meaningful gaps to close
Thin 1 Limited public surface area

Companies reaching this through an API (3)

These companies publish an API, specification or operation carrying “Microsoft” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.

Anomaly Detection University of Exeter Wazo

Score breakdown

Frequency
49.3
log-scaled weighted occurrences
Breadth
1.0
spread across providers
Quality lift
49.1
mean composite of providers using it
Cohesion
13.3
strength of nearest seed neighbor

Related tags

Microsoft Graph 12 co-occurrences Microsoft Azure 18 co-occurrences Microsoft 365 10 co-occurrences SharePoint 6 co-occurrences .NET 8 co-occurrences Web API 5 co-occurrences Extensions 9 co-occurrences Spreadsheets 5 co-occurrences

Where this tag comes from

Provider tag81
Api tag3
Openapi tag1
Openapi op tag4

Cohort brief

Auto-generated

The 75 providers in the APIs.io catalog tagged Microsoft, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
75
of 81 in the catalog
Mean Kin Score
50.6
+26.5 vs catalog 24.1
Mean Agent Readiness
20.9
+6.8 vs catalog 14.1
Spread
2.6–76.7
median 56.8 · σ 20.3
How the 75 split by band
Exemplar 21Strong 22Developing 8Thin 12Emerging 9Minimal 3
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Operational Transparency 50.1 13.2 +36.9 75
Developer Ergonomics 58.9 24.5 +34.4 75
Contract Quality 37.6 18.6 +19 75
Access Clarity 48 30 +18 75
Discoverability 76.5 59.1 +17.4 75
Contract Governance 19.1 9.7 +9.4 75

A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 33% 18% +15
MCP server (first-party) 32% 16% +16
Agent Skills 0% 0% 0
OAuth scopes 49% 13% +36
Security 96% 99% -3
Arazzo workflows 14% 1% +13
Governance rules 68% 36% +32

mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.

All 81 members of this roster resolve to a provider in the catalog; 75 carry a score (93%). The figures above describe the scored members only.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.

Work with this as data

Every tag here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/microsoft"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.