When testing Authentication Policies that require a managed device, users may encounter the following generic error instead of specific remediation instructions (for example, "Enroll in MDM").
Access Denied
This article explains the logic behind Okta's display or hiding of management remediation signals.
- Management attestation
- Okta Identity Engine (OIE)
- iOS
- macOS
- Windows
- Android
Okta only triggers remediation messaging when it detects a viable path for the user to resolve the requirement. If the specific platform (iOS, Android, macOS, or Windows) is missing or disabled under Device Integrations, Okta views the "Managed" requirement as an impossible condition. Because the system does not know which MDM vendor (for example, Intune, Jamf) is responsible for the attestation, it returns a generic error rather than providing instructions to a non-existent destination.
To ensure remediation instructions are visible to the end-user, verify the following configuration:
- Check Device Integrations: Navigate to Security > Device Integrations > Endpoint Management. Confirm that a valid configuration exists and is Active for the platform being tested.
- Verify Authentication Policy: Ensure the rule explicitly requires a "Managed" device and that no higher-priority rule is overriding the logic.
- Update Okta Verify: The Management Attestation signal relies on the handshake between the local Okta Verify client and the MDM certificate; ensure the app is up to date on the test device.
In this table, a "Platform Config" refers to an active MDM (Mobile Device Management) integration in the Okta Admin Console. For Okta to display specific remediation instructions, a corresponding record must exist under Security > Device Integrations > Endpoint Management for the operating system (iOS, Android, macOS, or Windows) in use.
If this configuration is missing or inactive, Okta cannot identify the remediation path (for example, whether to point the user toward Jamf, Intune, or another provider) and will default to a generic "Access Denied" message.
Summary of Behaviors
| Scenario | Resulting Behavior |
| Rule requires "Managed" + Platform Config exists | Okta shows remediation instructions (for example, "Install Company Portal"). |
| Rule requires "Managed" + No Platform Config exists | Okta treats the requirement as a hard "Deny" (Generic Error). |
