¿Cómo elegir un proveedor de autenticación de Microsoft Graph?

How to choose a Microsoft Graph authentication provider?

To learn more, see Microsoft identity platform and OAuth 2.0 authorization code flow. Authorization code, client credential, and on-behalf-of OAuth flows require that you implement a custom authentication provider at this time. For more information, see Using a custom authentication provider.

In addition to that, note that the Microsoft Graph API has two endpoints right now, the beta endpoint and the V1 endpoint, do not confuse this with the v1 and v2 endpoints for Azure portal as the azure v1 and v2 endpoints are not related to the Microsoft Graph’s v1 and beta endpoints.

The first step to getting access to the Microsoft Graph REST API is to setup an AAD Application Registration. First we are going to want to create the AAD Application registrations in the portal. For this we will need to configure the application to be able to work with Postman so that we can make the call to the Microsoft Graph API.

The client credential flow enables service applications to run without user interaction. Access is based on the identity of the application. For more information, see Microsoft identity platform and the OAuth 2.0 client credentials flow.

Under Manage, select Certificates & secrets. Under Client secrets, select New client secret, enter a name, and then select Add. Record the secret value in a safe location for use in a later step. Under Manage, select API Permissions > Add a permission. Select Microsoft Graph. Select Application permissions.

The Application ID assigned by the Azure app registration portal. A Client (application) Secret, either a password or a public/private key pair (certificate). A Redirect URL for your service to receive token responses.