This makes it possible to lock down any given user to viewing contact details only of the employees they are supposed to see, creating an impression that the user is in a different Exchange / Office 365 organization. It was possible to do this in on-prem Exchange 2010, Exchange 2007, and even as far back as Exchange 2003.
But it is a somewhat new concept in Exchange Online and Office 365, and there isn’t a great deal of information on it out there yet.
Outlook 2016 gal not updating exchange 2016 Income from adult chat room
This next batch of commands requires only Exchange Online powershell session (see step 2 above).
This last command gets object IDs of all user objects from Office 365 directory where Office attribute is set to “Flexecom”, then uses this object ID list to query Exchange Online mailboxes where External Directory Object ID attribute matches one of the object IDs from Office 365, then finally pipes the mailboxes into a commandlet that performs address book assignments. but it really isn’t all that complicated once you do it one or two times, and it does work great!
First, get the guid of the Office 365 group that was used for address book filtering: Guids will be displayed in the left column. Substitute “GUID” with the actual GUID, you don’t need to use single or double quotes around the GUID for this to work.
This command grabs object IDs of all members of our test group, gets their associated mailboxes, and pipes them into commandlet that assigns the new address book policy.
Also, and this is important, check to make sure that you have either an Enterprise (E) or an Educational (A) Office 365 subscription level.