Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Microsoft Entra website screenshot

Microsoft Entra

Microsoft Entra (formerly Azure Active Directory) provides identity and access management services including authentication, authorization, and directory services.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Microsoft Entra the way a machine reads it — 163 machine-readable artifacts across 17 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 Entra scores 67.3/100 (strong), 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 67.3/100 · strong
Contract Quality 17.0 / 25
Developer Ergonomics 9.6 / 20
Commercial Clarity 14.2 / 20
Operational Transparency 8.9 / 13
Governance 8.8 / 12
Discoverability 8.8 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Microsoft Entra

Each block below is one kind of artifact we hold for Microsoft Entra. 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 17

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 Entra ID Protection API

API for identity risk detection, investigation, and remediation.

Microsoft Entra Conditional Access API

API for managing conditional access policies and controls.

Microsoft Entra Privileged Identity Management API

API for managing privileged access and just-in-time administration.

Microsoft Entra Verified ID API

API for issuing and verifying decentralized identity credentials.

Microsoft Entra External ID API

API for managing customer and partner identity and access management.

Microsoft Entra ID Governance API

API for managing identity governance including access reviews, entitlement management, and lifecycle workflows to ensure the right people have the right access at the right time.

Microsoft Entra Application Management API

API for registering, configuring, and managing applications and service principals in Microsoft Entra ID.

Microsoft Entra Authentication Methods API

API for managing user authentication methods including FIDO2 security keys, passwordless phone sign-in, Microsoft Authenticator, and MFA registration.

Microsoft Entra Workload ID API

API for managing and securing identities for software workloads such as applications, services, scripts, and containers.

Microsoft Entra Provisioning API

API for automating user provisioning and deprovisioning using SCIM protocol, including API-driven inbound provisioning from any system of record.

Microsoft Entra Global Secure Access API

API for managing Microsoft Entra Internet Access and Microsoft Entra Private Access, providing identity-centric secure web gateway and zero-trust network access.

Microsoft Identity Platform API

API endpoints for OAuth 2.0, OpenID Connect, and SAML authentication protocols enabling application integration with Microsoft Entra ID.

Microsoft Entra Agent ID API

API for creating, securing, and monitoring AI agent identities, providing authentication, authorization, and lifecycle management for AI agents.

Microsoft Entra Applications API

Register and manage application objects that define application configuration including credentials, permissions, and sign-in settings

Microsoft Entra Groups API

Manage groups for organizing users, devices, and other principals including Microsoft 365 groups, security groups, and distribution lists

Microsoft Entra ServicePrincipals API

Manage service principal objects that represent application instances in a tenant for authentication and authorization

Microsoft Entra Users API

Manage user accounts in the directory including creation, updates, profile management, and lifecycle operations

Scroll within the panel for all 17 ·

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).

Arazzo Workflows 14

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 Entra Audit User Memberships

Find a user by UPN, read its profile, and list its group memberships.

ARAZZO

Microsoft Entra Create Group With Member

Create a security group, add a member, and list its members.

ARAZZO

Microsoft Entra Create Microsoft 365 Group With Member

Create a Unified M365 group, add a member, and read the group back.

ARAZZO

Microsoft Entra Decommission Application

Find a service principal by appId, delete it, then delete the app.

ARAZZO

Microsoft Entra Deprovision User

Disable a user account, then delete the user from the directory.

ARAZZO

Microsoft Entra Find And Update Application

Find an app by appId, update its display name, and read it back.

ARAZZO

Microsoft Entra Find And Update Group

Find a group by display name, update it, and read it back.

ARAZZO

Microsoft Entra Find And Update User

Find a user by UPN, update its profile, and read the result.

ARAZZO

Microsoft Entra Grant App Role Assignment

Grant an app role to a service principal then list its assignments.

ARAZZO

Microsoft Entra Offboard User From Group

Find a user by UPN, remove it from a group, and verify removal.

ARAZZO

Microsoft Entra Onboard User To Group

Create a user, add it to an existing group, and confirm membership.

ARAZZO

Microsoft Entra Provision User

Create a new Entra ID user and read back the provisioned account.

ARAZZO

Microsoft Entra Register Application With Service Principal

Create an app registration then instantiate its service principal.

ARAZZO

Microsoft Entra Rotate Application Secret

Add a fresh client secret to an app, then remove the old one.

ARAZZO

Scroll within the panel for all 14 ·

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 Entra Rate Limits

9 limits

RATE LIMITS

FinOps 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 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.

Identity and Access Management

Manage user identities, authentication, and authorization across cloud and hybrid environments with single sign-on.

Conditional Access

Enforce adaptive access policies based on user, device, location, and risk signals for zero trust security.

Identity Governance

Automate access reviews, entitlement management, and lifecycle workflows to ensure proper access controls.

Privileged Identity Management

Manage, control, and monitor privileged access with just-in-time and approval-based activation.

Verified ID

Issue and verify decentralized identity credentials using open standards for portable, self-sovereign identity.

External Identities

Enable secure collaboration with external partners and customers through B2B and B2C identity management.

Global Secure Access

Provide identity-centric secure web gateway and zero-trust network access for internet and private resources.

Workload Identities

Secure and manage identities for applications, services, scripts, and containers running as software workloads.

