Home

Azure AD Connect and On-Prem ADFS federated with multiple partner organization

%3CLINGO-SUB%20id%3D%22lingo-sub-56161%22%20slang%3D%22en-US%22%3EAzure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56161%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EScenario%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EWe%20have%20an%20on-prem%20ADFS%20which%20is%20configured%20to%20federate%20with%20couple%20of%20partner%20organizations.%20The%20federated%20authentication%20with%20both%20our%20partners%20works%20well%20in%20On-Prem.%20Now%20we%20want%20to%20use%20this%20ADFS%20as%20authentication%20mechanism%20for%20Office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EQuestions%3A%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3COL%3E%3CLI%3EUsers%20of%20our%20AD%20will%20be%20synched%20with%20the%20help%20of%20Azure%20AD%20connect.%20Do%20we%20really%20need%20to%20sync%20the%20users%20of%20partner%20organization's%20AD%20as%20well%20to%20let%20them%20access%20our%20Office%20365%20tenant(shared%20SharePoint%20sites)%3F%20if%20it%20is%20required%2C%20what%20should%20be%20the%20approach%3F%3C%2FLI%3E%3CLI%3EIf%20partner-A%20and%20partner-B%20needs%20to%20access%20Office%20365%20SharePoint%20Site%2C%20what%20kind%20of%20license%20would%20they%20require%3F%20Can%20they%20be%20considered%20as%20external%20user%3F%20Would%20they%20require%20to%20have%20their%20own%20Office%20365%20tenant%3F%3C%2FLI%3E%3CLI%3EWe%20assume%20that%20once%20the%20ADFS%20federation%20with%20Office%20365%20configured%2C%20the%20authentication%20will%20happen%20in%20following%20way%3CUL%3E%3CLI%3EPartner-A%20user%20tries%20to%20access%20SharePoint%20Online%20site%20URL%20that%20i've%20shared%3C%2FLI%3E%3CLI%3EOffice%20365%20will%20route%20the%20request%20to%20on-prem%20ADFS%20of%20my%20organization%3C%2FLI%3E%3CLI%3EMy%20on-prem%20ADFS%20will%20then%20pass%20the%20request%20to%20Partner-A%20ADFS%3C%2FLI%3E%3CLI%3EThe%20user%20will%20get%20authenticated%20with%20Partner-A%20ADFS%20and%20returned%20to%20My%20ADFS%20with%20the%20token%3C%2FLI%3E%3CLI%3EMy%20ADFS%20will%20replace%20Partner-A's%20token%20with%20its%20own%20token%20and%20send%20back%20the%20user%20to%20Office%20365%3C%2FLI%3E%3CLI%3EUser%20successfully%20accesses%20the%20shared%20SharePoint%20Online%20site%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Is%20this%20the%20correct%20understanding%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-56161%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132721%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132721%22%20slang%3D%22en-US%22%3EI%20mean%20federation%20as%20defined%2C%20which%20is%20joining%20two%20distinct%20or%20disconnected%20directories.%20The%20purpose%20is%20so%20you%20do%20not%20have%20to%20create%20and%20manage%20users%20in%20the%20other%20directory.%20The%20user%20account%20exists%20and%20is%20maintained%20in%20one%20directory%2C%20but%20can%20access%20resources%20trusted%20by%20another%20directory.%20You%20can%20setup%20a%20B2B%20tenant%20if%20you'd%20like%2C%20but%20that%20is%20just%20one%20way%20to%20accomplish%20it.%20You%20are%20correct%20that%20a%20user%20object%20has%20to%20exist%20in%20the%20Azure%20AD%20tenant%20to%20login%20to%20O365%2C%20that%20is%20what%20the%20invite%20as%20external%20user%20from%20another%20Azure%20AD%20tenant%20option%20does.%20This%20only%20makes%20the%20user%20available%20to%20be%20granted%20access%20to%20applications%20under%20the%20tenant%2C%20but%20their%20user%20account%20still%20exists%20and%20is%20maintained%20in%20the%20other%20tenant.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132588%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132588%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20term%20federation%20means%20many%20things%20in%20Office%20365%2FAzure%20AD%2C%20so%20I%20think%20we%20are%20simply%20talking%20about%20different%20things%20here.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20I%20meant%20by%20federation%20is%20that%20you%20either%20create%20a%20new%20federated%20domain%20to%20Office%20365%20or%20convert%20an%20existing%20one%20to%20federated%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3E%23%20Create%20a%20new%20federated%20domain%0ANew-MsolFederatedDomain%20-DomainName%20mydomain.com%0A%23%20Convert%20a%20domain%20to%20federated%0AConvert-MsolDomainToFederated%20-DomainName%20mydomain.com%3C%2FPRE%3E%0A%3CP%3EThis%20naturally%20requires%20that%20the%20domain%20is%20registered%20to%20that%20Office%20365%20tenant.%20Moreover%2C%20what%20the%20federation%20does%20is%20that%20it%20only%20authenticates%20the%20user.%20To%20log%20in%20and%20use%20Office%20365%20services%2C%20there%20must%20be%20a%20matching%20user%20object%20in%20the%20Office%20365%20tenant.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20suppose%20by%20federation%20you%20meant%20something%20like%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-b2b-what-is-azure-ad-b2b%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20B2B%20Collaboration%3CFONT%3E%3F%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132578%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132578%22%20slang%3D%22en-US%22%3EI%20think%20you%20might%20be%20mixing%20up%20federation%20with%20sync.%20%20You%20can't%20sync%20a%20domain%20to%20more%20than%20one%20tenant%20but%20you%20can%20absolutely%20federate%20with%20other%20directories.%20%20If%20they%20are%20in%20another%20Azure%20tenant%2C%20you%20have%20two%20options%2C%20invite%20them%20as%20external%20users%20to%20your%20tenant%20or%20setup%20federation%20between%20two%20tenants%20using%20custom%20policies.%20%20If%20you%20don't%20mind%20external%20users%20in%20your%20directory%2C%20then%20inviting%20them%20as%20external%20users%20is%20by%20far%20the%20easiest%20of%20the%20two%20options.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132569%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132569%22%20slang%3D%22en-US%22%3EGood%20point%2C%20it%20would%20be%20better%20from%20the%20management%20point-of-view%20to%20have%20all%20users%20in%20Azure%20AD%20in%20partner's%20own%20tenant.%3CBR%20%2F%3E%3CBR%20%2F%3EHowever%2C%20there%20is%20no%20need%20to%20federate%20anything%2C%20Office%20365%20takes%20care%20of%20authentication.%20Besides%2C%20if%20the%20partner%20is%20already%20using%20Office%20365%2C%20their%20domain%20is%20registered%20to%20their%20tenant%20it%20cannot%20be%20federated%20to%20other%20tenants.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-131111%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131111%22%20slang%3D%22en-US%22%3EI'd%20assume%20they%20wouldn't%20want%20them%20using%20a%20Microsoft%20account%20for%20account%20management%20purposes.%20%20You%20can%20signup%20for%20a%20Microsoft%20account%20with%20any%20email%20address.%20%20If%20they%20do%20it%20with%20their%20work%20email%20address%2C%20two%20things%20would%20happen%20that%20would%20be%20issues%20with%20a%20lot%20of%20organizations.%20%201.%20It%20would%20be%20a%20separate%20account%20with%20a%20separate%20password.%20%202.%20%20If%20they%20left%20the%20partner%20company%2C%20they%20would%20still%20be%20able%20to%20login%20with%20the%20Microsoft%20account%20after%20the%20company%20partner%20account%20is%20deactivated%20or%20password%20changed.%20%20%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20partner%20would%20need%20their%20own%20Azure%20AD%20with%20on-prem%20accounts%20synced%20or%20their%20own%20ADFS%20and%20you%20would%20federate%20your%20Azure%20AD%20with%20that.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-129518%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-129518%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20sync%20your%20users%20to%20Azure%20AD%20and%20simply%20invite%20your%20partners'%20users%20to%20SharePoint%20sites.%20If%20done%20so%2C%20the%20answers%20are%20as%20follows%3A%3C%2FP%3E%3COL%3E%3CLI%3ENo%2C%20you%20do%20not%20need%20to%20sync%20them%20to%20Azure%20AD.%3C%2FLI%3E%3CLI%3ENo%20need%20for%20any%20license%2C%20just%20invite%20them%20as%20external%20users.%20To%20login%2C%20your%20partners'%20invited%20users%20do%20require%20either%20a%20Microsoft%20Account%20(outlook.com%2C%20hotmail.com%2C%20etc.)%20or%20Azure%20AD%20account%20(Office%20365%20etc.).%3C%2FLI%3E%3CLI%3EThere%20is%20no%20need%20to%20any%20AD%20FS%20scenario%20here.%20When%20partners%20are%20external%20users%2C%20Office%20365%20will%20handle%20all%20the%20authentication%3C%2FLI%3E%3C%2FOL%3E%3CP%3EFor%20security%20reasons%2C%20I%20suggest%20that%20you%20run%20the%20following%20PowerShell%20command%20in%20your%20tenant.%20It%20forces%20the%20external%20users%20to%20login%20with%20the%20same%20email%20address%20the%20invitation%20was%20sent%20to.%3C%2FP%3E%3CPRE%3ESet-SPOTenant%20-RequireAcceptingAccountMatchInvitedAccount%20%24true%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-129024%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-129024%22%20slang%3D%22en-US%22%3E%3CP%3EEasiest%20implementation%20would%20be%20your%20partners%20also%20sync%20their%20users%20to%20Azure%20AD.%26nbsp%3B%20Then%20you%20can%20invite%20them%20as%20a%20guest%20to%20your%20tenant%20and%26nbsp%3Bthen%26nbsp%3Bthey%20will%20be%20available%20to%20add%20a%20users%20in%20Office%20365.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77613%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77613%22%20slang%3D%22en-US%22%3Ehi%2C%3CBR%20%2F%3E%3CBR%20%2F%3E1%2F%20In%20sharepoint%2C%20you%20can%20add%20a%20external%20user%2C%20the%20user%20of%20partner%20organisation%20not%20need%20sync%20to%20let%20them%20access.%20But%20is%20just%20for%20sharing%20document.%3CBR%20%2F%3E%3CBR%20%2F%3E2%2F%20if%20you%20use%20the%201%20solution%2C%20not%20need%20licence.%3CBR%20%2F%3E%3CBR%20%2F%3E3%2F%20For%20give%20access%20at%20partner%20org%2C%20you%20have%20few%20solutions%2C%3CBR%20%2F%3E%3CBR%20%2F%3E-%20You%20can%20use%20Azure%20BtoB%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-b2b-what-is-azure-ad-b2b%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-b2b-what-is-azure-ad-b2b%3C%2FA%3E)%3CBR%20%2F%3E-%20you%20can%20federated%20their%20on-premise%20AD%20with%20your%20tenant%20(%20it's%20very%20intrusive%20for%20your%20organisation)%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77302%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77302%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2237%22%20target%3D%22_blank%22%3E%40Atul%20Moghe%3C%2FA%3E%26nbsp%3BDid%20you%20get%20any%20solution%20for%20this%20scenario.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56493%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56493%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20there%20is%20no%20article%20of%20that%2C%20but%20you%20can%20only%20validate%20your%20domains%20on%20Office%20365%20not%20your%20partner%20and%20that%20is%20a%20requisite%20of%20ADFS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBellow%20is%20an%20article%20of%20implementing%20ADFS%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Frmilne%2F2014%2F04%2F28%2Fhow-to-install-adfs-2012-r2-for-office-365%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Frmilne%2F2014%2F04%2F28%2Fhow-to-install-adfs-2012-r2-for-office-365%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56467%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56467%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Nuno%20for%20your%20quick%20response!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20point%20me%20to%20an%20article%20where%20this%20or%20similar%20kind%20of%20scenario%20is%20explained%20in%20detail%3F%20I%20couldn't%20find%20any%20good%20resource%2Fdocumentation%20around%20this%20scenario%20and%20i%20believe%20this%20must%20be%20quite%20common%20requirement%20for%20many%20big%20enterprises.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56171%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Connect%20and%20On-Prem%20ADFS%20federated%20with%20multiple%20partner%20organization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56171%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Atul%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20not%20use%20your%20ADFS%20to%20authenticate%20partner%20users%20because%20you%20will%20need%20to%20validate%20their%20domain%20on%20your%20Office%20365%20as%20an%20accepted%20and%20validated%20domain.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Atul Moghe
Occasional Contributor

