| title | List registeredUsers |
|---|---|
| description | Retrieve a list of users that are registered users of the device. |
| author | myra-ramdenbourg |
| ms.localizationpriority | medium |
| ms.subservice | entra-directory-management |
| doc_type | apiPageType |
| ms.date | 10/25/2024 |
Namespace: microsoft.graph
Retrieve a list of users that are registered users of the device.
For cloud joined devices and registered personal devices, registered users are set to the same value as registered owners at the time of registration.
[!INCLUDE national-cloud-support]
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
[!INCLUDE permissions-table]
[!INCLUDE limited-info]
Important
In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported Microsoft Entra role or a custom role with a supported role permission. The following least privileged roles are supported for this operation.
- Directory Readers
- Global Reader
- Intune Administrator
- Windows 365 Administrator
You can address the device using either its id or deviceId.
GET /devices/{id}/registeredUsers
GET /devices(deviceId='{deviceId}')/registeredUsersThis method supports the $select, $search, $count, and $filter OData query parameters to help customize the response. $search is supported on the displayName and description properties only.
The use of query parameters with this API is supported only with advanced query parameters. For more information, see Advanced query capabilities on directory objects.
| Name | Type | Description |
|---|---|---|
| Authorization | string | Bearer {token}. Required. Learn more about authentication and authorization. |
Don't supply a request body for this method.
If successful, this method returns a 200 OK response code and collection of directoryObject objects in the response body.
The following example shows a request.
GET https://graph.microsoft.com/v1.0/devices/{id}/registeredUsers
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response. Note: The response object shown here might be shortened for readability.
HTTP/1.1 200 OK
Content-type: application/json
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#directoryObjects",
"value": [
{
"@odata.type": "#microsoft.graph.user",
"@odata.id": "https://graph.microsoft.com/v2/72f988bf-86f1-41af-91ab-2d7cd011db47/directoryObjects/96a5df40-617b-4450-8b7a-1dc18b872d8f/Microsoft.DirectoryServices.User",
"id": "96a5df40-617b-4450-8b7a-1dc18b872d8f",
"displayName": "Alex Wilber",
"mail": "AlexW@contoso.com",
"mailNickname": "AlexW@contoso.com"
}
]
}