Blog: AI agent identity in Okta and Entra ID
Reviewed 2026-11-10 · Editorial assessment by the editors
Longer pieces on how Okta and Microsoft Entra ID handle AI agents, grouped by theme. Each post reads the vendors' own availability statements, separates generally available features from planned ones, and links every fact to a dated source. Shorter buyer guides stay in the desk notes.
Shorter buyer guides and standards briefings are in the desk notes.
Product releases
What Okta and Microsoft shipped for agents this autumn, read against their own availability statements.
Oktane 2026 for AI agents separates available features from plans
. 5 min read.
Read the Oktane 2026 agent announcements by availability, from Agent SSO to planned gateway controls, endpoint discovery and runtime kill switch changes.
Entra Agent ID in autumn 2026 adds identity patterns and shared signals
. 5 min read.
Review Microsoft’s October Entra Agent ID announcement, including local agents, sensor-discovered identities and Project Perception, without assuming dates.
Shadow agent discovery differs across Okta and Microsoft
. 5 min read.
Compare Okta’s endpoint discovery descriptions with Microsoft’s sensor-discovered agent identities, then define evidence for ownership and access reviews.
Standards and controls
How NIST's agent identity tenets, runtime enforcement, delegated authorization and human approval map to current products.
Okta and Entra ID against NIST's ten agent identity tenets
. 5 min read.
Compare Okta and Microsoft Entra source statements against NIST's ten agent identity tenets, with roadmap limits and unstated controls clearly marked.
Where runtime enforcement sits for Okta and Microsoft
. 5 min read.
Locate agent runtime enforcement in Okta and Microsoft source statements, separating token decisions, tool-call controls, release plans and pilot evidence.
Cross App Access and Enterprise-Managed Authorization for Okta and Entra customers
. 5 min read.
Separate Cross App Access connections from action approval, with Okta Agent SSO facts, MCP authorization context and questions for Microsoft Entra customers.
Human approval for agent actions in Okta and Microsoft
. 5 min read.
Compare sourced human approval statements for Okta, Microsoft and NewCore, distinguishing named owners, roadmap features and review of individual actions.
Running agents
Registration, discovery, deactivation and dual-provider estates, as the vendors document them.
Agent registration at scale needs a reconciliation plan
. 5 min read.
Review Okta AI Agent Import, registration and MCP catalog updates alongside Entra agent identities, with a practical plan for ownership and reconciliation.
Governing agents across Okta and Entra ID
. 6 min read.
Plan agent governance across Okta and Entra ID by mapping identities, sponsors, connection policies, approval boundaries, and evidence for a shared workflow.
Deactivating agents in Okta and Entra ID
. 6 min read.
Distinguish agent deactivation from active-session termination in Okta and Entra ID, and define a kill-switch test with clear boundaries and recorded results.
Buying
Published prices, what is not public, and the questions to put to a provider.
Agent pricing as published for Agent 365 and Okta Agent SSO
. 5 min read.
Compare published Agent 365 pricing with Okta Agent SSO inclusion, separate workforce subscriptions, and identify agent controls that still need a quote.
Ten questions to ask your identity provider about AI agents
. 5 min read.
Ask identity providers ten concrete questions about agent identity, delegated access, runtime controls, human approval, revocation, evidence, and pricing.