Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

Scoped Directory Search requires Information Barrier Segments?

%3CLINGO-SUB%20id%3D%22lingo-sub-1886165%22%20slang%3D%22en-US%22%3EScoped%20Directory%20Search%20requires%20Information%20Barrier%20Segments%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1886165%22%20slang%3D%22en-US%22%3E%3CDIV%3EWe'd%20like%20to%20use%20Scoped%20directory%20search%20in%20Teams%20and%20all%20the%20documentation%20seems%20to%20suggest%20that%20we%20can't%20use%20just%20Address%20Book%20polices%20to%20accomplish%20this.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ESome%20confusion%20is%20caused%20because%20the%20documentation%20states%20that%20we'll%20also%20need%20to%20setup%20%22Information%20Barriers%20Policies%22%20to%20segment%20the%20users%20first.%26nbsp%3B%20(which%20also%20require%20A5s)%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EHas%20anyone%20used%20scoped%20directory%20search%3F%20How%20did%20you%20do%20it%3F%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1886165%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1887210%22%20slang%3D%22en-US%22%3ERe%3A%20Scoped%20Directory%20Search%20requires%20Information%20Barrier%20Segments%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1887210%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20last%20played%20with%20it%2C%20it%20worked%20just%20fine%20with%20Address%20Book%20Policies.%20I%20suppose%20Microsoft%20will%20replace%20those%20with%20Information%20Barriers%20at%20some%20point%2C%20but%20afaik%20they%20still%20dont%20support%20Exchange.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor
We'd like to use Scoped directory search in Teams and all the documentation seems to suggest that we can't use just Address Book polices to accomplish this. 
 
Some confusion is caused because the documentation states that we'll also need to setup "Information Barriers Policies" to segment the users first.  (which also require A5s)
 
Has anyone used scoped directory search? How did you do it? 
 
4 Replies

When I last played with it, it worked just fine with Address Book Policies. I suppose Microsoft will replace those with Information Barriers at some point, but afaik they still dont support Exchange.

@Vasil Michev   Thank you for the reply.  That's how I've always known them to work.  

 

Microsoft's current documentation states that only information barrier policies are used and seems to suggest that information barrier segments are required.  It's odd.

 

Teams scoped directory search 

Info barriers does use address book policies under the hood however to set it up it requires you to remove any existing address book policies first @Louis Hubert 

That may be true, but my question is, regarding Scoped Directory search and its requirements.

The documentation now states that you need Information barriers for scoped directory search, which is a change.

https://techcommunity.microsoft.com/t5/microsoft-teams-blog/what-s-new-in-microsoft-teams-november-r...

I've also found this post from the introduction of Scoped Directory Search. It states that:

You can now leverage Exchange address book policies to create virtual boundaries within your organization and control how users find and communicate with each other in Teams. This is useful if you manage an organization that has multiple entities within a single tenant, or if you manage a school and want to limit chat between faculty and students within the same class or grade.

and

To use scoped directory search for your organization in Teams, first create address book policies via the Exchange Admin Center (EAC) and then enable scoped directory search in Teams via the Microsoft Teams & Skype for Business Admin Center (Org-wide settings > Teams settings).