Rolling Out Provisioning Safely

Key Takeaways

  • Confirm operation support and use source credentials scoped to the intended target operations.

  • Apply configuration in a controlled population and check affected identities before widening criteria.

  • Turning off automated writes can route changes to manual work. Plan for that operational effect.

  • Use explicit authorized remediation for target changes already made. Configuration reversal alone leaves existing access to reconcile.

Last updated: November 2026

Prepare the change and its dependencies

Start with the approved business change. Specify which identity population should be affected, what event should trigger the change, and which source accounts may be created, modified, disabled or deleted. Ask the source owner to confirm connector support and the service account’s required permissions for that exact operation. Separate read access, account write access and privileged entitlement modification. Follow a successful Test Connection with evidence that the service account may write a protected field or change a restricted group.

Record a baseline from the tenant and the native system. Include the current source connection, account creation and synchronization configuration, affected role criteria, lifecycle state settings, and relevant assignment evidence. For a changed role, estimate which people qualify before applying it. Take note of accounts that have shared access or multiple correlated accounts. The size and complexity of the affected population determine the monitoring and support needed. For the pilot, assign ownership for both target checks and provisioning history. Set explicit stop criteria before activation. An unexpected group on a privileged account should halt expansion even if every other operation in the pilot completed successfully. Coordinate with people who own manual tasks and connectors before a rollout that may route fulfillment to them.

Release pointEvidence required to advance
Before productionSandbox tests at the appropriate connector and permission boundary, plus a reviewed list of expected changes
PilotSmall, deliberate population, representative target accounts, and identified operational owner
ExpansionVerified successful writes and absence of unintended accounts or privileges for excluded users
Stop and investigateUnexpected targets, unresolved partial operations, unexplained queue growth, or retries that mask a persistent fault
RecoveryVerified correction on the actual affected accounts and reconciled request or task state

Apply configurations with scope in mind

SailPoint documents that Apply Changes from roles, access profiles, and applications recalculates eligible identities, and advises completing that set of related edits before initiating the broader job. When a profile mapping change is involved, preview representative results. Applying changes from the profile processes its associated identities. For a small validation before expansion, targeted identity processing is available, with limits governed by the configuration you saved. Where a saved role could become effective through other processing in the meantime, use deliberately narrow pilot criteria or do the test in the sandbox. A pilot assumes scope control at the actual trigger, including source updates and scheduled processing.

Suppose a team introduces an expense role for one business unit. Rather than rely on a later broad Apply Changes as the first test event, make the first policy population a defined pilot. Include a person with no target account and a person with an existing one, each eligible for the same standing grant. Compare account creation and modification in the activity records. Verify group membership on the target and check a nearby nonpilot identity. Widen the eligibility only after the target results agree with the intended scope and the manual/retry queues are understood.

Plan recovery around the actual operation

A rollback can have two parts. First, stop or narrow future triggers according to the configuration, with explicit ownership for queued operations. Second, reconcile authorized remediation for any changes already written. For example, switching a supported direct-connect source to read-only can cause subsequent provisioning to create manual work items. Plan for routing and review those tasks. Disabling or deleting a role can prevent future assignment while leaving previously granted entitlements. Use supported assignment removal and reconcile shared access as part of an explicit access rollback.

Maintain a list of the operations that completed, failed or remain in flight. For each target account, compare current entitlements to the baseline and preserve legitimate shared access. Check whether a queued request could act after an operator corrects the target, then follow approved procedures for it. Validate recovery and safe expansion with actual source results. A rollout plan earns confidence when an operator can identify the intended operation, its evidence, and the response to a mismatch.

See SailPoint’s testing and provisioning overview, Apply Changes scope, source provisioning controls, and role disable and removal behavior.

Test Your Knowledge

A new expense role will trigger production writes. Which rollout preserves control over the first assignments?

A

Use deliberately narrow pilot eligibility, then check activity and native account/group changes before expanding

B

Enable company-wide criteria and rely on deleting the role later to remove all granted access

C

Skip the pilot because the target connection test passes

D

Use a read-only source and assume its manual tasks prove automatic writes

Test Your Knowledge

A source is switched to read-only to stop automatic changes during an incident. What does the runbook still need to address?

A

Only the time zone used by the identity profile

B

Only the source’s account name schema field

C

Manual work items for subsequent required changes and target access already written before the switch

D

An automatic deletion of all existing target accounts

Sections you finish are checked off in the contents.