<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5WR00001PmUuz0AFOkta Classic EngineMulti-Factor AuthenticationAnswered2026-09-01T21:31:33.000Z2026-03-10T09:43:53.000Z2026-09-01T21:31:33.000Z
  • Mihai N. (Okta, Inc.)

    Updating this response for ease of access and reference:

     

    End users attempting to transfer Okta Verify to a new device may fail to generate a QR code or an eight-digit code via Bluetooth. This occurs because the organization must enable specific features, such as Okta FastPass, to support this transfer method. To resolve this, the user must verify the feature requirements, use an alternative authentication method to enroll the new device, or contact the IT support desk for a multifactor authentication (MFA) reset.

     

    Applies To

    • Okta Identity Engine (OIE)
    • Okta Classic Engine
    • Okta Verify

     

    Cause

    The organization must configure specific requirements, such as enabling Okta FastPass, to allow the transfer of an Okta Verify account to another device using Bluetooth. If the organization disables these features, the original device fails to generate the required QR code or eight-digit code.

     

    Solution

    How does an end user transfer Okta Verify to a new device using Bluetooth?

    The user must ensure the organization enables the required features, such as Okta FastPass, to use the Bluetooth transfer option. Add the Okta Verify account to another device using Bluetooth by following the appropriate device-specific guide.

     

    End users must use an alternative authentication method or contact IT support if the Bluetooth transfer fails.

    If the Bluetooth transfer requirements remain unmet, the user must sign in to the Okta account using an alternative multifactor authentication (MFA) option, such as SMS, Google Authenticator, or a YubiKey, to enroll the new device. If the user lacks an alternative authentication method, they must contact the organization IT support or Help Desk. The IT support team must reset the MFA configuration to trigger a new enrollment flow. The organization handles individual account management at the tenant level.

     

    Related References

     

    Summary

    Transfer Okta Verify to a new device by meeting the Bluetooth requirements, using an alternative authentication method, or requesting an MFA reset.

     

     

     

     

    Regards.

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • Mihai N. (Okta, Inc.)

    Hi @KennyN.19554 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    There are a few requirements, for example the FastPass feature, to be able to use the “add your Okta account to another device option”. Details here: 

     

    For iOS: 

    https://help.okta.com/eu/en-us/content/topics/end-user/ov-ios-add-acc-bluetooth.htm

     

    For Android: 

    https://help.okta.com/eu/en-us/content/topics/end-user/ov-andr-add-acc-bluetooth.htm

     

     

    Additional guides: 

    Android: https://help.okta.com/eu/en-us/content/topics/end-user/ov-setup-android.htm

    iOS: https://help.okta.com/eu/en-us/content/topics/end-user/ov-setup-ios.htm

     

     

     

    Otherwise, for security reasons you'll need to use an alternative option (ex. SMS, Google Authenticator, Yubikey etc) to sign into your Okta account and enroll the new device. If you do not have an alternative option, please reach out to the company's or service provider's IT support or Help Desk so they can help you enroll a new device and provide further assistance. They will need to reset your MFA and this will trigger a new enrollment flow. 

     

    While Okta provides the Product (Okta Verify app), individual account management is handled by your company or service provider at tenant level. 

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    • KennyN.19554 (Customer)

      Hi Mihai,

      Thanks for the reply.
      How can I use an alternative option (ex. SMS, Google Authenticator, Yubikey etc) to sign into your Okta account and enroll the new device ?

      Regards.
      Kenny
      Expand Post
      • Mihai N. (Okta, Inc.)

        You will need to use the browser to go to your organization's site (if this is for a work account) and on the login page after you provide the username/password, you should be asked for MFA. On that page, if it's enable and configured, you should be able to choose a different method other than Okta Verify.

        Once you log in, you can go to your account setting and configure Okta Verify again.  

        If not alternative MFA options are provided, you will need to reach out to the IT Support/Help Desk of your organization, so they can trigger a re-enrollment from their end.  

         

        Regards.

        --

        Help others in the community by liking or hitting Select as Best if this response helped you.

        Collect them all. Learn a new skill and earn a new Okta Learning badge.

        Just released: More Okta Community badges just added

        Expand Post
      • KennyN.19554 (Customer)

        Hi Mihai,

        Is this the site for my organization ?

        [REDACTED by Moderator]

        ?

        Unfort we do not have the login credential for this site. How can I re-enroll it as I am the IT Support here ?

        Regards.

        Kenny

        [REDACTED by Moderator]

        Expand Post
      • Mihai N. (Okta, Inc.)

        We would not be able to validate this for you.

        I recommend reaching out to you internal resources to clearly define the way Okta was integrated with your organization (if at all) and what the support structure is there.

        It's unclear at this point if you(or your organization) are an Okta Customer or not. It could be that you are using a third party service that just happens to use Okta as back-end platform for its services.

        IT Support within the organization does not necessarily mean that it covers the Okta implementation. It could have been outsourced to a third-party.

        An Okta Administrator should already have access to the information and tools you require as well as points of contact for support within Okta.

         

        Regards.

        --

        Help others in the community by liking or hitting Select as Best if this response helped you.

        Collect them all. Learn a new skill and earn a new Okta Learning badge.

        Just released: More Okta Community badges just added

        Expand Post
  • Mihai N. (Okta, Inc.)

    Updating this response for ease of access and reference:

     

    End users attempting to transfer Okta Verify to a new device may fail to generate a QR code or an eight-digit code via Bluetooth. This occurs because the organization must enable specific features, such as Okta FastPass, to support this transfer method. To resolve this, the user must verify the feature requirements, use an alternative authentication method to enroll the new device, or contact the IT support desk for a multifactor authentication (MFA) reset.

     

    Applies To

    • Okta Identity Engine (OIE)
    • Okta Classic Engine
    • Okta Verify

     

    Cause

    The organization must configure specific requirements, such as enabling Okta FastPass, to allow the transfer of an Okta Verify account to another device using Bluetooth. If the organization disables these features, the original device fails to generate the required QR code or eight-digit code.

     

    Solution

    How does an end user transfer Okta Verify to a new device using Bluetooth?

    The user must ensure the organization enables the required features, such as Okta FastPass, to use the Bluetooth transfer option. Add the Okta Verify account to another device using Bluetooth by following the appropriate device-specific guide.

     

    End users must use an alternative authentication method or contact IT support if the Bluetooth transfer fails.

    If the Bluetooth transfer requirements remain unmet, the user must sign in to the Okta account using an alternative multifactor authentication (MFA) option, such as SMS, Google Authenticator, or a YubiKey, to enroll the new device. If the user lacks an alternative authentication method, they must contact the organization IT support or Help Desk. The IT support team must reset the MFA configuration to trigger a new enrollment flow. The organization handles individual account management at the tenant level.

     

    Related References

     

    Summary

    Transfer Okta Verify to a new device by meeting the Bluetooth requirements, using an alternative authentication method, or requesting an MFA reset.

     

     

     

     

    Regards.

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
This question is closed.
Loading
Unable to get QR code or 8 digits code from original phone