Address lists in Commutation Server

  • Article
  • seven minutes to read

An accost list is a collection of mail-enabled recipient objects from Active Directory. Address lists are based on recipient filters, and are basically unchanged from Exchange 2010. You can filter by recipient type (for instance, mailboxes and mail contacts), recipient backdrop (for instance, Company or Land or Province), or both. Address lists aren't static; they're updated dynamically. When you create or modify recipients in your organization, they're automatically added to the advisable address lists. These are the unlike types of accost lists that are available:

  • Global address lists (GALs): The congenital-in GAL that'due south automatically created by Exchange includes every mail service-enabled object in the Agile Directory woods. You can create additional GALs to separate users past organisation or location, merely a user can only see and use one GAL.

  • Address lists: Address lists are subsets of recipients that are grouped together in one list, which makes them easier to observe by users. Commutation comes with several congenital-in address lists, and y'all can create more based on you lot organization's needs.

  • Offline accost books (OABs): OABs incorporate address lists and GALs. OABs are used by Outlook clients in buried Exchange fashion to provide local access to address lists and GALs for recipient wait-ups. For more data, run into Offline address books in Exchange Server.

Users in your organization employ address lists and the GAL to find recipients for email messages. Here'south an example of what accost lists look like in Outlook 2016:

Global Address List (GAL).

For procedures related to address lists, see Procedures for address lists in Exchange Server.

Recipient filters for address lists

Recipient filters identify the recipients that are included in address lists and GALs. In that location are ii basic options: precanned recipient filters and custom recipient filters. These are basically the same recipient filtering options that are used by dynamic distribution groups and electronic mail accost policies. The following table summarizes the differences between the two filtering methods.

Recipient filtering method User interface Filterable recipient properties Filter operators
Precanned recipient filters Address lists: Exchange admin center (EAC) and the Exchange Management Beat out

GALs: Exchange Management Shell only

 Limited to:
• Recipient type (All recipient types or any combination of user mailboxes, resource mailboxes, mail service contacts, mail users, and groups)
• Company
• Custom Attribute one to 15
• Department
• State or Province		 Property values require an exact match. Wildcards and partial matches aren't supported. For case, "Sales" doesn't match the value "Sales and Marketing".

Multiple values of the same property always use the or operator. For example, "Department equals Sales or Department equals Marketing".

Multiple backdrop always employ the and operator. For example, "Department equals Sales and Company equals Contoso".
Custom recipient filters Exchange Management Shell only You can use virtually any available recipient attributes. For more data, see Filterable Properties for the -RecipientFilter Parameter. Yous utilize OPATH filter syntax to specify any bachelor Windows PowerShell filter operators. Wildcards and partial matches are supported.

Notes:

  • Yous can't used precanned filters and customized filters at the same fourth dimension.

  • The recipient's location in Active Directory (the organizational unit or container) is available in both precanned and custom recipient filters.

  • If an address list uses custom recipient filters instead of precanned filters, you can see the address list in the EAC, but you can't alter or remove it by using the EAC.

  • You lot tin hibernate recipients from all address lists and GALs. For more information, run across Hibernate recipients from address lists.

Global accost lists

By default, a new installation of Exchange Server creates an GAL named Default Global Accost List that'due south the primary repository of all recipients in the Exchange organization. Typically, most organizations have but one GAL, because users tin simply see and use one GAL in Outlook and Outlook on the web (formerly known every bit Outlook Web App). Yous might need to create multiple GALs if you want to prevent groups of recipients from seeing each other (for example, you single Exchange organization contains two divide companies). If you program on creating boosted GALs, consider the following issues:

  • You can just use the Commutation Management Shell to create, change, remove, and update GALs.

  • The GAL that users see in Outlook and Outlook on the spider web is named Global Address Listing, even though the default GAL is named Default Global Address List, and any new GALs that y'all create will require a unique proper noun (users tin't tell which GAL that they're using by proper noun).

  • Users tin only see a GAL that they vest to (the recipient filter of the GAL includes them). If a user belongs to multiple GALs, they'll still see only ane GAL based on the following weather condition:

    • The user needs permissions to view the GAL. Y'all assign user permissions to GALs by using accost book policies (ABPs). For more information, see Accost volume policies in Exchange Server.

    • If a user is still eligible to see multiple GALs, only the largest GAL is used (the GAL that contains the almost recipients).

    • Each GAL needs a corresponding offline address volume (OAB) that includes the GAL. To create OABs, come across Use the Exchange Management Shell to create offline address books.

