Before you start
- Use a test account in a known group and ask a provider administrator to inspect the policies that apply to that account and app.
- Keep an independent recovery method or administrator available. Review existing settings and leave enforcement in place.
- Check Okta availability
- Check Microsoft Entra ID availability
- Check Google Workspace availability
- Check JumpCloud availability
Data and access
Okta
In the Okta Identity Engine Admin Console, open Security → Authenticators. Check that Google Authenticator is listed and that the Enrollment policy for the test user allows it. Check the app’s authentication policy as well. Okta documents this method as Google Authenticator.
Check. Record whether the pilot group can enroll Google Authenticator and whether the test app’s rule accepts it.
Microsoft Entra ID
In the Authentication methods policy, check Third-party software OATH tokens and whether the test user is in scope. In the account’s Security info setup, look for the option to use a different authenticator app. The built-in phishing-resistant MFA strength excludes software OATH codes.
Check. Record whether the software OATH policy includes the test user and whether the app’s sign-in requirement accepts that method.
Google Workspace
In the Admin console, open Security → Authentication → 2-step verification for the test user’s group or organizational unit. Check the Methods setting. Only security key allows security keys and passkeys and excludes authenticator app codes.
Check. Record the group or unit, its effective Methods setting and whether it permits codes.
JumpCloud
In the Admin Portal, open Security → MFA Configurations and check TOTP Configuration for the User Portal. Check whether the test user is required to use MFA. The User Portal setting is separate from the Admin Portal and other resources.
Check. Record the test user’s effective User Portal requirement and whether TOTP is available at that portal.
Check the specific sign-in
Keep the original session open and sign in from a private browser window. Note which method the provider offers for the exact app or portal and which recovery path remains available. Use the provider’s instructions to verify an allowed method with the test account.
Check. The private window shows the method you recorded and opens the expected app with that account when the allowed method succeeds.
Check your result
Record the method the test user was offered and the policy and group that applied. This walkthrough checks provider policy. To confirm that a specific authenticator works, test enrollment and a fresh sign-in on that account.
If you get stuck
The method is enabled but does not appear
Check whether the user is enrolled and which group, organizational unit, or app policy applies. The target app may require a stronger method than the provider allows for general enrollment. Use a method the policy already permits.