Default Global Address List Restritions

%3CLINGO-SUB%20id%3D%22lingo-sub-2464692%22%20slang%3D%22en-US%22%3EDefault%20Global%20Address%20List%20Restritions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2464692%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Team%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20requirement%20to%20accomplish%20the%20following%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Prevent%20a%20list%20of%20about%20250%20contacts%20from%20Showing%20up%20in%20the%20Default%20Global%20Address%20list%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20we%20can%20do%20this%20with%20GAL%20Segmentation%20but%20we%20have%20a%20very%20large%20messaging%20environment%20all%20in%20exchange%20online%2C%20hybrid.%20In%20this%20case%20the%20contacts%20in%20question%20are%20all%20Sync'd%20to%20the%20cloud.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20would%20like%20to%20avoid%20using%20ABP%20because%20of%20the%20setup%20requirements%20(having%20to%20create%202%20separate%20address%20lists%2C%20OAB%2C%20Email%20Routing%20agent%20etc).%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20ideas%20on%20how%20we%20might%20do%20this%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20this%20were%20on-prem%20we%20could%20simply%20filter%20the%20default%20Global%20Address%20list%2C%20and%20exclude%20those%20contacts%20based%20on%20populating%20an%20attribute%20or%20something%20similar%2C%20but%20we%20are%20not%20able%20to%20do%20so%20using%20EXO.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERobert%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2464692%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2464928%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Global%20Address%20List%20Restritions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2464928%22%20slang%3D%22en-US%22%3EWouldn't%20hiding%20them%20from%20the%20GAL%20(toggle%20-HiddenFromAddressListsEnabled%20flag)%20help%20here%3F%20It%20will%20affect%20other%20ALs%20of%20course%2C%20but%20as%20far%20simplicity%20goes%2C%20nothing%20beats%20that%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Contributor

Hey Team, 

 

We have a requirement to accomplish the following:

 

"Prevent a list of about 250 contacts from Showing up in the Default Global Address list"

 

I know we can do this with GAL Segmentation but we have a very large messaging environment all in exchange online, hybrid. In this case the contacts in question are all Sync'd to the cloud. 

We would like to avoid using ABP because of the setup requirements (having to create 2 separate address lists, OAB, Email Routing agent etc). 

Any ideas on how we might do this? 

 

If this were on-prem we could simply filter the default Global Address list, and exclude those contacts based on populating an attribute or something similar, but we are not able to do so using EXO. 

 

Thanks, 

 

Robert 

 

 

3 Replies
Wouldn't hiding them from the GAL (toggle -HiddenFromAddressListsEnabled flag) help here? It will affect other ALs of course, but as far simplicity goes, nothing beats that :)

@Vasil Michev 

 

Thanks Vasil. That's the problem, we don't want them hidden from all address lists, just from the Default GAL. 

 

The contacts need to be visible to each other, but not to the greater global address list, if that makes any sense. 

The hard way it is then :)