Instead, the permission scopes introduced only cover the basic scenarios: access only your own resources, access resources shared with you, access all resources. As it tries to cover quite diverse set of resources, the permissions model used by the Graph doesn’t go into the peculiarities of each individual workload. Here lies one of the problems when using the Graph. For authentication to happen, the app must be recognized by the Microsoft Identity platform, in other words an application registration must be performed by the developer first. To control which actions a given application can perform, the developer describes the permissions needed by the app and you, or an admin in the tenant, has to grant (“ consent” to) the permissions. The authentication process is performed against the Microsoft Identity platform by means of obtaining tokens, which are then presented to the workload against which you want to perform a given operation. You can run those in the context of a given user, or as a background service. To give you the TL DR version – the Graph allows you to perform various actions against different resources in Office 365, such as creating a message, deleting a file, or accessing a report. Microsoft has published extensive documentation on all these topics and this article is a good starting point. It’s beyond the scope of the article to give you a complete introduction, but in order to better understand the examples shown here, you will be required to have at least a basic understanding of the concepts behind OAuth, OIDC, application registration, permission roles and scopes, consent, access tokens and so on. Switching to the Graph comes with somewhat of a learning curve. While EWS will continue working for the foreseeable future, going forward you will have to switch to the Graph, so understanding how to control it is vital.Ī n ot so short introduction to the Graph API Microsoft has already announced plans to stop any feature development for the EWS API and focus on the Graph instead. The Microsoft Graph has been around for a while now and is slowly turning into the de-facto standard API for any Office 365 developer, including those focused on Exchange Online. Application Access Policies in Exchange Online
0 kommentar(er)