Default accost lists

By default, Exchange comes with five congenital-in address lists and one GAL. These address lists are described in the following table. Note that by default, system-related mailboxes like arbitration mailboxes and public folder mailboxes are hidden from accost lists.

Name Type Description Recipient filter used
All Contacts Address listing Includes all mail contacts in the organization. To learn more about postal service contacts, see Recipients. "Allonym -ne $nix -and (ObjectCategory -like 'person' -and ObjectClass -eq 'contact')"
All Distribution Lists Address list Includes all distribution groups and postal service-enabled security groups in the arrangement. To acquire more most mail-enabled groups, see Recipients. "Allonym -ne $nothing -and ObjectCategory -like 'grouping'"
All Rooms Address list Includes all room mailboxes. Equipment mailboxes aren't included. To learn more than about room and equipment (resource) mailboxes, come across Recipients. "Allonym -ne $null -and (RecipientDisplayType -eq 'ConferenceRoomMailbox' -or RecipientDisplayType -eq 'SyncedConferenceRoomMailbox')"
All Users Address list Includes all user mailboxes, linked mailboxes, remote mailboxes (Microsoft 365 or Role 365 mailboxes), shared mailboxes, room mailboxes, equipment mailboxes, and mail users in the organization. To acquire more virtually these recipient types, run into Recipients. "((Allonym -ne $null) -and (((((((ObjectCategory -like 'person') -and (ObjectClass -eq 'user') -and (-not(Database -ne $null)) -and (-not(ServerLegacyDN -ne $aught)))) -or (((ObjectCategory -like 'person') -and (ObjectClass -eq 'user') -and (((Database -ne $null) -or (ServerLegacyDN -ne $cipher))))))) -and (-not(RecipientTypeDetailsValue -eq 'GroupMailbox')))))"
Default Global Address List GAL Includes all mail service-enabled recipient objects in the organization (users, contacts, groups, dynamic distribution groups, and public folders. "((Alias -ne $null) -and (((ObjectClass -eq 'user') -or (ObjectClass -eq 'contact') -or (ObjectClass -eq 'msExchSystemMailbox') -or (ObjectClass -eq 'msExchDynamicDistributionList') -or (ObjectClass -eq 'group') -or (ObjectClass -eq 'publicFolder'))))"
Public Folders Accost list Includes all postal service-enabled public folders in your organization. Access permissions determine who can view and use public folders. For more data about public folders, see Public folders. "Alias -ne $zippo -and ObjectCategory -like 'publicFolder'"

Custom accost lists

An Commutation organization might contain thousands of recipients, so the built-in address lists could go quite large. To prevent this, you can create custom address lists to help users find what they're looking for.

For example, consider a company that has two large divisions in 1 Exchange organization:

  • Quaternary Java, which imports and sells coffee beans.

  • Contoso, Ltd, which underwrites insurance policies.

For virtually mean solar day-to-day activities, employees at Fourth Coffee don't communicate with employees at Contoso, Ltd. Therefore, to brand information technology easier for employees to discover recipients who exist only in their division, you tin create two new custom address lists: one for 4th Coffee and one for Contoso, Ltd. All the same, if an employee is unsure most where recipient exists, they can search in the GAL, which contains all recipients from both divisions.

You can also create address lists under other address lists. For example, you tin create an accost list that contains all recipients in Manchester, and yous tin can create another address list under Manchester named Sales that contains only sales people in the Manchester role. You lot can also movement address lists dorsum to the root, or under other address lists after you've created them. For more information, see Use the Exchange Management Vanquish to move accost lists.

All-time practices for creating additional address lists

Although address lists are useful tools for users, poorly planned address lists can cause frustration. To make sure that your address lists are practical for users, consider the following best practices:

  • Address lists should make it easier for users to find recipients.

  • Avoid creating and then many address lists that users can't tell which list to use.

  • Apply a naming convention and location hierarchy for your address lists so users tin can immediately tell what the list is for (which recipients are included in the list). If you accept difficulty naming your accost lists, create fewer lists and remind users that they can find anyone in your arrangement by using the GAL.

For detailed instructions nigh creating address lists in Exchange Server, see Create address lists.

Update address lists

After you create or modify an address list, you need to update the membership.

If the address list contains a large number of recipients (our recommendation is more than than 3000), you should use the Exchange Management Shell to update the address list (not the EAC). For more information, see Update address lists.

To update a GAL, you lot always need to use the Exchange Management Shell. For more data, run into Utilize the Commutation Management Beat out to update global address lists.