microsoftgraph / microsoftgraph/msgraph-beta-sdk-dotnet

Managed Devices list request: filter by azureADDeviceId work incorrect when passing more then 1 azureADDeviceId

Open
#1,156 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:waiting-for-triage type:bug
Dominant language
C#
Stars
112
Forks
37
Avg merge
14h 57m
Merged PRs (30d)
3

Description

Describe the bug

I am trying to filter managedDevices by set of known azureADDeviceIds.

I send request https://graph.microsoft.com/beta/deviceManagement/managedDevices?$filter=azureADDeviceId eq 'id1' or azureADDeviceId eq 'id2' or azureADDeviceId eq 'id3'
The response contain only 1 device, with the first 'id1' azureADDeviceId, although other azureADDeviceIds also have related managed devices.

Furthermore, if I change filter order: azureADDeviceId eq 'id2' or azureADDeviceId eq 'id1' or azureADDeviceId eq 'id3', I receive managedDevice with the first 'id2' azureADDeviceId.

Image Image
Expected behavior

Several managed devices should be returned from the response, not only one device firth the first azureADDeviceId. Because all azureADDeviceIds are valid.

How to reproduce

Select several valid managedDevice.azureADDeviceId and try to filter

SDK Version

6.2.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output
Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the beta managedDevices request from the issue with multiple azureADDeviceId values and compare the response when the filter order changes. Inspect the SDK's request-building and filtering-related entry points only after confirming whether the behavior is exposed by the client; done means valid devices for all supplied IDs are returned or the issue is clearly identified as service-side.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.