# Check authenticator app policies

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/check-authenticator-app-policies/)

See where to check whether Okta, Microsoft Entra ID, Google Workspace, or JumpCloud allows time-based authenticator codes for a test account.

## 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](https://keysigner.io/integrations/setup-requirements/#provider-availability-okta)
- [Check Microsoft Entra ID availability](https://keysigner.io/integrations/setup-requirements/#provider-availability-microsoft-entra-id)
- [Check Google Workspace availability](https://keysigner.io/integrations/setup-requirements/#provider-availability-google-workspace)
- [Check JumpCloud availability](https://keysigner.io/integrations/setup-requirements/#provider-availability-jumpcloud)

## Data and access

- **Shared or checked**. The provider evaluates its authentication policy for the selected user and decides whether to offer a time-based code enrollment or challenge.
- **Check separately**. Group membership, app assignment and user-specific method policies can change what other users see.

## 1. 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.

## 2. 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.

## 3. 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.

## 4. 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.

## 5. 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.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## 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.

## Tools in this guide

- [Okta](https://keysigner.io/integrations/okta/)
  - [Review passkey access controls](https://help.okta.com/oie/en-us/content/Topics/identity-engine/authenticators/passkeys-access-controls.htm)
  - [Review verification rules for the Okta Admin Console](https://help.okta.com/oie/en-us/Content/topics/security/mfa/mfa-enable-admins.htm)
- [Microsoft Entra ID](https://keysigner.io/integrations/microsoft-entra-id/)
  - [Review how to enable passkeys for a pilot group](https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-authentication-passkeys-fido2)
- [Google Workspace](https://keysigner.io/integrations/google-workspace/)
- [JumpCloud](https://keysigner.io/integrations/jumpcloud/)
  - [Review supported security key setup](https://jumpcloud.com/support/use-security-key-or-device-authenticator-with-user-accounts)

## Setup instructions

- [Check authenticator enrollment in Okta](https://help.okta.com/oie/en-us/content/Topics/identity-engine/authenticators/google-authenticator.htm)
- [Review third-party OATH settings in Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-authentication-methods-manage)
- [Review Microsoft Entra ID authentication strengths](https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-strengths)
- [Check 2-Step Verification settings in Google Workspace](https://knowledge.workspace.google.com/admin/security/deploy-2-step-verification)
- [Check TOTP in the JumpCloud User Portal](https://jumpcloud.com/support/configure-totp-mfa-for-user-accounts)
- [Pilot an Okta access policy](https://keysigner.io/integrations/guides/pilot-an-okta-access-policy/)
- [Test a one-time code in a Keycloak realm](https://keysigner.io/integrations/guides/set-up-a-keycloak-one-time-code/)
- [Set up codes for Salesforce, PingOne, JumpCloud or Auth0](https://keysigner.io/integrations/guides/set-up-provider-account-sign-in-codes/)
- [Test a Google or Microsoft account code in KeySigner](https://keysigner.io/integrations/guides/set-up-workspace-account-sign-in-codes/)
- [Set up an Okta, OneLogin, miniOrange, or Oracle Fusion code](https://keysigner.io/integrations/guides/set-up-identity-provider-sign-in-codes/)

[More guides for this task](https://keysigner.io/integrations/tasks/test-account-access/)
