Hi Gaurav, currently the OIDC implementation for TOL is super limited to Google, so you are restricted to use SAML.

I haven't tested yet but really believe the same solution would work with Azure B2C on SAML protocol. I.e. probably adding the "Journey Framing" code under the sign up custom policy for SAML is all it takes.

But yeah, it needs to be tested. Let me know if you do test. You can follow my guide to get the lines of code for journey framing and this one to configure B2C with SAML: https://docs.microsoft.com/en-us/azure/active-directory-b2c/saml-service-provider?tabs=macos&pivots=b2c-custom-policy

Also, if your question relates to SSO for an embedded solution, consider using "Connected Apps" method instead, this is really the way forward.

Keep us posted on your findings!

Cheers,
Alex