Powerful Guide to Address Book and Address Book Policies in Exchange Online

Address Book and Address Book Policies play a critical role in how users in Microsoft Exchange Online discover, view, and interact with organizational contacts. When designed correctly, they provide clarity, security, and control. When mismanaged, they can expose unnecessary information and cause confusion across departments.

In modern enterprises—especially those using multi‑tenant, hybrid, or shared Microsoft 365 environments—administrators must ensure that users only see relevant people and resources. This is where Address Book and Address Book Policies become powerful tools.

Address Book and Address Book Policies
Address Book and Address Book Policies

This comprehensive guide explains what they are, how they differ, how they function together, and why every Exchange administrator should master them.

What Is an Address Book in Exchange Online?

An Address Book in Exchange Online is a filtered list of directory objects such as:

  • Users
  • Mail contacts
  • Mail users
  • Groups
  • Rooms and equipment mailboxes

Unlike the default Global Address List (GAL), custom address books allow administrators to define which objects appear, based on filters like department, company, or recipient type.

Key Purpose of Address Books

The primary purpose of an address book is to:

  • Control visibility of recipients
  • Reduce directory clutter
  • Improve user experience in Outlook and Outlook on the web
  • Support organizational separation in shared tenants

By design, address books are server‑side objects created and managed through Exchange Online PowerShell.

Types of Address Books

Exchange Online supports several types of address books that work together:

1. Global Address List (GAL)

The Global Address List is the default master address book. Every mailbox must be able to access exactly one GAL.

If no custom GAL is assigned, users automatically see the default one.

2. Offline Address Book (OAB)

The Offline Address Book allows users to access address information when Outlook is offline.

Although Microsoft is moving toward online-only experiences, OABs are still required when using Address Book Policies.

3. Room Address Book

Room address books contain:

  • Conference rooms
  • Equipment mailboxes

They help Outlook’s Room Finder feature display only relevant meeting spaces.

What Are Address Book Policies?

An Address Book Policy (ABP) is a container that groups multiple address book components and assigns them to users.

Each Address Book Policy includes:

  • One Global Address List
  • One Offline Address Book
  • One Room Address Book
  • One or more Address Lists

Once assigned, the user only sees the directory objects defined in that policy.

Address Book Policies enforce directory segmentation, not just organization.

Why Address Book and Address Book Policies Matter

Using Address Book and Address Book Policies allows organizations to:

  • Prevent users from viewing unrelated departments
  • Separate companies sharing the same tenant
  • Reduce accidental communications
  • Improve compliance and privacy
  • Enhance Outlook usability

This is especially valuable in:

  • Multi‑company tenants
  • Educational institutions
  • Managed service providers (MSPs)
  • Large enterprises with strict access boundaries

How Address Book and Address Book Policies Work Together

Think of it this way:

  • Address Books define what data exists
  • Address Book Policies define who can see what

An Address Book Policy does nothing on its own—it simply ties multiple books together and applies them to a mailbox.

Once assigned:

  • Users cannot search the full GAL
  • All address lookups are filtered automatically
  • Outlook, OWA, and mobile clients obey the policy

Outlook Web Access (OWA) Policies: The Ultimate Positive Admin Guide for Secure Email Access

Creating Address Books (High‑Level Overview)

Although we won’t run commands here, the general process involves:

  1. Creating filtered address lists
  2. Creating a custom Global Address List
  3. Creating a Room Address Book
  4. Creating an Offline Address Book
  5. Combining everything into an Address Book Policy
  6. Assigning the policy to mailboxes

All of this is done using Exchange Online PowerShell.

Best Practices for Address Book and Address Book Policies

Use Clear Naming Conventions

Include company or department identifiers:

  • GAL_Contoso
  • ABP_Finance
  • AL_Sales_Users

Avoid Overlapping Filters

Overlapping filters can cause:

  • Missing objects
  • Inconsistent directory results

Each mailbox should clearly match only one policy scope.

Always Test with a Pilot User

Before full rollout:

  • Assign the policy to a test mailbox
  • Verify Outlook, OWA, and mobile results

Plan for Growth

Design filters that allow:

  • New departments
  • Mergers
  • Organizational changes

Future‑proof filters save administrative effort later.

Limitations You Should Know

While Address Book and Address Book Policies are powerful, they have some constraints:

  • Not supported with on‑prem Exchange only
  • No dynamic assignment (must assign per mailbox)
  • Requires PowerShell (no full GUI setup)
  • One policy per mailbox

Understanding these limitations helps set proper expectations.

Address Book Policies vs GAL Segmentation

FeatureAddress Book PoliciesGAL Segmentation (Legacy)
Supported in Exchange OnlineYesNo
Granular controlsYesLimited
Future‑proofYesDeprecated
PowerShell basedYesYes

Address Book Policies are the modern, supported solution.

Common Scenarios for Address Book Policies

Multi‑Company Tenant

Each company sees only its own users.

University or School

Students, faculty, and staff are isolated using different address books.

M&A (Mergers and Acquisitions)

Provides temporary directory separation during consolidation.

MSP‑Managed Tenants

Prevents cross‑customer address visibility.

Performance and User Experience Impact

When properly configured, Address Book and Address Book Policies:

  • Improve directory search performance
  • Reduce Outlook auto‑complete clutter
  • Provide clean, relevant results

There is no negative performance impact on Exchange Online itself.

Security and Compliance Benefits

Address book segmentation helps with:

  • Data minimization
  • Internal privacy policies
  • Regulatory requirements (data exposure control)

While not a security boundary, ABPs offer practical exposure reduction.

Final Thoughts: Why Master Address Book and Address Book Policies

Address Book and Address Book Policies are often overlooked but immensely powerful features of Exchange Online.

They allow administrators to:

  • Design cleaner directory experiences
  • Enforce logical organization boundaries
  • Support secure and scalable tenant designs

When combined with good planning and naming standards, they become a rock‑solid foundation for directory management in Microsoft 365.

If you manage Exchange Online in any professional capacity, mastering Address Book and Address Book Policies is no longer optional—it’s essential.

Vishal Prajapati is a Microsoft 365 administrator and technology enthusiast with hands-on experience managing and supporting modern cloud-based environments. He works extensively with Microsoft 365 services and focuses on helping administrators understand complex concepts through clear, practical, and real-world guidance.

Leave a Comment