You can use these credentials to authenticate the following nodes:
Microsoft includes an Entra ID free plan when you create a Microsoft Azure account.
Refer to Microsoft Entra ID’s documentation for more information about the service.
For self-hosted users, there are two main steps to configure OAuth2 from scratch:
Follow the detailed instructions for each step below. For more detail on the Microsoft OAuth2 web flow, refer to Microsoft authentication and authorization basics.
Register an application with the Microsoft Identity Platform:
Refer to Register an application with the Microsoft Identity Platform for more information.
With your application created, generate a client secret for it:
Refer to Microsoft’s Add credentials for more information on adding a client secret.
Microsoft Entra ID credentials use the following scopes by default:
openid
offline_access
AccessReview.ReadWrite.All
Directory.ReadWrite.All
NetworkAccessPolicy.ReadWrite.All
DelegatedAdminRelationship.ReadWrite.All
EntitlementManagement.ReadWrite.All
User.ReadWrite.All
Directory.AccessAsUser.All
Sites.FullControl.All
GroupMember.ReadWrite.All
To select different scopes for your credentials, enable the Custom Scopes slider and edit the Enabled Scopes list. Keep in mind that some features may not work as expected with more restrictive scopes.
Here are the known common errors and issues with Microsoft Entra credentials.
When attempting to add credentials for a Microsoft360 or Microsoft Entra account, users may see a message when following the procedure that this action requires admin approval.
This message will appear when the account attempting to grant permissions for the credential is managed by a Microsoft Entra. In order to issue the credential, the administrator account needs to grant permission to the user (or “tenant”) for that application.
The procedure for this is covered in the Microsoft Entra documentation.