In Day 6 we finished discussing many of the query parameters available for Microsoft Graph requests. Today we'll look at the concept of paging results when there are more records than can be returned in a single response.
In Day 5 we began discussing the query parameters available for Microsoft Graph requests. Today we'll continue looking at query parameters available for requests against Microsoft Graph.
In day 4 we discussed the syntax for Microsoft Graph requests. Today we'll begin looking at query parameters available for requests against Microsoft Graph.
In Day 3 we discussed the Graph Explorer. Today we'll inspect the syntax for Microsoft Graph requests.
While it may be great to read about Microsoft Graph and all that it can do it is equally important to see it in action. Thankfully, Microsoft Graph product group has made it extremely easy to test out queries and view examples against a demo tenant or live on your own tenant.
What started as an Office specific set of APIs (read here for more on the history) has now expanded into Microsoft Graph which covers APIs across multiple services including Office 365, Azure AD, Enterprise Mobility and Security, Windows 10, and Education.
Microsoft Graph unifies API access to the services in the Microsoft 365 suite. Developers can now consume data through a single public endpoint (https://graph.microsoft.com) – using simple REST calls or with an SDK available on just about any platform.
Throughout the month of November 2018, we are publishing daily articles (30 total) that aim to introduce developers to Microsoft Graph. We’ll have content that covers 0-level to 200-level topics. Each post should take you 5-15 mins to read and try out the sample exercises. No prior knowledge of Microsoft Graph is required.
A quick reference to the Microsoft Graph on-demand sessions at Ignite 2018
Release notes for Microsoft Graph SDKs including GA and preview releases for public and beta APIs.
