Resolve device requirement issues

If you receive a Device requirements not set message when trying to sign in to apps using Okta, your device doesn't meet the security requirements for your org.

Follow the troubleshooting steps outlined here, then attempt to sign in to your app again. If the problem persists, contact your org's help desk for assistance.

If you receive a Use a device managed by your organization. message, the app requires a device that your org manages. See Your device isn't managed by your organization.

Note:

Ensure that your device has the latest version of Okta Verify installed. See Okta Verify release notes.

Check the Device health page in Okta Verify to see which device conditions might be blocking access to your app.

Open Okta Verify on your device.
Go to the Device health page:
- On Android, go to Settings (...) > Device health.
- On iOS, go to Settings (...) > Device Health.
- On macOS or Windows, click the gear icon, and then select View device health.

Identify which security checks failed and follow the instructions to fix the issue.

Message	What to fix
`Outdated operating system version`	Update your operating system to the latest version.
`No password set`	Ensure that your device has a password set on the lock screen.
`Biometric authentication is not enabled`	Ensure that you can unlock your device with your fingerprint or face recognition.
`Disk is not encrypted`	Encrypt your device.
`Operating system is rooted or jailbroken`	Reset your device to remove any unofficial versions of the operating system.
`Device has hardware keystore`	You may be required to access protected resources from a device that has a built-in hardware-backed keystore. The only remediation for this error is to use a different device.

Your device isn't managed by your organization

Access to this resource is restricted to devices that your org manages. This device isn't currently enrolled in your org's device management, so Okta denied access.

You can't resolve this from the Device health page in Okta Verify, because device management is set up by your org rather than on your device.

To regain access, do one of the following:

Contact your org's help desk and ask to have this device enrolled in your org's device management.
Sign in to the app from a device that your org already manages.