This article explains why Okta Verify enrollment is not automatically triggered when a user navigates to the admin portal URL to begin the enrollment process. While direct access to the organization URL (for example, http://<subdomain>.okta.com) typically initiates enrollment automatically for users who want to add their account on Okta Verify, using the admin portal URL (for example, http://<subdomain>-admin.okta.com) leads to a redirection to the organization URL, but the enrollment sequence does not start.
- Okta Verify
- MFA Enrollment
- Android
- iOS
- macOS
- Windows
- Okta Identity Engine (OIE)
The automatic Okta Verify enrollment process is designed to be initiated upon direct navigation to the organization URL. When a user is redirected from an admin portal URL to the organization URL, the redirected path does not contain or trigger the parameters required for the Okta Verify enrollment sequence to begin.
To ensure the automatic Okta Verify enrollment is triggered:
Navigate directly to the organization URL (for example, http://<subdomain>.okta.com) using a web browser instead of using the admin portal URL (for example, http://<subdomain>-admin.okta.com) to initiate the enrollment process.
