microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Inability to retrieve user accounts from EntraID through Webjob\FunctionApp -TrackingID#2406031420000580
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Good morning,
this ticket has been opened to report an issue about the Graph API graphServiceClient.Users.Request: this method, used to get all the enabled users (filter "accountEnabled eq true") in EntraID of the tenant, reports zero users found (see "First call graph - users found: 0" in attached log screenshot, webjob_log) for most of the times.
The Graph API is in a function App metod called by a scheduled webjob. Sometimes the method seems to work correctly especially if it is executed manually.
In the attached screenshot Graph_Code it is reported the Graph API used call (Graph v4.54).
I have also attached the permission assigned to the logic App (screenshot Permission)
The same code is already used for a similar application for another tenant without the issue.
I have also executed the same Graph method in the tenant through Graph Explorer (https://graph.microsoft.com/v1.0/users?$count=true&$filter=(accountEnabled eq true) ) with no issue.
We have already opened a ticket to Azure ( TrackingID#2406031420000580) to analize this issue and it was requested to open also a parallel ticket on Github.
Could you verify why the Graph method graphServiceClient.Users.Request could return zero users found without generating a more specific exceptions?
Regards,
Andrea
Attachment:
-Permission:
-Graph_Code:
-webjob_log:
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.
Research direction
Start by reviewing the Graph_Code attachment and the webjob_log showing the first call returning zero users, then compare the scheduled WebJob/Function App request with the successful Graph Explorer query. Done means identifying a reproducible cause or documenting why graphServiceClient.Users.Request can return an empty result without a specific exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- api, backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100