Identity APIs in Microsoft Graph: Advanced Queries deep dive
summary
Explains that Microsoft Graph routes identity reads either to the legacy Rest Directory Service or a new Advanced Query service backed by an index store synced by a sync engine, and that queries requiring counts or search must include ConsistencyLevel=eventual and $count=true to hit the index. Shows tokenized search behavior, filter+orderby only on listed properties, transitive counts/expansions (level=max), batching requiring eventual header per subrequest, and current B2C and skip limitations.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:38Advanced Queries Architecture
- 4:21Why the magic parameters?
- 21:20Documentation and Sample references
related talks
12mIntegrating Microsoft Identit(ies) into your applications
55mMastering the Microsoft Graph PowerShell
41mTales of OAuth2/OIDC in the wild
26mAzure Managed Identities: Why are you still using anything else?!?
18mAPI Governance in the age of AI
50mManaging Enterprise and Consumer Identity with Azure Active Directory
38mAll You Need is Guest
11mMicrosoft Graph (/v1.0)