Skip to content

Commit c6ef574

Browse files
committed
Unified connectors is now available for Okta Single Sign-On connectors (Preview)
1 parent 970175c commit c6ef574

File tree

3 files changed

+31
-5
lines changed

3 files changed

+31
-5
lines changed

ATPDocs/okta-defender-for-identity-overview.md

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,11 +46,25 @@ For a full list of supported alerts, see: [Defender for Identity XDR alerts](/de
4646

4747
### Use advanced hunting to investigate Okta activity
4848

49-
Advanced hunting lets you investigate identity activity across different services including Okta, Active Directory, and Microsoft Entra ID. The IdentityInfo table includes account metadata such as privilege level, group membership, and identity source.
49+
Advanced hunting lets you investigate identity activity across different services including Okta, Active Directory, and Microsoft Entra ID. The **IdentityInfo** table includes account metadata such as privilege level, group membership, and identity source. The **IdentityEvents** table includes events related to those identities, such as sign-ins, authentication attempts, and identity-related alerts across supported identity providers.
5050

51-
To explore the full schema and build your own queries, see [IdentityInfo ](/defender-xdr/advanced-hunting-identityinfo-table) and [IdentityEvents(Preview)](/defender-xdr/advanced-hunting-identityevents-table?branch=pr-en-us-4691).
51+
To explore the full schema and build your own queries, see:
52+
- [IdentityInfo ](/defender-xdr/advanced-hunting-identityinfo-table)
53+
- [IdentityEvents(Preview)](/defender-xdr/advanced-hunting-identityevents-table).
5254

53-
## Next steps
55+
### Remediation Actions
56+
57+
When Microsoft Defender for Identity identifies an identity as at risk, you can take the following remediation actions directly from the Defender portal to update the user's status in Okta.
58+
59+
- Revoke all user's sessions
60+
61+
- Deactivate user in Okta
62+
63+
- Set user risk in Okta
64+
65+
For more information, see: [Remediation actions in Microsoft Defender for Identity](remediation-actions.md#roles-and-permissions)
66+
67+
## Next steps
5468

5569
- [Connect Okta to Microsoft Defender for Identity](okta-integration.md)
5670

ATPDocs/okta-integration.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms. reviewer: izauer-bit
88

99
# Connect Okta to Microsoft Defender for Identity (Preview)
1010

11-
This article explains how to connect Microsoft Defender for Identity to your existing Okta account. This connection gives you visibility into and control over Okta use. For information about how Defender for Identity protects Okta, see: [How Defender for Identity helps protect your Okta environment](okta-defender-for-identity-overview.md).
11+
This page explains how to connect Microsoft Defender for Identity to your Okta account using the Unified Connectors experience. This connection provides visibility into Okta activity and enables shared data collection across Microsoft security products. The Unified Connectors experience allows Defender for Identity to collect Okta system logs once and share them with other supported Microsoft security products, such as Microsoft Sentinel. This reduces API usage, avoids duplicate data collection, and simplifies connector management. For more details, see [Unified connectors](/azure/sentinel/unified-connector?branch=pr-en-us-302665#unified-collector-service).
1212

1313
## Prerequisites
1414

@@ -24,6 +24,12 @@ Your Okta environment must have one of the following licenses:
2424
> - The Super Admin role is required only to create the API token. After you create the token, remove the role and assign the Read-Only Administrator and Defender for Identity custom roles for ongoing API access.
2525
> - If your Okta environment is already integrated with [Microsoft Defender for Cloud Apps](/defender-cloud-apps/protect-okta), connecting it to Microsoft Defender for Identity can cause duplicate Okta data, such as user activity, to appear in the Defender portal.
2626
27+
## Required Entra roles
28+
29+
To successfully set up the Okta connector, ensure that your account has one of the following Entra roles assigned:
30+
31+
- Security Operator
32+
- Security Admin
2733

2834
### Connect Okta to Microsoft Defender for Identity
2935

@@ -168,4 +174,4 @@ To complete the configuration in Okta, assign the custom role and resource set t
168174
169175
## Related articles
170176

171-
- [How Defender for Identity helps protect your Okta environment](okta-defender-for-identity-overview.md)
177+
- [How Defender for Identity helps protect your Okta environment](okta-defender-for-identity-overview.md).

ATPDocs/whats-new.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,12 @@ For updates about versions and features released six months ago or earlier, see
2525

2626
## August 2025
2727

28+
## Unified connectors is now available for Okta Single Sign-On connectors (Preview)
29+
30+
Microsoft Defender for Identity supports the [Unified connectors](/azure/sentinel/unified-connector?branch=pr-en-us-302665#unified-collector-service) experience, starting with the Okta Single Sign-On connector. This enables Defender for Identity to collect Okta system logs once and share them across supported Microsoft security products, reducing API usage and improving connector efficiency.
31+
32+
For more information see: [Connect Okta to Microsoft Defender for Identity (Preview)](okta-integration.md)
33+
2834

2935
## New security posture assessment: Remove discoverable passwords in Active Directory account attributes (Preview)
3036

0 commit comments

Comments
 (0)