devices expand=registeredUsers does only return the id
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start by reproducing the request through GraphServiceClient and DevicesRequestBuilder with expand=['registeredUsers'], then compare the SDK response with the Graph Explorer response. Trace how registeredUsers is represented and populated in the returned device objects; done means expanded users expose properties beyond id, matching the service response.
Written by the indexing model from the issue text.
Description
Describe the bug
Using the devices endpoint in graph and the parameter expand=registeredUsers is supposed to return (all) values for all registered users.
Each registered user is supposed to be of type #microsoft.graph.user
Using graph-explorer, this works, i.e. https://graph.microsoft.com/beta//devices?$expand=registeredUsers
will contain a list of microsoft.graph.user objects in the registeredUsers property, where each user has attributes like mail, imAddresses etc filled.
Using the SDK only the id property for the microsoft.graph.user object is filled, i.e. all other properties are None or empty collections.
Is this a bug or something on my end I don't understand?
my calling code (broken down):
request_config = DevicesRequestBuilder.DevicesRequestBuilderGetQueryParameters(
top=20,
expand=['registeredUsers']
)
self._event_loop.run_until_complete(self._graph_service.devices.get(request_config))
where _event_loop == asyncio.get_event_loop()
and _graph_service == GraphServiceClient
Expected behavior
A list of devices is returned, where registered Users of type #microsoft.graph.user in the device's registeredUsers property have more properties filled than just the ID
How to reproduce
See description
SDK Version
1.56.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
No response
Configuration
- OS: MacOS 26.3.1
- Arch: Apple Silicon
- Python: 3.13.7 (venv)
Other information
No response
- Dominant language
- Python
- Stars
- 44
- Forks
- 16
- Avg merge
- 20h 39m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-beta-sdk-python
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
type:bug type:investigation
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoftgraph/msgraph-beta-sdk-python#1033 · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
microsoftgraph/msgraph-beta-sdk-python#987 · 2 comments ·
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoftgraph/msgraph-beta-sdk-python
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100