What are the ways to include user requirements (user subscriptions or a list of roles as an example) in the token before its release in Azure AD B2C, provided that the claims are stored somewhere on your own server (not available in B2C)? The goal is to have claims in the token in order to avoid an additional round trip to the store for each request.
Research on this topic led me to the following paths:
source
share