Okta

What it is

Okta is the independent workforce identity provider: single sign-on, MFA, a central user directory, provisioning into SaaS apps, and access reviews, sold to more than 20,000 customers. For an ops team it is the thing that decides who can open Salesforce, Ashby or Ironclad, and what happens to that access the day someone leaves.

What changed in 2026 is that Okta now treats AI agents as identities in the same directory as employees. It ships this in two layers, and buyers confuse them:

• Agent SSO — generally available on 24 August 2026 and included in core Okta SSO plans at no additional cost. An agent that supports Cross App Access (XAA) is registered in Universal Directory with a human owner, and instead of a stored API key it gets short-lived tokens issued under the same policies as the person it works for. Cross App Access is an OAuth extension Okta led in designing; it is now the official Enterprise-Managed Authorization extension for MCP. Launch partners include Anthropic (Claude), Slack, Notion, Linear, Glean, Granola, Asana, Atlassian, Figma, Canva, Datadog and Supabase.
• Okta for AI Agents — a separate, paid subscription, generally available on 30 April 2026. It adds discovery of shadow agents through browser, endpoint and network signals, coverage for agents that do not speak XAA, an Agent Gateway with a virtual MCP server that logs every agent-to-resource call, vaulting and rotation of agent credentials, access certifications, and Universal Logout for AI Agents — a kill switch that revokes an agent’s tokens everywhere.

Okta also closed its acquisition of Permiso Security, an identity threat-detection company, on 26 August 2026 (Okta 10-Q). Expect its detection to surface inside Identity Threat Protection over the next releases; do not buy on that roadmap.

The question it answers

“Do we govern our ops agents’ access through Okta, or do we need a separate MCP gateway or agent-security layer?” The answer depends on which agents you run. If the agents that matter are Claude, Glean or Slack-native agents reaching XAA-ready apps, Agent SSO covers registration, short-lived access and offboarding on the licence you already pay for — the cheapest governance you will find. If the risk is the long tail — n8n flows holding a Salesforce token, MCP servers someone installed on a laptop, agents built in-house — you need Okta for AI Agents or a dedicated gateway such as Runlayer or Obot. Agent SSO does not see agents that never ask Okta for a token.

Pricing reality

Okta publishes per-user list prices for its Workforce suites, billed annually, with a $1,500 annual contract minimum:

• Starter — $6/user/month: SSO, MFA, Universal Directory, 5 Workflows.
• Core Essentials — $14/user/month.
• Essentials — $17/user/month: adds Adaptive MFA, Lifecycle Management, Access Governance, Privileged Access for 2 admins and 50 Workflows.
• Professional and Enterprise — quote only: add Identity Threat Protection, Identity Security Posture Management, Device Access, API Access Management and more.

At 200 employees, Starter lists at $14,400 a year and Essentials at $40,800. Okta for AI Agents is a quote-only add-on with no published price, and Identity Governance is sold separately. The bill that surprises ops leaders is the one for SaaS apps: SCIM provisioning and SSO are often locked behind the vendor’s enterprise tier, so the real cost of “put it behind Okta” includes the upgrade on the other side. Price both before you promise it.

Best for

The IT or security lead at a 200-to-5,000-person company running a mixed SaaS estate — Google Workspace or Microsoft 365 plus Salesforce, Slack, an ATS and a CLM — who wants one place that decides which humans and which agents can reach each app. The scoped case where Okta wins: a RevOps or Legal Ops team rolling out Claude and Glean against Slack, Notion and Linear, where Agent SSO gives every agent an owner and a revocable token without buying another tool.

Not for

A Microsoft-only shop where Entra ID is already licensed in Microsoft 365 E3 or E5 — paying again for directory and SSO is hard to justify. Also not for a team under about 25 people: the $1,500 floor and the SaaS tier upgrades outweigh what a password manager with SSO would cost.

Versus the alternatives

• Microsoft Entra ID — bundled into Microsoft 365, so most companies already own it. Agent identity runs through Entra Agent ID and Microsoft Agent 365 at $15 per user per month. Pick Entra when most of your agents live in Copilot Studio, Foundry or the Microsoft tenant; pick Okta when the agents that matter act across non-Microsoft SaaS.
• Ping Identity — the other large independent workforce vendor, merged with ForgeRock under Thoma Bravo, strongest in hybrid and on-premises estates. Pick it when legacy apps and custom federation dominate the requirement list.
• Rippling AI Governance — the fastest-moving entrant: an MCP gateway, agent identity and shadow-AI detection launched in August 2026 on top of an HRIS. Pick it when Rippling is already your system of record and access should follow employment status without a separate identity vendor.
• Runlayer, Obot, Composio, Arcade — gateways and tool-auth layers that sit next to Okta, not instead of it. They federate to Okta for identity; pick one when the gap is MCP traffic inspection or agent write access to hundreds of apps, not who the agent is.
• Zenity or WitnessAI — pick these when the concern is what agents and copilots do with data at runtime, which an identity provider does not inspect.

Watch-outs

• Agent SSO only covers agents that ask. It registers XAA-capable agents; an automation holding a static API key is invisible to it. Guard: inventory agent credentials in your top ten SaaS apps before declaring coverage, and budget Okta for AI Agents or a gateway for whatever is not on the XAA partner list.
• Okta sits in the path of every login, which makes it a target. Its October 2023 support-system breach exposed customer session data. Guard: enforce phishing-resistant MFA for Okta admins, ship Okta System Log to your SIEM, and keep a documented break-glass admin account outside SSO.
• List price is only half the quote. SCIM and SSO on the SaaS side, Identity Governance, and the AI Agents add-on are all separate lines. Guard: get every add-on priced in the same quote, and cap the renewal uplift in the order form.
• Roadmap from acquisitions. Permiso’s detection is not yet a named Okta SKU. Guard: evaluate only what is generally available today, and write any promised feature into the contract with a date.

Related reading: MCP servers explained and the internal ops portal stack.