Machine-to-machine (M2M) authorization (RFC 6749 §4.4). There is no human user and no browser redirect. The client application authenticates directly with the identity provider using its own credentials to obtain an access token.
Unlike user-centric flows that require an authorization code dance, the client credentials grant is a streamlined, single-legged protocol:
POST to the IdP's token endpoint with
grant_type=client_credentials, client_id,
client_secret, and the desired scope.
access_token (typically valid for 1 hour).
id_token asserts the identity of a human who logged in; because no user is present, an ID token is not issued. Similarly, refresh tokens are not provided because the machine client can simply request a fresh access token whenever needed using its stored secret.
Enter your machine client credentials. No redirect URI or user interaction is required.
https://graph.microsoft.com/.default for Entra ID).This is the raw HTTP POST that will be sent to the token endpoint. Notice the form-urlencoded parameters proving the application's identity.
// Fill in config above to preview
The backend confirms the exact HTTP POST headers and body sent over the wire to the IdP.
// Will appear after executing the request
The IdP returns a JSON payload containing the access_token, its token type (Bearer), and lifetime in seconds (expires_in).
// Awaiting request…
Explore the claims inside the access token. Notice that the sub (subject) refers to the client application itself, and the roles claim reflects the application permissions approved by the tenant admin.