Hi Felipe,
Here is a list of items which can cause token refresh:
- Conditional Access Policies:
- Implementing Conditional Access policies can influence token lifetimes. For instance, setting specific sign-in frequencies can require users to reauthenticate more often, affecting refresh token validity. learn.microsoft.com
- Security Defaults and Multi-Factor Authentication (MFA):
- Enabling security defaults or configuring MFA can impact token lifetimes. Settings like "remember multi-factor authentication on trusted devices" might cause tokens to expire sooner. learn.microsoft.com
- Application Type:
- Single-page applications (SPAs) have refresh tokens with a shorter lifespan, typically expiring after 24 hours, to enhance security. learn.microsoft.com
- Session Management Settings:
- Configuring session management settings, such as setting the
signInSessionsValidFromDateTime
property for a user, can invalidate existing refresh tokens, requiring users to sign in again. learn.microsoft.com
- Configuring session management settings, such as setting the
- Token Lifetime Policies:
- While not all aspects are configurable, certain token lifetime settings can be adjusted in Azure AD B2C to control how long tokens remain valid. learn.microsoft.com
hope that helps.