Fixing AADSTS700082: refresh tokens expiring after 12 hours in Azure Entra External ID
The article discusses an issue with refresh tokens expiring after 12 hours in Azure Entra External ID, affecting user experience in a mobile app. The problem was traced to a configuration setting related to Sign-in Frequency rather than a bug in the refresh token system. The author provides insights into the symptoms, what was ruled out, and the eventual resolution of the issue.
- ▪Users of a mobile app experienced unexpected logouts due to refresh tokens expiring after 12 hours of inactivity.
- ▪The issue was linked to the Sign-in Frequency setting in Azure Entra External ID, not a bug in the refresh token mechanism.
- ▪The article outlines the troubleshooting process and confirms that the expected 90-day refresh token was being capped at 12 hours.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/samvanhoutte/fixing-aadsts700082-refresh-tokens-expiring-after-12-hours-in-azure-entra-external-id-1mj0 |
| Publication time | Wed, 20 May 2026 08:21:52 +0000 |
| Retrieval time | 2026-05-20T08:35:01.090Z |
| Last seen | 2026-05-20T08:35:01.090Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | YdpkjUGY3Omk |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1282259) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Sam Vanhoutte Posted on May 20 Fixing AADSTS700082: refresh tokens expiring after 12 hours in Azure Entra External ID #azure #oauth Fixing AADSTS700082: refresh tokens expiring after 12 hours in Azure Entra External ID At libelo we use Azure Entra External ID (CIAM) (Customer Identity and Access Management) as the identity provider for our React Native mobile app.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
