Create Plan your upgrade rollout doc#6211
Conversation
Acrolinx scoreA minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Successfully checked 3 of 3 documents. Reopen the pull request or push new changes to check again. Depending on the Acrolinx server configuration, the |
Acrolinx scoreA minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Successfully checked 3 of 3 documents. Reopen the pull request or push new changes to check again. Depending on the Acrolinx server configuration, the |
Acrolinx scoreA minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Successfully checked 3 of 3 documents. Reopen the pull request or push new changes to check again. Depending on the Acrolinx server configuration, the |
Acrolinx scoreA minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Successfully checked 3 of 3 documents. Reopen the pull request or push new changes to check again. Depending on the Acrolinx server configuration, the |
Acrolinx scoreA minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Successfully checked 3 of 3 documents. Reopen the pull request or push new changes to check again. Depending on the Acrolinx server configuration, the |
|
|
||
| #### What you need | ||
|
|
||
| * Access to the Admin Console for each org you plan to upgrade |
There was a problem hiding this comment.
| * Access to the Admin Console for each org you plan to upgrade | |
| * Access to the Admin Console for each org that you plan to upgrade |
| Whichever strategy you choose, follow this sequence: | ||
|
|
||
| 1. Start with internal users or a small test group. | ||
| 2. Validate sign-in, registration, MFA enrollment, and password recovery end-to-end. |
There was a problem hiding this comment.
| 2. Validate sign-in, registration, MFA enrollment, and password recovery end-to-end. | |
| 2. Validate sign-in, registration, MFA enrollment, and password recovery flows end to end. |
|
|
||
| ## Upgrade your Sign-In Widget | ||
|
|
||
| If your app uses an embedded Sign-In Widget, verify that it runs version 5.11.0 or later before you schedule the org upgrade. Earlier versions don't support Identity Engine flows. If you haven't already upgraded the widget, do it now as part of your rollout prep, not at the same time as the org upgrade. |
There was a problem hiding this comment.
| If your app uses an embedded Sign-In Widget, verify that it runs version 5.11.0 or later before you schedule the org upgrade. Earlier versions don't support Identity Engine flows. If you haven't already upgraded the widget, do it now as part of your rollout prep, not at the same time as the org upgrade. | |
| If your app uses an embedded Sign-In Widget, verify that it runs version 5.11.0 or later before you schedule the org upgrade. Earlier versions don't support Identity Engine flows. If you haven't already upgraded the widget, do it now as part of your rollout prep. |
|
|
||
| ## Replace Integrated Windows Authentication | ||
|
|
||
| Integrated Windows Authentication (IWA) routing rules needs to be removed before you can upgrade. The Identity Engine Upgrade Hub blocks the upgrade if any IWA routing rules exist in your org. |
There was a problem hiding this comment.
| Integrated Windows Authentication (IWA) routing rules needs to be removed before you can upgrade. The Identity Engine Upgrade Hub blocks the upgrade if any IWA routing rules exist in your org. | |
| Remove Integrated Windows Authentication (IWA) routing rules before you upgrade. The Identity Engine Upgrade Hub blocks the upgrade if any IWA routing rules exist in your org. |
|
|
||
| Integrated Windows Authentication (IWA) routing rules needs to be removed before you can upgrade. The Identity Engine Upgrade Hub blocks the upgrade if any IWA routing rules exist in your org. | ||
|
|
||
| To prepare: |
There was a problem hiding this comment.
| To prepare: | |
| To prepare, complete the following steps: |
|
|
||
| Classic Engine Device Trust isn't supported in Identity Engine. The replacement is Okta Verify with managed certificates and Okta FastPass. | ||
|
|
||
| Start by identifying whether your org uses Device Trust for Desktop, mobile, or both, then plan the migration path for each. |
There was a problem hiding this comment.
| Start by identifying whether your org uses Device Trust for Desktop, mobile, or both, then plan the migration path for each. | |
| Start by identifying whether your org uses Device Trust for Desktop, mobile, or both, and then plan the migration path for each. |
|
|
||
| ## Replace Okta Mobile | ||
|
|
||
| Okta Mobile is deprecated and unavailable after the Identity Engine upgrade. Before upgrading, make sure that all affected users are enrolled in Okta Verify. |
There was a problem hiding this comment.
| Okta Mobile is deprecated and unavailable after the Identity Engine upgrade. Before upgrading, make sure that all affected users are enrolled in Okta Verify. | |
| Okta Mobile is unavailable in Identity Engine. Before upgrading, make sure that all affected users are enrolled in Okta Verify. |
| Okta Mobile is deprecated and unavailable after the Identity Engine upgrade. Before upgrading, make sure that all affected users are enrolled in Okta Verify. | ||
|
|
||
| * Identify which users currently rely on Okta Mobile. | ||
| * Communicate the deprecation timeline to those users. |
There was a problem hiding this comment.
is the phrase "deprecation timeline" accurate? Okay if so, but I don't think we call other features that are Classic-only "deprecated in OIE"
Description
Adds a new developer guide, Plan your upgrade rollout, for the "Prepare to Upgrade to Okta Identity Engine" journey.
The guide walks developers and admins through sequencing org upgrades (preview → sandbox → production), rolling out Identity Engine flows gradually to user segments using code-based routing, load balancing, or incremental scaling, and replacing deprecated features — Integrated Windows Authentication, Device Trust, and Okta Mobile — before the upgrade.
This update also adds five new sections sourced from gaps identified against the admin-facing help.okta.com content:
Files changed:
Is this PR related to a Monolith release?
No. Targeting the July monthly developer docs release (code freeze June 26, 2026.07.0).
Resolves
Netlify preview link
Preview link