Key takeaways: Expanded platform coverage
- Say yes to more agent builder platforms: Okta’s AI Agent Import library now supports six major agent builder platforms: Gemini Enterprise Agent Platform, DataRobot, Workday, Microsoft, Glean, and LangSmith.
- Easily bring agents under governance: Custom agents running inside these platforms frequently operate outside central IAM visibility, creating compliance risks and security blind spots.
- Onboard all your agents into one registry: Security teams can now automatically sync and govern custom agents from these newly supported platforms to manage access, lifecycle controls, and deactivations within Okta’s single control plane.
Enterprise teams adopt AI agent platforms for specific, targeted advantages. They choose Anthropic's Claude because it excels at parsing complex code, legal contracts, and more. They choose Azure AI Foundry because it naturally plugs into their existing Microsoft stack. They choose DataRobot because it runs their predictive models.
The governance problem begins when each platform maintains its own isolated agent registry and policy layer, completely disconnected from the identity systems your security team uses to govern the rest of the organization. Meanwhile, agent adoption is outpacing governance programs by a wide margin.
Gartner predicts 40% of enterprise applications will feature task-specific AI agents by the end of 2026. Yet, fewer than one-third (32%) of organizations currently hold those agents to the same strict governance standards as human identities. That risk surface grows with every new agent a business team spins up.
Closing that gap starts with a foundational question from the blueprint for the secure agentic enterprise: Where are my agents?
The AI Agent Import feature of Okta for AI Agents does exactly that. It integrates with the builder tools your teams are actually using, pulling critical information about your agents’ identities from siloed platforms into a single, unified identity registry.
Once the data is imported into Okta, security and identity and access management (IAM) teams have a single place to manage ownership, lifecycle controls, access certifications, and deactivation.
A single platform's native registry can't offer that same coverage. It governs the agents within its walls. AI Agent Import is platform-agnostic, which means AI teams can keep building on whatever platform fits the job, and security gets the same governance guardrails everywhere. This way, you get the most out of your AI agents.
Supported agent platforms and governance capabilities
Connecting each builder tool directly to Okta extends visibility and automated control across your entire AI ecosystem. AI Agent Import already supports existing platforms, like Claude Managed Agents. With this latest expansion, the AI Agent Import library can help security teams govern and secure AI agents across the enterprise.
This capability now expands to additional agent builder platforms like:
- Gemini Enterprise Agent Platform
- DataRobot
- Workday
- Microsoft
- Glean
- LangSmith
More platforms, more tools, less visibility
Coverage gaps multiply with every platform you add. If your teams build on two platforms, governance often means managing two separate tools. Four platforms, four tools. Each covers its own agents and nothing else.
Discovery tools can surface a list of agents and flag risks. Detection tools can tell you what an agent did after something goes wrong. Neither can tell you who owns the agent running right now, what it has access to, or how to deactivate it before the next review forces the question.
Centralizing agent governance in your identity control plane is critical for keeping pace with how fast business teams adopt new tools. That is the power of AI Agent Import. Connect a platform once, and every agent registers automatically in Okta.
This means Okta registers the agent’s base profile, allowing you to view it in the same registry you use to govern your human identities. The registry stays current every time you run an import, reflecting any agents you add or remove at the source. Each platform uses a pre-built integration, not a custom connector your team has to build and maintain.
Where agents already touch your most sensitive workflows
AI teams don't wait for governance to catch up; they build. Take a few examples:
- A team spins up a custom customer service operations agent on the Gemini Enterprise Agent Platform (using Vertex AI Agent Engine) to handle tier-one support. It reads the customer relationship management (CRM) system, queries order history, and updates support tickets across thousands of daily interactions.
- Another team builds a custom HR onboarding agent in an enterprise HR system, such as Workday, that reads employee profiles, queries tax documents, and updates payroll routing details to automate internal transfers.
Both agents operate in production, have access to highly sensitive customer and employee data, and have permission to modify records.
But when your security team runs an access review, or a compliance officer processes a data subject request (DSR) or payroll audit requiring a paper trail of every system that touches that data, these agents are invisible. They do not exist in your identity inventory. They only live deep inside the Gemini or Workday platforms.
AI Agent Import changes that by pulling the identity of these agents directly into Okta, assigning them owners, and making them visible in the same reviews as every other human identity.
This logic holds across your SaaS ecosystem, including:
- Claude Managed Agents conducting automated code reviews
- Microsoft Copilot Studio and Microsoft Foundry agents accessing sensitive enterprise data
- Glean agents surfacing deep organizational knowledge
- Workday Agent System of Record (ASOR) automating critical HR workflows
- LangSmith deploying agents that orchestrate workflows, accessing internal tools and data
While the platforms and use cases differ, the solution remains the same. Connect the platform to Okta, run a sync, and every agent on it is automatically added to your central identity registry.
Extend visibility and control with every pre-built integration you add
Your teams will keep adopting new agent platforms. If closing each new gap requires custom code, your governance model will inevitably break.
We designed Okta’s expanding import library to stay ahead of that pace. You connect each platform to Okta individually using pre-built integrations, switching the workflow from building custom connectors to simply configuring them. We’ve already done the heavy lifting for you.
Each new integration adds to a shared governance layer that grows more complete with every platform you connect, and every agent your teams deploy on it.
The bottom line: The organization that centralizes agent governance today can confidently say "yes" to the platform their business teams want to use tomorrow. Set up the import, run the sync, and secure their access (and don't be surprised if the sheer number of registered agents catches your security team off guard.)
Secure the agentic enterprise with Okta for AI Agents
AI agents represent the fastest-growing identity in the enterprise and the least governed. Okta for AI Agents provides the central identity layer to securely manage your AI agents from a single control plane. By importing your AI agents into Okta, your security teams can discover, onboard, protect, and govern them at scale.
Ready to close the identity gap at the center of your AI security? Don’t leave your agentic enterprise unprotected. Get our blueprint for the secure agentic enterprise to help you answer three non-negotiable questions of agent security: Where are they? What can they connect to? What can they do?
These materials are intended for general informational purposes only and are not intended to be legal, privacy, security, compliance, or business advice. You are responsible for obtaining security, privacy, compliance, or business advice from your own professional advisors. Any mention of future products, features, functionalities, or certifications in this blog is for informational purposes only. These items are not commitments to deliver and should not be relied upon to make purchasing decisions. © Okta, Inc. and/or its affiliates 2026.
