AADSTS700082: The refresh token has expired due to inactivity
A cached refresh token wasn’t used for 90 days (the inactivity limit) and is no longer valid.
Seen on:
Azure
Meaning
Long-unused CLI sessions, scripts or apps holding refresh tokens must sign in again interactively. Automated jobs should use service principals or managed identity instead of user tokens.
Common causes
- Refresh token unused for 90+ days
- Automation relying on a user’s cached tokens
⚡ Quick fix
- Sign in again (az login / Connect-AzAccount)
- Switch automation to a service principal or managed identity
Detailed fix by platform
Azure CLI
- bash
az logout az login
How to diagnose
- Age — Last use of the cached account
- Automation — Using user credentials?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Azure
- AADSTS50076 Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
- AuthorizationPermissionMismatch Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
- AADSTS700016 Azure AD (Entra ID): AADSTS700016 Application not found in the directory
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 8 Oct 2026