Refresh tokens are invalidated after change to Custom Policy in B2C

Håvard Olsen 0 Reputation points
2024-10-30T09:58:03.6733333+00:00

We manage a Azure AD B2C instance, with a custom policy for login.

Sometimes when we are deploying changes to the policy all users are asked to login again. It seems that the refresh tokens are being invalidated.

This does not happen every time, so my question is if there is any documentation about what type of change causes this to happen?

Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
2,926 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Raja Pothuraju 8,095 Reputation points Microsoft Vendor
    2024-10-30T14:16:04.32+00:00

    Hello @Håvard Olsen,

    Thank you for posting your query on Microsoft Q&A.

    Based on your description, I understand that whenever changes are made to a custom policy, users are prompted to re-login, even if they have an active session. You mentioned that this only happens occasionally when deploying changes to a custom policy in Azure AD B2C.

    Since this behavior is somewhat unusual, could you let me know how long it takes for active sessions to be revoked or invalidated after deploying updates to the custom policy in Azure AD B2C?

    Which files are you modifying when this behavior occurs?

    Please share this information to help us better understand the scenario. In the meantime, I'll check internally to see if there are any known cases of similar behavior.

    Thanks,
    Raja Pothuraju.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.