JWT Decoder
A JSON Web Token (JWT) is the access token that many Power Platform connections use to prove who is calling and what they are allowed to do. When a flow gets a 401 or 403 error from Microsoft Graph, SharePoint or your own API, the answer is usually inside the token: the wrong audience, a missing role or an expired time. This JWT decoder shows the header, the payload and the expiry date of a token in your browser, so you can check those claims in seconds.
Also known as: decode jwt, jwt parser, json web token decoder, jwt debugger.
This tool decodes only. It does not verify the signature.
Your data is processed locally in your browser and is not uploaded to our servers.
Features
- Header and payload as formatted JSON
- Expiry and issue times in UTC
- Local processing, nothing uploaded
How to use the JWT Decoder
- Get the token. For example, call the token endpoint from an HTTP action and copy the access_token value from the run history.
- Paste the token into the box. A JWT has three parts separated by dots.
- Click Decode JWT.
- Read the header, the payload and the times. The exp claim is when the token expires, iat is when it was issued and nbf is when it becomes valid. They are shown as UTC dates.
- Compare the claims with what your API expects, then fix the app registration, scope or permission.
Real-world use case: fixing 401 and 403 errors in flows and custom connectors
Say a flow uses an HTTP action with a Microsoft Entra ID app registration to read SharePoint sites through Microsoft Graph. The call returns 403 Forbidden even though the app seems to have permission. Decode the access token and look at three claims. The aud claim should be the API you are calling, such as https://graph.microsoft.com. The roles claim (for application permissions) or the scp claim (for delegated permissions) should list the permission you need, for example Sites.Read.All. And exp should be in the future.
If roles is empty, the permission was probably added to the app registration but admin consent was never granted. If aud points to a different resource, the token was requested for the wrong scope or resource. Both are quick fixes once you can see the claims, and both are hard to guess from an error message alone.
Custom connectors with OAuth 2.0 work the same way. When a connector call fails after it worked yesterday, decode a fresh token and check exp and the tenant ID in the tid claim. Access tokens are usually valid for roughly an hour, so a long-running flow that reuses an old token can fail halfway through.
One caution matters here. A decoder only reads the token. It does not prove that the token is genuine, because that needs the signing key and must happen on the server. Treat tokens like passwords: decode them for debugging, and never paste a live production token into a ticket or a chat.
Example input and output
Input: a sample token (not a real one)
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJodHRwczovL2dyYXBoLm1pY3Jvc29mdC5jb20iLCJpc3MiOiJodHRwczovL3N0cy53aW5kb3dzLm5ldC8wMDAwMDAwMC0wMDAwLTAwMDAtMDAwMC0wMDAwMDAwMDAwMDAvIiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjE3MDAwMDM2MDAsInJvbGVzIjpbIlNpdGVzLlJlYWQuQWxsIl0sImFwcGlkIjoiMTExMTExMTEtMTExMS0xMTExLTExMTEtMTExMTExMTExMTExIn0.c2FtcGxlLXNpZ25hdHVyZQ
What you should check in the decoded result
HEADER
{ "alg": "RS256", "typ": "JWT" }
PAYLOAD (excerpt)
"aud": "https://graph.microsoft.com" -> the API being called
"roles": ["Sites.Read.All"] -> the permission that was granted
TIMES (UTC)
iat: 2023-11-14T22:13:20.000Z
exp: 2023-11-14T23:13:20.000Z -> one hour laterFrequently asked questions
What is a JWT and what does it contain?
A JWT is a signed token with three Base64URL parts: a header with the algorithm, a payload with claims such as aud, exp and roles, and a signature. Anyone who holds the token can read the payload, so it must not contain secrets.
How do I check when a JWT expires?
Decode the token and read the exp claim, a Unix timestamp in seconds. This decoder converts it to a UTC date for you. If the time is in the past, request a new token.
Does this tool verify the signature?
No. It decodes only. Verifying a signature needs the issuer's public key, and that check belongs on your server or in the service that receives the token.
Why use PowerApps Ninja?
Access tokens are credentials. Some online JWT tools send what you paste to a server, which is a real risk with live tokens. PowerApps Ninja decodes the token inside your browser and never uploads it, and there is no sign-up. The page is written for Power Platform scenarios such as Graph calls from flows and custom connectors.