Connect SailPoint with a dedicated API principal and least-required roles

Use this document to resolve one bounded operational decision: Connect SailPoint with a dedicated API principal and least-required roles. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• The Defender portal API connector gives security administrators visibility into SailPoint-managed identities, identity-related threats, and account activity. The research record locates this support at Opening overview.
• The prerequisites require a SailPoint IdentityNow Admin role for application creation and documented Microsoft Entra or Defender permissions for setup. The research record locates this support at Prerequisites section.

The source support ends with the statements listed above. Use them to examine identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs in the applicable environment, not to imply a wider guarantee.

What the source does not establish

The connector is marked Preview; store client secrets securely and review every granted API scope before production use. 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 Prerequisites section, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations and sanitize protected material before retention.

Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Prerequisites section. Favor integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records, linked to stable identifiers, time, and operator.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

• Connect SailPoint Identity Security Cloud to Microsoft Defender for Identity (Preview) — Microsoft