In preparation for onboarding a user, once the user is created and appropriate license is applied, now we can update the user specific mailbox settings like the users time zone, locale info, working hours etc.
In Day 16 we extended the base .Net Core console application to create a user by calling Azure AD. Today we'll extend the base console application to assign a user license in Office 365.
In Day 15 we registered an Azure Active Directory (Azure AD) application and created a console application using .Net Core. The application uses a client secret and the Microsoft Authentication Library (MSAL) to establish an authentication context with the Microsoft Graph API. Today we'll extend that application to create a user within Azure AD.
In Day 14 we discussed batch processing requests to Microsoft Graph requests. Today we'll take a big jump and build our first project in .Net Core that can make calls against Microsoft Graph.
In Day 13 we discussed calling Microsoft Graph with Postman. Today we'll look at the concept of batching that can help optimize your application by combining multiple Microsoft Graph queries.
In Day 11 we discussed Access Tokens which are crucial to make Microsoft Graph requests. Today we'll look at the various authentication scenarios that are possible when querying with Microsoft Graph.
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.