Managing external identities to enable secure access for partners, customers, and other non-employees
Hello Gurpreet0101Singh-9444,
Thank you for Reaching Out Microsoft Q&A Platform.
You do not need to create separate custom policies for each client. Instead, you can parameterize a single policy using techniques like:
- Custom Attributes
- Tag users with a
clientIdororganizationId. - Use this attribute to drive conditional logic in the policy. https://learn.microsoft.com/en-us/azure/active-directory-b2c/user-profile-attributes
- Claims-Based Branching
- Use
<Predicates>and<Preconditions>to branch logic based onclientId. - Example: If
clientId == "ClientA", call REST API A; else call REST API B. https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-policies-series-overview
- REST API Integration
- Call a REST API to fetch client-specific logic or branding dynamically.
- This keeps your policy clean and offloads logic to your backend. https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-policies-series-overview
- Custom Domains and UI Branding
- Use query strings or domain names to load client-specific branding. https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-domain?pivots=b2c-user-flow
You can also found similar Question reference:
https://learn.microsoft.com/en-us/answers/questions/2262067/managing-identity-with-azure-entra-for-multiple-cl
- Multitenant Architecture
If clients are in separate tenants, consider using federation or multi-tenant sign-in.
Hope this helps to resolve your issue.
Regards,
Monalisha