Cybersecurity

Managing hybrid identity access with Okta

Hybrid identity environments face visibility gaps when Okta operates alongside Active Directory and Microsoft Entra ID. Microsoft Defender for Identity mitigates these risks by correlating Okta user activity with on-premises data to detect high-risk behaviors like token abuse.

Managing hybrid identity access with Okta

Visibility gaps in hybrid identity models

In a hybrid workforce environment, monitoring identity activity becomes difficult because Okta functions alongside on-premises systems like Active Directory and cloud services like Microsoft Entra ID. This hybrid model makes it harder to detect threats consistently across different platforms. Microsoft Defender for Identity ingests Okta user and activity data and correlates it with identity data from Active Directory and Microsoft Entra ID. This integration provides a centralized view of user activity, posture risks, and suspicious behavior across the identity infrastructure. Microsoft Defender for Identity adds Okta users to the identity inventory in the Microsoft Defender portal to allow unified tracking across platforms. The IdentityInfo table includes account metadata such as privilege level, group membership, and identity source, while the IdentityEvents table includes events related to those identities such as sign-ins and authentication attempts. Microsoft Defender alerts you when it detects high-risk behavior in Okta, such as anonymous sign-ins, privileged role assignments, and token abuse. Administrators can also receive alerts for a privileged API token being created or updated, or for suspicious privileged role assignments to an application. If the system identifies an identity as at risk, you can take remediation actions directly from the Defender portal by revoking all user sessions, deactivating the user, or setting the user risk.

Errors in privileged account management

Administrators often fail to secure their identity environment by leaving too many Okta accounts with privileged roles or failing to limit the number of Okta Super Admin accounts. High numbers of privileged roles or highly privileged Okta API tokens increase the risk of misuse. You must assign multifactor authentication to Okta privileged user accounts and change passwords for these accounts to maintain security. Microsoft Defender for Identity evaluates identity configuration in Okta and surfaces posture recommendations in Microsoft Secure Score, such as removing dormant Okta privileged accounts. Security teams must address the risks of the agentic stack by using Identity Security Posture Management to identify risky agents and exposed credentials. Using Microsoft Defender for Identity to gain a unified view of user activity across the entire identity infrastructure is the most effective way to secure this environment. Okta for AI Agents becomes generally available on April 30, 2026, to help discover, register, authenticate, govern, and manage AI agents. The platform also includes Auth0 for AI Agents to secure and scale agentic applications. Organizations must prioritize establishing secure permissions and verifying AI agent identity within a single, secure ecosystem.

Configuration requirements for Defender integration

Technical setup requires adding specific custom user attributes in the Okta Profile Editor to ensure the connection functions. You must add ObjectSid, ObjectGuid, and DistinguishedName as string data types.

Attribute Display Name Variable Name Data Type
ObjectSid ObjectSid String
ObjectGuid ObjectGuid String
DistinguishedName DistinguishedName String

To support ongoing API access, administrators must assign both the Read-Only Administrator role and the custom Microsoft Defender for Identity role to the dedicated account, as configuration fails if either role is missing. The custom role must include permissions to edit user’s lifecycle states, edit user’s authenticator operations, and view roles, resources, and admin assignments. Administrators must also create a resource set named Microsoft Defender for Identity and add All users and All Identity and Access Management resources to that set. After the Super Admin creates the API token by selecting Security, then API, then Tokens, and choosing Any IP, the administrator should remove the Super Admin role and assign the Read-Only Administrator and custom roles to ensure the account only holds relevant permissions. If an identity becomes at risk, the Microsoft Defender portal allows you to revoke all user sessions, deactivate the user in Okta, or set the user risk in Okta. Does the removal of the Super Admin role create new permission gaps for automated tasks?