Forum Discussion
Scoped Directory Search requires Information Barrier Segments?
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.
VasilMichev 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.
https://docs.microsoft.com/en-us/MicrosoftTeams/teams-scoped-directory-search#:~:text=Microsoft%20Teams%20scoped%20directory%20search%20allows%20organizations%20to,Information%20Barrier%20policies%20to%20support%20these%20custom%20views.
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 WMLouis
- 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-round-up/ba-p/284335
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).
