In Day 10 we discussed Azure AD applications created through the V1 endpoint. Today we'll look at the permissions available and how to assign them to a user / Azure AD application.
In Day 9 we discussed how to register an Azure AD Application using V2 endpoint. Today we’ll look at registering an Azure AD Application using V1 endpoint that will be used to communicate with Microsoft Graph.
In Day 8 we discussed the authentication roadmap and access tokens which are crucial to make Microsoft Graph requests. Today we'll look at registering an Azure Active Directory (Azure AD) application that will be used to communicate with Microsoft Graph.
In Day 7 we discussed paging results for Microsoft Graph requests. Today we'll look at the current and future states of authenticating to Microsoft Graph, specifically obtaining access tokens.
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.
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.