Playbook: Okta Classic Engine loses three features on March 5, 2027

3 Reply templates

Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

Helpful first

Sorry you have to deal with this. You can stay on Okta. Here is what to change before March 5, 2027:

1. Check which engine you use. In the Okta Admin Console, check if your org runs Classic Engine.
2. List the features you use. Note if you use Self-Service Registration, Desktop SSO or Device Trust.
3. Plan the Identity Engine upgrade. Okta upgrades orgs in waves. Plan yours well before March 5, 2027.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]

Short answer

You have until March 5, 2027. You can stay on Okta. First: check which engine you use. Then list the features you use.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

If you do nothing

> What happens if I do nothing?

Okta says:
- If you do nothing: You lose access to them unless you upgrade to Okta Identity Engine first.

You can stay on Okta. To choose when it happens, make the change yourself before March 5, 2027.
Details: https://developer.okta.com/blog/2026/09/18/okta-classic-engine-deprecation

I build a tool for people who would rather leave: <your link>
[Disclosure: I build <your product>.]

4 Switch-page builder

Create a draft “Switch from Okta” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

Add your product name to replace “Your product”.

Preview

Switch from Okta to Your product

Okta Classic: registration, Desktop SSO, Device Trust: a change is due by March 5. You can stay on Okta. If you would rather leave, here is how to move to Your product.

What changes at Okta

From March 5, 2027, Okta turns off Self-Service Registration, Desktop SSO and Device Trust on Classic Engine. To keep them, upgrade to Okta Identity Engine first. The upgrade is free.

Features turn off: March 5, 2027 (Okta)
Features: Self-Service Registration, Desktop Single Sign-On (IWA) and Device Trust (Okta)
If you do nothing: You lose access to them unless you upgrade to Okta Identity Engine first (Okta)
Cost of the upgrade: Free (Okta)
Self-Service Registration becomes: Profile Enrollment Policy (Okta)
Desktop SSO becomes: Agentless Desktop SSO or Okta FastPass (Okta)
Device Trust becomes: Management attestation with Okta Verify (Okta)
Announced: September 18, 2026 (Okta)
Orgs still on Classic Engine using these features: Lose them on March 5, 2027 (Okta)

You can stay on Okta if you make the change. This page is for people who would rather leave.

What Your product gives you

Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

How to move from Okta to Your product

Save what you need from Okta. Keep a copy before you cancel anything.
Import into Your product. Say which files you accept and how long an import takes.

Tell readers the key date: March 5, 2027.

Questions people ask

If Your product has a direct answer to one of these, add it here. Keep it short and true.

How to help new users settle in

Send one short email. Say what changed, where to find you now, and what they need to do. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Sources

Okta Classic Engine deprecation — Okta (primary), checked 2026-10-13

Okta Classic Engine loses three features on March 5, 2027

1 Related discussions

2 What people ask