Configuration versioning

Configuration versioning lets administrators review previous versions of supported configurations, compare them with the current version, and restore an earlier configuration.

📘

Restoring a version does not overwrite the existing version history. The selected version loads as an editable draft and is saved as a new version after you review or update it.

Supported configurations

Configuration versioning is available for:

  • Adaptive Access policies
  • Branding policies
  • Lifecycle Event Hooks
  • Identity stores
    • Changes to settings on the General and Configuration tabs are versioned.
  • Password quality policies
  • Self-service policies

View version history

📘

The View version history option is available to administrators with Read permission for Audit logs.

To view the version history of a supported configuration:

  1. Open the kebab menu (⋮) for the configuration to show additional actions.
  2. Select View version history.

The version history shows:

  • Version: The configuration version.
  • Date: The date and time when the version was created.
  • Actor: The administrator who made the change.

The active configuration is marked as the Current version.

You can filter the version history by date, version, or account ID.

Compare versions

Open a previous version to compare it with the current version.

The comparison view displays the selected version on the left and the current version on the right.

Differences in the underlying configuration data are highlighted so that you can identify values that were added, removed, or changed.

Each version shows its date, actor, and action. Expand the version details to view additional audit information, including:

  • URL
  • Version
  • IP address
  • User agent

Use the navigation arrows to move between versions.

Restore a previous version

Restoring a previous version loads its configuration as an editable draft. Existing versions are not overwritten.

To restore a version:

  1. Open the version you want to restore.
  2. Select Restore version [version].
  3. Select Restore version to confirm.
  4. If the version contains references that can no longer be resolved, update or remove those references when prompted.
  5. Review the restored configuration and make any additional changes.
  6. Select Restore to save the configuration as a new current version.

The restored configuration is validated using the current configuration rules before it is saved.

⚠️

Previous versions can contain a different policy tag from the current version.

When restoring a version, its policy tag is restored only if you have access to that tag. Otherwise, the restored configuration uses the policy tag from the current version.

Missing references

A previous version can contain references to configurations, variables, or secrets that are no longer available. This can happen if the referenced resource was removed or if you no longer have access to it.

When a missing reference prevents the selected version from being restored, the Admin Console prompts you to resolve it.

For example:

  • An Adaptive Access policy can reference a push notification or custom MFA configuration that no longer exists. You can remove the assignment or map it to another available configuration before restoring the version.
  • A Lifecycle Event Hook variable can use an instance variable or secret as its default value. If the referenced variable or secret no longer exists, you can remove the default value or map it to another available variable or secret.

The updated reference becomes part of the restored configuration when the new version is saved.



Did this page help you?