Module 2: Microsoft Graph Permissions and Consent | Microsoft Graph Fundamentals for Beginners

Key Takeaways

to develop a customer application that retrieves microsoft 365 data you need to understand how permissions and consent work in microsoft graph you want to make the right choices about what data your application can and can't access of course for example if you want to show a signed in users upcoming meetings you'll want your application to have permission to access their calendar data from microsoft 365. now applications request permission to access specific microsoft 365 resources via microsoft graph as i just talked with the previous scenario of accessing a calendar these requests can be made up front when the application is registered or dynamically when the application is running when an application requests permission a user or administrator must consent to the permission before microsoft graph will authorize requests so here are a few concepts to understand when your application needs to interact with microsoft graph we'll talk about each of these in turn first off you need to understand microsoft graph permissions or scopes you'll see that permissions actually contain scopes and we'll talk more about that coming up shortly you also need to know about permission types and there's two key types that i'll talk about in just a moment as well and then finally you need to know about access tokens now we've seen some examples of how access tokens are kind of like a specialized key that gets you in certain doors but you're going to see shortly that permissions play a big role with access tokens so let's go ahead and start things off by talking about microsoft graph permissions or scopes