Scroll within the panel for all 8 ·

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 Entra Context

0 classes · 5 properties

JSON-LD

Microsoft Entra Graph Identity Context

0 classes · 0 properties

JSON-LD

Spectral 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 Entra API Rules

6 rules · 4 warnings

SPECTRAL

Microsoft Entra API Rules

17 rules · 8 errors · 8 warnings

SPECTRAL

JSON Schema 48

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.

ApiApplication

5 properties

JSON SCHEMA

Microsoft Entra Application

24 properties

JSON SCHEMA

ApplicationCollectionResponse

4 properties

JSON SCHEMA

AppRole

6 properties

JSON SCHEMA

AppRoleAssignment

8 properties

JSON SCHEMA

AppRoleAssignmentCollectionResponse

4 properties

JSON SCHEMA

AssignedLicense

2 properties

JSON SCHEMA

DirectoryObject

3 properties

JSON SCHEMA

DirectoryObjectCollectionResponse

4 properties

JSON SCHEMA

ApiApplication

5 properties

JSON SCHEMA

AppRoleAssignmentCollectionResponse

4 properties

JSON SCHEMA

AppRoleAssignment

8 properties

JSON SCHEMA

AppRole

6 properties

JSON SCHEMA

ApplicationCollectionResponse

4 properties

JSON SCHEMA

Application

13 properties

JSON SCHEMA

AssignedLicense

2 properties

JSON SCHEMA

DirectoryObjectCollectionResponse

4 properties

JSON SCHEMA

DirectoryObject

3 properties

JSON SCHEMA

GroupCollectionResponse

4 properties

JSON SCHEMA

Group

18 properties

JSON SCHEMA

KeyCredential

7 properties

JSON SCHEMA

ODataError

1 properties

JSON SCHEMA

ODataReference

1 properties

JSON SCHEMA

PasswordCredential

6 properties

JSON SCHEMA

PasswordProfile

3 properties

JSON SCHEMA

PermissionScope

8 properties

JSON SCHEMA

RequiredResourceAccess

2 properties

JSON SCHEMA

ServicePrincipalCollectionResponse

4 properties

JSON SCHEMA

ServicePrincipal

20 properties

JSON SCHEMA

SpaApplication

1 properties

JSON SCHEMA

UserCollectionResponse

4 properties

JSON SCHEMA

User

31 properties

JSON SCHEMA

WebApplication

4 properties

JSON SCHEMA

Group

18 properties

JSON SCHEMA

GroupCollectionResponse

4 properties

JSON SCHEMA

KeyCredential

7 properties

JSON SCHEMA

ODataError

1 properties

JSON SCHEMA

ODataReference

1 properties

JSON SCHEMA

PasswordCredential

6 properties

JSON SCHEMA

PasswordProfile

3 properties

JSON SCHEMA

PermissionScope

8 properties

JSON SCHEMA

RequiredResourceAccess

2 properties

JSON SCHEMA

ServicePrincipal

20 properties

JSON SCHEMA

ServicePrincipalCollectionResponse

4 properties

JSON SCHEMA

SpaApplication

1 properties

JSON SCHEMA

Microsoft Entra User

39 properties

JSON SCHEMA

UserCollectionResponse

4 properties

JSON SCHEMA

WebApplication

4 properties

JSON SCHEMA

Scroll within the panel for all 48 ·

JSON Structure 25

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 Entra Structure

0 properties

JSON STRUCTURE

Scroll within the panel for all 25 ·

Examples 24

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 24 ·

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.

Microsoft Entra Authentication

oauth2 · 1 scheme

SECURITY

Microsoft Entra Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Microsoft Entra Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Microsoft Entra Scopes

13 scopes · authorizationCode/clientCredentials

13 scopes

SCOPES

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.

Microsoft Entra Agentic Access

28 operations · 17 acting

28 operations · 17 acting

AGENTIC

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.

Zero Trust Implementation

Implement zero trust architecture with identity-based access controls, conditional access policies, and continuous verification.

Hybrid Identity Management

Synchronize and manage identities across on-premises Active Directory and cloud environments.

Application Single Sign-On

Enable SSO for thousands of SaaS and on-premises applications with SAML, OIDC, and password-based authentication.

Automated User Provisioning

Automate user lifecycle management with SCIM-based provisioning and deprovisioning across integrated applications.

AI Agent Identity Management

Create, secure, and monitor identities for AI agents with authentication, authorization, and lifecycle management.

Integrations 8

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 for identity and access management across all Microsoft 365 applications and services.

Azure Services

Native identity provider for Azure resources including VMs, databases, storage, and managed identities.

Active Directory

Hybrid identity synchronization with on-premises Active Directory using Azure AD Connect.

Salesforce

SAML and SCIM integration for single sign-on and automated user provisioning with Salesforce.

ServiceNow

SSO and automated provisioning integration with ServiceNow ITSM platform.

Workday

Inbound provisioning from Workday HR to automate user lifecycle management.

SAP

SSO and provisioning integration with SAP applications and S/4HANA.

Okta

Cross-platform identity federation and migration support with Okta identity provider.

Scroll within the panel for all 8 ·

Resources

Every other property we hold for Microsoft Entra — 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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/microsoft-entra · machine-readable index on apis.io