Avoid duplicate Okta ingestion when enabling the Defender for Identity connector

Use this document to connect an official requirement or behavior to observable evidence: Avoid duplicate Okta ingestion when enabling the Defender for Identity connector. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Connect Okta to Microsoft Defender for Identity (Preview) from Microsoft supports the following bounded statements:

• The connector collects Okta system logs once and shares them with supported Microsoft security products to reduce API use and duplicate collection. The research record locates this support at Opening overview.
• If Okta is already integrated through Microsoft Defender for Cloud Apps, enabling the Defender for Identity connection can cause duplicate Okta data in the Defender portal. The research record locates this support at Duplicate-data warning.

Keep the evidence boundary at these traced claims. They support a review of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

The connector is marked Preview; inventory existing integrations and validate resulting records before changing production collection. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Duplicate-data warning, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Tie each conclusion back to Opening overview; Duplicate-data warning and to observable material such as integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Connect Okta to Microsoft Defender for Identity (Preview) — Microsoft