Scenario:

We have an on-prem ADFS which is configured to federate with couple of partner organizations. The federated authentication with both our partners works well in On-Prem. Now we want to use this ADFS as authentication mechanism for Office 365.

 

Questions: 

  1. Users of our AD will be synched with the help of Azure AD connect. Do we really need to sync the users of partner organization's AD as well to let them access our Office 365 tenant(shared SharePoint sites)? if it is required, what should be the approach?
  2. If partner-A and partner-B needs to access Office 365 SharePoint Site, what kind of license would they require? Can they be considered as external user? Would they require to have their own Office 365 tenant?
  3. We assume that once the ADFS federation with Office 365 configured, the authentication will happen in following way
    • Partner-A user tries to access SharePoint Online site URL that i've shared
    • Office 365 will route the request to on-prem ADFS of my organization
    • My on-prem ADFS will then pass the request to Partner-A ADFS
    • The user will get authenticated with Partner-A ADFS and returned to My ADFS with the token
    • My ADFS will replace Partner-A's token with its own token and send back the user to Office 365
    • User successfully accesses the shared SharePoint Online site

            Is this the correct understanding?

12 Replies

Hi Atul,

 

You should not use your ADFS to authenticate partner users because you will need to validate their domain on your Office 365 as an accepted and validated domain.

