Devices inventory
To view information about devices that are registered in your organization, go to in the Admin Console.
Devices are registered in the Okta Universal Directory and listed in the inventory through several methods. Okta Verify enrollment is the most common, but it isn't the only one. See How the Devices inventory is populated. The device details presented in the inventory are updated each time users authenticate successfully with Okta FastPass.
Device Visibility
Early Access release
When you enable the Device Visibility feature, the device detail pages for macOS and Windows use a four-tab layout: Accounts, Configurations, Signals, and Identifiers.
If you don't have the Device Visibility feature enabled, then macOS and Windows devices show the existing single-page view.
iOS and Android devices continue to use the existing single-page view layout to show device details, regardless of whether you enable the Device Visibility feature. See View device details.
| Device info |
Select the device name to view details. This also shows the user name and the email address of the user that is enrolled on the device. If several user profiles are associated with the device, this shows the total number of profiles. |
| Enrolled By |
The authenticator used to enroll the device. |
| Platform | This shows the device operating system (OS) and the device identifier. The device identifier for iOS or macOS is the Unique Device Identifier (UDID). For Windows, the device identifier is the Security Identifier (SID) attribute. |
| Status | This shows the device status: Active, Suspended, or Deactivated.
This also shows the profile status: Managed or Not managed A user can have multiple user profiles on a device. For example, a business profile could be used to access restricted company apps, while a personal profile can be used to access personal files. If a device has a mix of Managed and Not managed profiles, this shows the total count of each profile status. Depending on the status of the device, you can activate, suspend, unsuspend, deactivate, or delete a device. |
Search for a specific device
You can search devices by display name, serial number, International Mobile Equipment Identity (IMEI), Mobile Equipment Identifier (MEID), Unique Device ID (UDID), or Security Identifier (SID).
<UDID> is a predefined macro provided by the MDM provider. If this value can't be retrieved, Okta Verify reports empty values. See Managed app configurations for iOS devices.
Filter by device criteria
You can filter the list of devices displayed by the following criteria:
| Enrolled By | View devices according to which authenticator was used for enrollment. |
| Platform | View devices by their OS. Options: Any OS, Android , iOS , macOS , Windows |
| Access status | Options: Any, Created, Active, Suspended, Deactivated |
| Device management | Options: Any, Managed, Not managed
|
| Security signals | Options: Any, Jailbroken or rooted, Disabled screen lock |
Factory resets and duplicate device records
Okta Verify for iOS stores an Okta device ID in the local keychain.
If a user performs a factory reset, the device is restored to its factory settings. All the user's data is deleted from the device, including the Okta device ID from the local keychain.
If a user re-enrolls in Okta Verify after a factory reset, this creates a new Okta device ID. Okta Verify doesn't recover the original Okta device ID.
In this case, the Devices page () displays two device records for the same device. You can delete the duplicate device record.
How the Devices inventory is populated
A device appears in the inventory when it becomes known to Okta Universal Directory. Devices become known through several methods, each with its own configuration. If a device that you expect to see is missing, confirm that at least one of these methods is configured and active for it.
| Method | Description |
|---|---|
| Okta Verify enrollment | A user enrolls a device in Okta Verify. This registers the device and enables Okta FastPass. |
| Custom authenticator enrollment | A device enrolls through a custom authenticator built with the Devices SDK. See Configure a custom authenticator. |
| Device registration | A certificate deployed to the device lets it communicate with the Okta backend. This method applies to Device Access and the Okta Verify Device Posture Sensor Mode feature. See Device Access certificates and Device Posture Sensor Mode. |