In Day 20 we configured the base .Net Core console application to utilize the device code authentication flow. Today we will continue with that path by extending this application to interact with Planner.
In Day 19 we assigned user permissions to an Office 365 Group (unified group) using Microsoft Graph requests. Today we'll introduce device code authentication and modify the .Net Core console application to utilize this authentication flow.
In this post we will show you how to add users to Office 365 unified groups. By virtue of being part of these groups, the user will get permissions to access not just the group but also the associated SharePoint Online site.
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.