Hello @Patil, Sagar ,
For configuring tenant wide SSO via user flow https://learn.microsoft.com/en-us/azure/active-directory-b2c/session-behavior?pivots=b2c-user-flow#configure-the-user-flow have "SSO Configuration" set to "Tenant" and "Enable keep me signed in session" to "Yes"
For Custom policy as per https://learn.microsoft.com/en-us/azure/active-directory-b2c/session-behavior?pivots=b2c-custom-policy#configure-the-custom-policy in SignUpOrSignin.xml Change the value of the Scope attribute to "Tenant" Application, or Policy. As per https://learn.microsoft.com/en-us/azure/active-directory-b2c/cookie-definitions#cookies, the cookie "x-ms-cpim-sso:{Id}" must be set"persistent" to Enable Keep me signed in.
However, SSO will not work by mixing userflows and custom policies. It is because the custom policy is using different technical profile names, or session management names compared to the user flow behind the scenes.
Do let me know if you have any queries in the comments section.
Thanks,
Akshay Kaushik
Please "Accept the answer" and "Upvote" if the above-mentioned suggestion works as per your business need. This will help us and others in the community as well.