Philosophical question here as we have just started the road to Azure as IDP.
I work for an event organisation and we have (some) onprem AD's and a massive number of external users. Some thousands of them are direct contractors for larger events, some hundreds of them are working as team extensions, again some ten thousands to a couple
hundred thousands are external stakeholders that might do business with us at some point. Today we have a bunch of externals administered in our AD as "fake employees" as they needed access to company resources.
We would want to give them a single Company Identity to work with a single account across the IT landscape. Book example of AAD so far.
We already have an AADC syncing our company.com onprem AD into Azure.
I've been weighing in some options on how to best approach all these externals and I'd love to hear some input to these. Technically these are all doable (I believe), I'd like to hear your experience or "best practices" with these, if you will.
0) Treat everyone internal: same AD (different OU's), same AAD, same Displayname
- Externals grouped in a different OU in the same AD domain
- Sync all employees + the external companies as needed to the AAD
- John.Doe@company.com and the external Jane.Doe@company.com has virtually no difference, but in the onprem
This is basically the concept we want to get away from, but there might be good reasons to keep it.
1) Same AAD, same domain, different Displaynames.
- Put everyone in the company.com AD + sync'ed AAD,
- make the company name part of the display name like "Jane Doe (OTHERCOMPANY)".
This way all employees would know that she is an external, but all 3rd parties to the company would just see a company.com email (at first).
2) Same AAD, different domains
- Put everyone in the company.com AD + sync'd AAD, plus add custom domains and cloud-born identities to the AAD
- We're going to have "John.Doe@company.com" and "Jane.Doe@affiliatecompany.com" in the same AAD
Advantage: same AAD simplicity
Disadvantage: everyone knows that Jane is not an employee of Company, someone needs to admin the externals along with the core employees (admin segregation needs to be planned well)
3) Different AADs, different domains
- Put only employees in the AD
- Put all externals into an "company-ext" AAD and invite them to the company AAD as guests as needed
- Jane.Doe@company-ext.com will still look like an external address
Advantage: different AD allows for proper segregation of admin tasks
Disadvantage: introduces federation complexity (will everything work properly?)
Or any combination of the above? I've seen 0) and 1) working, I've yet to experience 2 and 3.