Deferred release migration FAQ
What has changed?
When the deferred release feature was introduced, it was an opt-in feature. This meant that Advanced Identity Cloud customers could choose whether to enable the feature for their tenants. From October 21, 2025, the deferred release feature has changed so it’s a standard feature.
Why has this changed?
By making deferred release a standard feature, Ping Identity is enhancing the release experience for all customers and delivering a consistent and controlled approach to managing change in production:
-
You can defer production upgrades for up to 7 days. This lets you validate new features and updates in your lower environments before they reach production.
-
You can trigger the production upgrade at any time during the 7-day deferral period. You can also select a preferred upgrade time in UTC for the automatic production upgrade at the end of the 7-day deferral period. This lets you align production upgrades with your organization’s change management processes and minimize disruption to your end users.
How are new tenants affected?
Production tenants created on or after October 21, 2025 have the deferred release feature as standard.
How are existing tenants affected?
Existing production tenants that already have the deferred release feature enabled aren’t affected by this change.
Existing production tenants that don’t yet have the deferred release feature enabled will be migrated in phases, with each phase preceded by a 4-week notice period to let you prepare.
How can I prepare for the change?
If you have an existing production tenant that doesn’t yet have the deferred release feature enabled, your Ping Identity representative will contact you to discuss the migration process and help you prepare for the change. You’ll have 4 weeks' notice before your tenant is migrated. When your migration date arrives, Ping Identity will make the necessary changes to enable the deferred release feature for your production tenant.