SOLVED
Home

Scoped Directory Not Working

%3CLINGO-SUB%20id%3D%22lingo-sub-808755%22%20slang%3D%22en-US%22%3ERe%3A%20Scoped%20Directory%20Not%20Working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-808755%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20when%20I%20played%20with%20it%20few%20months%20back%20I%20was%20able%20to%20see%20%22suggested%22%20people%20outside%20of%20the%20scope%2C%20and%20some%20other%20glitches.%20Since%20then%20we've%20received%20the%20Information%20barriers%20feature%20though%2C%20so%20try%20that%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Finformation-barriers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Finformation-barriers%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-808802%22%20slang%3D%22en-US%22%3ERe%3A%20Scoped%20Directory%20Not%20Working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-808802%22%20slang%3D%22en-US%22%3EInformation%20barriers%20may%20be%20an%20option.%20Yet%20I%20also%20think%20you%20have%20to%20consider%20that%20this%20functionality%20is%20in%20Office%20365%20E5%20or%20the%20standalone%20advanced%20compliance%20SKU%20which%20could%20mean%20a%20lot%20more%20expense%20for%20the%20business%20if%20you%20haven%E2%80%99t%20got%20that%20SKU.%20It%E2%80%99s%20not%20necessarily%20an%20easy%20conversation%20as%20it%20works%20as%20you%20need%20for%20a%20proportion%20of%20users.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20personally%20open%20a%20ticket%20to%20Microsoft%20and%20get%20them%20to%20look%20into%20the%20consistency%20issue.%20It%20ought%20to%20be%20consistent%20across%20all%20users.%20If%20Microsoft%20can%E2%80%99t%20remediate%20it%20then%20I%20would%20consider%20alternate%20options.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-808812%22%20slang%3D%22en-US%22%3ERe%3A%20Scoped%20Directory%20Not%20Working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-808812%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%20I'll%20open%20a%20ticket%20with%20MS%20to%20see%20what%20they%20think%2C%20hopefully%20they%20have%20an%20answer%20as%20I%20don't%20see%20management%20wanting%20to%20spend%20more%20money%20just%20to%20fix%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-808187%22%20slang%3D%22en-US%22%3EScoped%20Directory%20Not%20Working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-808187%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20setup%20an%20address%20book%20policy%20in%20exchange%20and%20have%20scoped%20directory%20on%20in%20teams.%20The%20ABP%20is%20working%20great%20in%20outlook%20only%20showing%20who%20we%20wanted%20but%20in%20Teams%20it%20is%20inconsistent.%20For%20some%20users%20it%20works%20great%20but%20for%20others%20they%20see%20certain%20users%20that%20shouldn't%20be%20in%20search.%20And%20even%20the%20users%20showing%20in%20search%20incorrectly%20is%20inconsistent%2C%20for%20one%20user%20they%20see%20contact%20A%26nbsp%3B%20but%20not%20contact%20B%20and%20another%20user%20will%20see%20contact%20B%20but%20not%20contact%20A%20even%20though%20nobody%20should%20see%20contact%20A%20or%20B.%3C%2FP%3E%3CP%3EThis%20issue%20is%20on%20both%20the%20desktop%20version%20of%20teams%20and%20the%20browser%20one.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20anything%20else%20in%20the%20back-end%20I%20need%20to%20do%20to%20get%20this%20to%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-808187%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGAL%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehelp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Escoped%20search%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
DM213
New Contributor

Hi,

I have setup an address book policy in exchange and have scoped directory on in teams. The ABP is working great in outlook only showing who we wanted but in Teams it is inconsistent. For some users it works great but for others they see certain users that shouldn't be in search. And even the users showing in search incorrectly is inconsistent, for one user they see contact A  but not contact B and another user will see contact B but not contact A even though nobody should see contact A or B.

This issue is on both the desktop version of teams and the browser one.

 

Is there anything else in the back-end I need to do to get this to work?

3 Replies

Yeah, when I played with it few months back I was able to see "suggested" people outside of the scope, and some other glitches. Since then we've received the Information barriers feature though, so try that: https://docs.microsoft.com/en-us/office365/securitycompliance/information-barriers

Solution
Information barriers may be an option. Yet I also think you have to consider that this functionality is in Office 365 E5 or the standalone advanced compliance SKU which could mean a lot more expense for the business if you haven’t got that SKU. It’s not necessarily an easy conversation as it works as you need for a proportion of users.

I would personally open a ticket to Microsoft and get them to look into the consistency issue. It ought to be consistent across all users. If Microsoft can’t remediate it then I would consider alternate options.

Best, Chris

@Christopher Hoard @Vasil Michev 

Thanks, I'll open a ticket with MS to see what they think, hopefully they have an answer as I don't see management wanting to spend more money just to fix this issue.

Related Conversations