Thanks for posting your query on Microsoft Q&A. From above description I could understand that you need to configured 2 application with same URL, where users from Tenant T1 should be able to access data from application hosted in Tenant T1.
And users from tenant T2 should be able to access application hosted on B2C tenant T3.
Please do let me know in the comments if this is not correct, else try following below suggestion:
- Create an application in T1 with
Accounts in this organizational directory only (T1 only - Single tenant) in Supported account types
- For 2nd application in B2C tenant T3 follow Set up sign-in for a specific Azure Active Directory organization (T2 in this case) in Azure Active Directory B2C
- Here while Configuring Azure AD as an identity provider select directory name of T2 (abc.onmicrosoft.com) to replace tenant below:
https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration
If you have 1 application hosted in B2C tenant, then
- You need to integrate AAD of Tenant 1 with B2C as an IDP, this would allow users from T1 to authenticate with T3 B2C tenant as federated users.
- Similarly you must allow local account signup. This would be used by users from T2 to register as local user, in this case all the authentication would be taken care by Azure AD B2C tenant T3.
The users will be registered as consumer accounts( local and federated B2C accounts), none of the above steps would create guest accounts in B2C tenant.
A local account refers to an account that is created in your Azure AD B2C directory when a user signs up for your application or an admin creates the account. Usernames and passwords are stored locally and Azure AD B2C serves as the identity provider for local accounts.
You can configure Azure AD B2C to allow users to sign in to your application with credentials from external social or enterprise identity providers (IdPs). Azure AD B2C supports many external identity providers and any identity provider that supports OAuth 1.0, OAuth 2.0, OpenID Connect, and SAML protocols.
With external identity provider federation, you can offer your consumers the ability to sign in with their existing social or enterprise accounts, without having to create a new account just for your application.
On the sign-up or sign-in page, Azure AD B2C presents a list of external identity providers the user can choose for sign-in. Once they select one of the external identity providers, they're redirected to the selected provider's website to complete the sign-in process. After the user successfully signs in, they're returned to Azure AD B2C for authentication of the account in your application.
Please do let me know if you have any further queries.
Thanks,
Akshay Kaushik
Please "Accept the answer" (Yes), and share your feedback if the suggestion answers you’re your query. This will help us and others in the community as well.