In Day 24 we concluded configuring implicit flow authentication on a single-page application.  Today we'll extend the base console application to create a OneNote notebook, section, and page.
In todays post we will see at four samples covering Azure AD v1 and v2 that uses ADAL and MSAL along with TypeScript, JQuery, React and Webpack.
Today and tomorrow, you'll learn to do much the same thing directly from a web browser in a Single Page Application. Today's article will walk you through updating your app registrations (for v1 and v2) so they'll work from the browser; tomorrow we'll dig into the code.
In day 21 we added plans, buckets, and tasks to Planner. Today we will be building on the .Net Core sample application started in Day 15 to add support for the device and app management functionality offered by Intune.
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.
The Microsoft Graph APIs are a game-changer for devs, and in this blog you’ll see how you can build an unparalleled Teams experience.
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.