Thanks Nuno for your quick response!

 

Can you point me to an article where this or similar kind of scenario is explained in detail? I couldn't find any good resource/documentation around this scenario and i believe this must be quite common requirement for many big enterprises.

I think there is no article of that, but you can only validate your domains on Office 365 not your partner and that is a requisite of ADFS.

 

Bellow is an article of implementing ADFS https://blogs.technet.microsoft.com/rmilne/2014/04/28/how-to-install-adfs-2012-r2-for-office-365/

@Atul Moghe Did you get any solution for this scenario. 

hi,

1/ In sharepoint, you can add a external user, the user of partner organisation not need sync to let them access. But is just for sharing document.

2/ if you use the 1 solution, not need licence.

3/ For give access at partner org, you have few solutions,

- You can use Azure BtoB (https://docs.microsoft.com/en-us/azure/active-directory/active-directory-b2b-what-is-azure-ad-b2b)
- you can federated their on-premise AD with your tenant ( it's very intrusive for your organisation)



Easiest implementation would be your partners also sync their users to Azure AD.  Then you can invite them as a guest to your tenant and then they will be available to add a users in Office 365.

Hi,

 

I would sync your users to Azure AD and simply invite your partners' users to SharePoint sites. If done so, the answers are as follows:

  1. No, you do not need to sync them to Azure AD.
  2. No need for any license, just invite them as external users. To login, your partners' invited users do require either a Microsoft Account (outlook.com, hotmail.com, etc.) or Azure AD account (Office 365 etc.).
  3. There is no need to any AD FS scenario here. When partners are external users, Office 365 will handle all the authentication

For security reasons, I suggest that you run the following PowerShell command in your tenant. It forces the external users to login with the same email address the invitation was sent to.

Set-SPOTenant -RequireAcceptingAccountMatchInvitedAccount $true
I'd assume they wouldn't want them using a Microsoft account for account management purposes. You can signup for a Microsoft account with any email address. If they do it with their work email address, two things would happen that would be issues with a lot of organizations. 1. It would be a separate account with a separate password. 2. If they left the partner company, they would still be able to login with the Microsoft account after the company partner account is deactivated or password changed.

The partner would need their own Azure AD with on-prem accounts synced or their own ADFS and you would federate your Azure AD with that.
Good point, it would be better from the management point-of-view to have all users in Azure AD in partner's own tenant.

However, there is no need to federate anything, Office 365 takes care of authentication. Besides, if the partner is already using Office 365, their domain is registered to their tenant it cannot be federated to other tenants.
I think you might be mixing up federation with sync. You can't sync a domain to more than one tenant but you can absolutely federate with other directories. If they are in another Azure tenant, you have two options, invite them as external users to your tenant or setup federation between two tenants using custom policies. If you don't mind external users in your directory, then inviting them as external users is by far the easiest of the two options.

The term federation means many things in Office 365/Azure AD, so I think we are simply talking about different things here.

 

What I meant by federation is that you either create a new federated domain to Office 365 or convert an existing one to federated:

 

# Create a new federated domain
New-MsolFederatedDomain -DomainName mydomain.com
# Convert a domain to federated
Convert-MsolDomainToFederated -DomainName mydomain.com

This naturally requires that the domain is registered to that Office 365 tenant. Moreover, what the federation does is that it only authenticates the user. To log in and use Office 365 services, there must be a matching user object in the Office 365 tenant. 

 

 

I suppose by federation you meant something like Azure B2B Collaboration?

I mean federation as defined, which is joining two distinct or disconnected directories. The purpose is so you do not have to create and manage users in the other directory. The user account exists and is maintained in one directory, but can access resources trusted by another directory. You can setup a B2B tenant if you'd like, but that is just one way to accomplish it. You are correct that a user object has to exist in the Azure AD tenant to login to O365, that is what the invite as external user from another Azure AD tenant option does. This only makes the user available to be granted access to applications under the tenant, but their user account still exists and is maintained in the other tenant.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies