Microsoft Purview
Microsoft Purview is a comprehensive data governance service that helps organizations discover, catalog, classify, and manage their data estate across on-premises, multi-cloud, and SaaS environments.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Microsoft Purview the way a machine reads it — 235 machine-readable artifacts across 44 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 Purview scores 73.0/100 (exemplar), 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 Purview
Each block below is one kind of artifact we hold for Microsoft Purview. 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 44
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 Purview Accounts API
Operations for managing Purview accounts
Microsoft Purview Approval API
Operations for approving or rejecting workflow tasks
Microsoft Purview Business Domains API
Operations for managing business domains
Microsoft Purview Cases API
Operations for managing eDiscovery cases
Microsoft Purview Classification Rules API
Operations for managing classification rules
Microsoft Purview Critical Data Elements API
Operations for managing critical data elements
Microsoft Purview Custodians API
Operations for managing custodians within cases
Microsoft Purview Data Products API
Operations for managing data products
Microsoft Purview Data Profiling API
Operations for data profiling operations
Microsoft Purview Data Quality Rules API
Operations for managing data quality rules
Microsoft Purview Data Quality Scans API
Operations for running data quality scans
Microsoft Purview Data Quality Scores API
Operations for retrieving data quality scores
Microsoft Purview Data Sources API
Operations for managing data source registrations
Microsoft Purview Discovery API
Operations for searching and discovering data assets
Microsoft Purview DLP Policies API
Operations for evaluating DLP policies on content
Microsoft Purview Entity API
Operations for managing catalog entities
Microsoft Purview Glossary API
Operations for managing glossary terms, categories, and assignments
Microsoft Purview Glossary Terms API
Operations for managing glossary terms in the unified catalog
Microsoft Purview Label Policy Settings API
Operations for managing label policy settings
Microsoft Purview Legal Holds API
Operations for managing legal holds
Microsoft Purview Lineage API
Operations for tracking data lineage
Microsoft Purview Metadata Policy API
Operations for managing metadata policies
Microsoft Purview Metadata Roles API
Operations for managing metadata roles
Microsoft Purview OKRs API
Operations for managing Objectives and Key Results
Microsoft Purview Operations API
Operations available on the Purview resource provider
Microsoft Purview Private Endpoint Connections API
Operations for managing private endpoint connections
Microsoft Purview Protection Scopes API
Operations for computing protection scopes
Microsoft Purview Relationship API
Operations for managing relationships between entities
Microsoft Purview Retention Event Types API
Operations for managing retention event types
Microsoft Purview Retention Events API
Operations for managing retention events
Microsoft Purview Retention Labels API
Operations for managing retention labels
Microsoft Purview Review Sets API
Operations for managing review sets
Microsoft Purview Scan Result API
Operations for running scans and viewing scan results
Microsoft Purview Scan Rulesets API
Operations for managing scan rulesets
Microsoft Purview Scans API
Operations for managing scan configurations
Microsoft Purview Searches API
Operations for managing eDiscovery searches
Microsoft Purview Sensitivity Labels API
Operations for accessing tenant-level sensitivity labels
Microsoft Purview Triggers API
Operations for managing scan triggers and schedules
Microsoft Purview Type API
Operations for managing type definitions
Microsoft Purview User Requests API
Operations for submitting user requests
Microsoft Purview Workflow API
Operations for managing individual workflows
Microsoft Purview Workflow Run API
Operations for managing workflow runs
Microsoft Purview Workflow Task API
Operations for managing workflow tasks
Microsoft Purview Workflows API
Operations for listing workflows
Scroll within the panel for all 44 ·
Postman Collections 12
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.
Scroll within the panel for all 12 ·
Open Collections 12
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 Purview Account API
OPEN COLLECTIONMicrosoft Purview Catalog API
OPEN COLLECTIONMicrosoft Purview Data Map API
OPEN COLLECTIONMicrosoft Purview Data Quality API
OPEN COLLECTIONMicrosoft Purview Data Security and Governance API
OPEN COLLECTIONMicrosoft Purview eDiscovery API
OPEN COLLECTIONMicrosoft Purview Information Protection API
OPEN COLLECTIONMicrosoft Purview Metadata Policies API
OPEN COLLECTIONMicrosoft Purview Records Management API
OPEN COLLECTIONMicrosoft Purview Scanning API
OPEN COLLECTIONMicrosoft Purview Unified Catalog API
OPEN COLLECTIONMicrosoft Purview Workflow API
OPEN COLLECTIONScroll within the panel for all 12 ·
Arazzo Workflows 17
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 Purview Assign a Glossary Term to Entities
Create a glossary term and assign it to one or more catalog entities.
ARAZZOMicrosoft Purview Categorize a Glossary Term
Create a glossary category and a term that is filed under that category.
ARAZZOMicrosoft Purview Classify a Data Asset Entity
Register a catalog entity, confirm it, then apply and verify a classification.
ARAZZOMicrosoft Purview Define a Classification Type and Apply It
Register a custom classification typedef, confirm it, then classify an entity with it.
ARAZZOMicrosoft Purview Define a Data Quality Rule and Scan
Create a data quality rule, confirm it, then run a quality scan that evaluates it.
ARAZZOMicrosoft Purview Move Found Entities into a Collection
Search the catalog, then move the discovered entities into a target collection.
ARAZZOMicrosoft Purview Onboard an Entity into a Collection
Create a Data Map entity, confirm it, move it into a collection, and classify it.
ARAZZOMicrosoft Purview Profile a Data Asset and Poll for Results
Kick off data profiling for an asset, then poll until the profiling completes.
ARAZZOMicrosoft Purview Provision a Custom Scan Ruleset
Create a custom classification rule, build a scan ruleset that uses it, and confirm.
ARAZZOMicrosoft Purview Publish a Data Product
Create a business domain, confirm it, then publish a data product under it.
ARAZZOMicrosoft Purview Publish a Glossary Term
Create a glossary, confirm it, then create a term anchored to that glossary.
ARAZZOMicrosoft Purview Register a Data Source and Launch a Scan
Register a data source, configure a scan, and kick off a scan run.
ARAZZOMicrosoft Purview Relate Two Catalog Entities
Create an entity, then create a relationship linking it to another entity.
ARAZZOMicrosoft Purview Run a Scan and Poll to Completion
Launch a scan run, then poll scan history until the run reaches a terminal state.
ARAZZOMicrosoft Purview Schedule a Recurring Scan
Configure a scan, attach a recurring trigger, enable it, and confirm the schedule.
ARAZZOMicrosoft Purview Search and Classify a Found Asset
Search the catalog, read the top hit, and apply a classification to it.
ARAZZOMicrosoft Purview Trace Data Asset Lineage
Search for an asset, read its entity, then walk its lineage graph with pagination.
ARAZZOScroll within the panel for all 17 ·
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-purview-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 Purview 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 Purview Finops
FINOPSSemantic 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 Purview Context
JSON-LDSpectral Rules 1
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 Purview API Rules
SPECTRALJSON Schema 138
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.
AccessKeys
JSON SCHEMAMicrosoft Purview Account
JSON SCHEMAAccountEndpoints
JSON SCHEMAAccountList
JSON SCHEMAAccountProperties
JSON SCHEMAAccountSku
JSON SCHEMAAccountUpdateParameters
JSON SCHEMAAtlasClassification
JSON SCHEMAAtlasClassifications
JSON SCHEMAAtlasEntitiesWithExtInfo
JSON SCHEMAAtlasEntity
JSON SCHEMAAtlasEntityHeader
JSON SCHEMAAtlasEntityHeaders
JSON SCHEMAAtlasEntityWithExtInfo
JSON SCHEMAAtlasGlossary
JSON SCHEMAAtlasGlossaryCategory
JSON SCHEMAAtlasGlossaryHeader
JSON SCHEMAAtlasGlossaryTerm
JSON SCHEMAAtlasLineageInfo
JSON SCHEMAAtlasObjectId
JSON SCHEMAAtlasRelatedCategoryHeader
JSON SCHEMAAtlasRelatedObjectId
JSON SCHEMAAtlasRelatedTermHeader
JSON SCHEMAAtlasRelationship
JSON SCHEMAAtlasRelationshipWithExtInfo
JSON SCHEMAAtlasTermAssignmentHeader
JSON SCHEMAAtlasTermCategorizationHeader
JSON SCHEMAAtlasTypeDef
JSON SCHEMAAtlasTypeDefHeader
JSON SCHEMAAtlasTypesDef
JSON SCHEMAAttributeMatcher
JSON SCHEMAAttributeRule
JSON SCHEMAAuthorityTemplate
JSON SCHEMAAutoCompleteRequest
JSON SCHEMAAutoCompleteResult
JSON SCHEMAAutoCompleteResultValue
JSON SCHEMABusinessDomain
JSON SCHEMABusinessDomainList
JSON SCHEMACategoryTemplate
JSON SCHEMACheckNameAvailabilityRequest
JSON SCHEMACheckNameAvailabilityResult
JSON SCHEMACitationTemplate
JSON SCHEMAMicrosoft Purview Classification
JSON SCHEMAClassificationResult
JSON SCHEMAClassificationRule
JSON SCHEMAClassificationRuleList
JSON SCHEMAClassificationRulePattern
JSON SCHEMACollectionAdminUpdate
JSON SCHEMACollectionReference
JSON SCHEMAColumnProfile
JSON SCHEMAConnectedVia
JSON SCHEMAContentInfo
JSON SCHEMACriticalDataElement
JSON SCHEMACriticalDataElementList
JSON SCHEMAMicrosoft Purview Data Source
JSON SCHEMADataProduct
JSON SCHEMADataProductList
JSON SCHEMADataQualityRule
JSON SCHEMADataQualityRuleList
JSON SCHEMADataQualityScanRequest
JSON SCHEMADataQualityScanResult
JSON SCHEMADataQualityScore
JSON SCHEMADataQualityScoreList
JSON SCHEMADataSource
JSON SCHEMADataSourceList
JSON SCHEMADecisionRule
JSON SCHEMADepartmentTemplate
JSON SCHEMADlpAction
JSON SCHEMADlpMatchedRule
JSON SCHEMADowngradeJustification
JSON SCHEMAEdiscoveryCase
JSON SCHEMAEdiscoveryCustodian
JSON SCHEMAEdiscoveryHoldPolicy
JSON SCHEMAEdiscoveryReviewSet
JSON SCHEMAEdiscoverySearch
JSON SCHEMAMicrosoft Purview Atlas Entity
JSON SCHEMAEntityMutationResponse
JSON SCHEMAFilePlanReferenceTemplate
JSON SCHEMAMicrosoft Purview Glossary Term
JSON SCHEMAGlossaryTermList
JSON SCHEMAGovernanceContact
JSON SCHEMAIdentity
JSON SCHEMAIdentitySet
JSON SCHEMAInformationProtectionAction
JSON SCHEMAInformationProtectionPolicySetting
JSON SCHEMAKeyValuePair
JSON SCHEMALabelingOptions
JSON SCHEMALineageRelation
JSON SCHEMAMetadataPolicy
JSON SCHEMAMetadataPolicyList
JSON SCHEMAMetadataRole
JSON SCHEMAMetadataRoleList
JSON SCHEMAMoveEntitiesRequest
JSON SCHEMAOKR
JSON SCHEMAOKRList
JSON SCHEMAOperation
JSON SCHEMAOperationList
JSON SCHEMAOperationResponse
JSON SCHEMAParentRelation
JSON SCHEMAPrivateEndpointConnection
JSON SCHEMAPrivateEndpointConnectionList
JSON SCHEMAProfilingRequest
JSON SCHEMAProfilingResult
JSON SCHEMAProtectionScope
JSON SCHEMARecurrenceSchedule
JSON SCHEMAResourceLink
JSON SCHEMAMicrosoft Purview Retention Label
JSON SCHEMARetentionEvent
JSON SCHEMARetentionEventType
JSON SCHEMARetentionLabel
JSON SCHEMARuleResult
JSON SCHEMAMicrosoft Purview Scan
JSON SCHEMAScanList
JSON SCHEMAScanResult
JSON SCHEMAScanResultList
JSON SCHEMAScanRuleset
JSON SCHEMAScanRulesetList
JSON SCHEMASearchFacetItem
JSON SCHEMASearchRequest
JSON SCHEMASearchResult
JSON SCHEMASearchResultValue
JSON SCHEMAMicrosoft Purview Sensitivity Label
JSON SCHEMASensitivityLabel
JSON SCHEMASuggestRequest
JSON SCHEMASuggestResult
JSON SCHEMATermSearchResultValue
JSON SCHEMATimeBoundary
JSON SCHEMATrigger
JSON SCHEMATriggerRecurrence
JSON SCHEMAUserRequestPayload
JSON SCHEMAUserRequestResponse
JSON SCHEMAValidationResult
JSON SCHEMAWorkflow
JSON SCHEMAWorkflowCreateOrUpdateCommand
JSON SCHEMAWorkflowList
JSON SCHEMAWorkflowRun
JSON SCHEMAWorkflowTask
JSON SCHEMAWorkflowTrigger
JSON SCHEMAScroll within the panel for all 138 ·
JSON Structure 1
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 Purview Structure
JSON STRUCTURESecurity 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.
Resources
Every other property we hold for Microsoft Purview — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 23
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 23 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
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
Other 13
Properties that don't map to a standard resource type
Scroll within the panel for all 13 ·
← All providers · Data indexed from github.com/api-evangelist/microsoft-purview · machine-readable index on apis.io