This video offers a general layout of this course, and what it teaches you.
- [Instructor] Now that I've introduced you to what Microsoft Graph is and what I intend to cover in this course, let me now talk about how I have chosen to structure this course. We will first start by writing a simple web application protected by Azure AD. Now, technically speaking, this has got nothing to do with Microsoft Graph, and I will not even be calling Microsoft Graph in this application. But this is an important stepping stone for us to understand what it means to have an Azure AD, what it means to register your application in Azure AD, and then later on down the road, we'll use the same web application to create APIs inside it, which can then tap into Microsoft Graph, or this application can coexist side by side with Office 365.
And then once we understand the concepts of registration as it comes to native applications inside of Azure AD, we'll expand our knowledge, and we'll take our knowledge to creating WPF applications or Windows Forms applications, and there we'll understand the concepts and importance of token management. So you'll see that there are two kinds of tokens that I'll be talking about. Access token, refresh token, and what are the uses and importance of each, how do manage them? That's what I'll be talking about here.
Let's be honest, these day a lot of applications we write are actually web applications. So it makes sense to understand how a web application can call Microsoft Graph as well. And there are two different scenarios here. Scenario number one is where only the application's identity is all you need. And there are certain kinds of API's that require you to work under application identity. And I'll be introducing those to you in this module. And then there is a concept of delegated user identity where the identity of the user matters when the web application calls Microsoft Graph.
So imagine that I have a custom web application and let's say as an example we're executing Search against Office 365. The search is also exposed as a Microsoft Graph API. But search results need to be trimmed to the user executing the search. So how do we forward the user's identity in the case of a web application calling Microsoft Graph? And then finally, I'll be talking about a Daemon Calling Graph Resources. This is an interesting example where you have a process running and that process is able to call Microsoft Graph but it doesn't give you the opportunity to provide a user name or password to authenticate.
And in all of these concepts, I'll be mentioning things like ADAL. I'll be mentioning things like Refresh Token and Access Token and I'll be explaining you the purposes of these. I'll be explaining things like a single tenant application. Or a multi-tenant application and way more. So buckle up and let's get started.
- What is Microsoft Graph?
- Registering a web application in Azure AD
- Adding authentication logic and authentication UI
- Native applications calling Graph
- Reviewing scenarios where web apps involving Graph are useful
- Web applications with application identity and delegated identity calling Graph
- Daemons calling Graph