Home

Domain based open federation

%3CLINGO-SUB%20id%3D%22lingo-sub-1205614%22%20slang%3D%22en-US%22%3EDomain%20based%20open%20federation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205614%22%20slang%3D%22en-US%22%3E%3CP%3EI%20want%20to%20allow%20open%20federation%20for%20users%20on%20one%20domain%2C%20but%20restrict%20federation%20for%20users%20on%20another%20domain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20the%20only%20way%20to%20do%20this%20today%20is%20to%20move%20users%20to%20separate%20Office%20365%20tenants%2C%20which%20I%20don't%20think%20is%20a%20great%20solution%20especially%20when%20there's%20a%20bunch%20of%20stakeholder%20systems%20in%20place.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20plan%20to%20allow%20this%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1205614%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChat%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFederation%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205789%22%20slang%3D%22en-US%22%3ERe%3A%20Domain%20based%20open%20federation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205789%22%20slang%3D%22en-US%22%3EI%20don%E2%80%99t%20see%20any%20documentation%20that%20supports%20this%20as%20a%20possibility.%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20may%20separate%20your%20users%20from%20each%20other%20with%20Information%20Barriers%20but%20both%20groups%20would%20still%20have%20the%20same%20federation%20access.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1212527%22%20slang%3D%22en-US%22%3ERe%3A%20Domain%20based%20open%20federation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1212527%22%20slang%3D%22en-US%22%3EIf%20you%20mean%202%20login%20domains%20and%20you%20have%20the%20same%20org%20tenant%2C%20you%20can%20utilize%20Information%20Barriers%20as%20Louis%20was%20referencing%20to%20put%20barriers%20between%20certain%20domains.%20Take%20a%20look%20here.%20It%20does%20require%20additional%20licensing%20etc.%20however%20so%20keep%20that%20in%20mind.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Finformation-barriers-in-teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Finformation-barriers-in-teams%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I want to allow open federation for users on one domain, but restrict federation for users on another domain.

 

It seems the only way to do this today is to move users to separate Office 365 tenants, which I don't think is a great solution especially when there's a bunch of stakeholder systems in place.

 

Is there any plan to allow this??

2 Replies
Highlighted
I don’t see any documentation that supports this as a possibility.

You may separate your users from each other with Information Barriers but both groups would still have the same federation access.
Highlighted
If you mean 2 login domains and you have the same org tenant, you can utilize Information Barriers as Louis was referencing to put barriers between certain domains. Take a look here. It does require additional licensing etc. however so keep that in mind. https://docs.microsoft.com/en-us/microsoftteams/information-barriers-in-teams