Nov 09 2019 08:34 AM
Nov 09 2019 08:34 AM
Let's say we have an organization on-prem with AD (company.com) and all the usual services.
This company has a lot of clients who need access to some applications such as SAAS that can be implemented in Azure. Let's say company's clients include several hundreds companies and its corresponding users. So each client, would have 5-10 users who need access to the applications provided by company.com.
Such external, outside users can and probably should, be maintained in a separate directory (clients.com). Let's say this is going to be an active directory which exists on-prem and maintains one-way trust with company.com AD environment. Or completely separated, not really that significantly important I think.
Company.com maintains their own Azure tenant. Also, for the clients, they can setup a separate tenant or create a separate directory in their own Azure tenant and sync users from clients.com. Each external company, would be represented by their own OU with users for such company synced from on-prem clients.com AD directory to the: either same tenant as comany.com under a different directory or synced from clients.com AD to the clients.onmicrosoft.com tenant. Multiple "sync profiles" can be created within the AADConnect tool to sync specific OU to the specific directory in the tenant, which basically would results to something like this - email@example.com, firstname.lastname@example.org, etc.
I hope this makes sense.
Is that something practical and realistic?
Are there any better or more functional approaches for such design?
Thank you for your time and feedback.
Nov 13 2019 05:12 PM
@VickVega, your ideia might work but not as you expect. Look, there's some supported topologies that you can deploy using Azure AD Connect and that will enable your customer to have their credentials (and password) synchronized.
Have you read this doc already? https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies
Since your customer's clients must connect using their own credentials, I think is worthy to take a look at that documentation.
Also, creating a structure like *@client1.clients.onmicrosoft.com is currently not supported, since you will only have access to clients.onmicrosoft.com domain. What you can do instead is using a custom domain like client1.clients.com and then assign the users this domain as their UPN like email@example.com. The problem with that is that you must have a separate domain exclusively to do this and you must be sure that you won't have any conflicts with users credentials (this might be a real headache).
Last thing is: is the application ready to be integrated with social accounts? would the application be compatible with Facebook, Google, etc? If so, you could try using Azure B2C for your customer to solve this.
Hope you find this useful.