Study guide

5.2 Creating & Managing Contacts

Microsoft 365 Administrator Expert MS-102

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 MS-102 Exam Facts & Blueprint 1.2 Registration, Retake & Renewal 1.3 Study Strategy & Using This Guide

2 Tenant Setup, Domains & Org Settings

2.1 Creating a Microsoft 365 Tenant 2.2 Implementing and Managing Domains 2.3 Configuring Org Settings: Security, Privacy & Profile

3 Service Health, Network & Software Updates

3.1 Monitoring Service Health & Notifications 3.2 Network Connectivity Insights 3.3 Configuring & Monitoring Software Updates

4 Adoption, Usage & Microsoft 365 Backup

4.1 Monitoring Adoption & Usage 4.2 Configuring & Managing Microsoft 365 Backup

5 Users, Contacts, Groups & Shared Mailboxes

5.1 Creating & Managing Users Including External Users 5.2 Creating & Managing Contacts 5.3 Managing Microsoft 365 Groups & Shared Mailboxes

6 Licensing & Bulk User Management

6.1 Managing & Monitoring Microsoft 365 Licenses 6.2 Bulk User Management with Graph & Entra PowerShell

7 Roles, Admin Units & Privileged Identity Management

7.1 Implementing & Managing Roles in M365 & Entra ID 7.2 Managing Permissions for Defender XDR, Purview & Workloads 7.3 Managing Delegation with Administrative Units 7.4 Managing Entra ID Roles in PIM

8 Identity Synchronization with Entra Connect

8.1 Preparing for Identity Synchronization & IdFix 8.2 Directory Sync with Entra Connect Sync & Cloud Sync 8.3 Monitoring Sync with Entra Connect Health 8.4 Troubleshooting Synchronization

9 Authentication, SSPR & Password Protection

9.1 Implementing & Managing Authentication Methods 9.2 Self-Service Password Reset (SSPR) 9.3 Microsoft Entra Password Protection 9.4 Investigating & Resolving Authentication Issues

10 Identity Protection, Conditional Access & MFA

10.1 Planning for Identity Protection 10.2 Implementing Entra Identity Protection 10.3 Planning & Implementing Conditional Access Policies 10.4 Managing MFA with Conditional Access

11 Defender XDR Posture, Incidents & Threat Intelligence

11.1 Security Exposure Management & Secure Score 11.2 Incidents, Alerts & Advanced Hunting 11.3 Reviewing Defender XDR Reports 11.4 Defender Threat Intelligence

12 Defender for Office 365: Policies, Alerts & Investigation

12.1 Threat Policies & Rules in Defender for Office 365 12.2 Configuring Alert Policies 12.3 Investigating & Responding to Email Threats

13 Attack Simulation & Restricted Entities

13.1 Managing Attack Simulations & Training 13.2 Managing Restricted Entities & Blocked Users

14 Defender for Endpoint

14.1 Onboarding Devices to Defender for Endpoint 14.2 Configuring Endpoint Settings 14.3 Defender Vulnerability Management Dashboard

15 Defender for Cloud Apps

15.1 Configuring the App Connector for Microsoft 365 15.2 Defender for Cloud Apps Policies & Alerts 15.3 Interpreting the Activity Log 15.4 Cloud App Discovery

16 Purview Information Protection & Data Lifecycle

16.1 Sensitive Information Types 16.2 Retention Labels & Policies 16.3 Sensitivity Labels & Policies 16.4 Monitoring Label Usage: Content & Activity Explorer

17 Purview Data Loss Prevention

17.1 DLP Policies for Microsoft 365 Workloads 17.2 Configuring Endpoint DLP 17.3 Reviewing & Responding to DLP Alerts, Events & Reports

18 Final Review & Exam Strategy

18.1 Exam-Day Strategy & Question Handling 18.2 Final Review Checklist & Next Steps

5.2 Creating & Managing Contacts

Key Takeaways Explain This Topic AI

Microsoft 365 distinguishes Mail contacts (external contact visible in the GAL, no sign-in credentials) from Mail users (external email address plus managed Entra credentials)

Mail contacts are created in Exchange Online and show in the Global Address List so internal users can email an external person without that person holding a mailbox in the tenant

Contacts are directory objects — not guest users and not shared mailboxes — and never consume a Microsoft 365 license

A Mail user signs in with Entra credentials but delivers mail to an external address; a Mail contact cannot sign in at all

Use a contact when the external party only needs to be email-reachable from inside the tenant; use a guest user when they need to collaborate in Teams, SharePoint, or M365 Group content

Last updated: August 2026

Two Kinds of Contacts in Microsoft 365

Microsoft 365 has two mail-enabled contact object types. They look similar in the GAL but differ in whether the object carries managed credentials.

Object Has Entra sign-in credentials? External email address? Visible in GAL? Typical use

Mail contact No Yes (external) Yes An external vendor or partner you want everyone in the company to be able to email

Mail user Yes (managed in Entra) Yes (external delivery) Yes A contractor who logs in to Entra-managed apps but receives mail at their own external address

Key distinction: A Mail user is an identity with an external delivery target . A Mail contact is just a directory entry with an external email — no identity, no sign-in, no password. Both appear in the GAL; only the Mail user can authenticate.

Creating Contacts

You can create contacts from two surfaces:

Microsoft 365 Admin Center

M365 admin center → Teams & groups → Shared mailboxes & Contacts (the left nav item is under Resources/Contacts depending on portal version) → Add a contact. The wizard collects display name, alias, and external email address. The contact is provisioned in Exchange Online automatically.

Exchange Admin Center

Exchange admin center → Recipients → Contacts → New contact . The Exchange surface exposes more mail-flow properties — custom email address policies, mail-tip text, message size restrictions, and hide-from-GAL lists — that the M365 wizard omits. Use the Exchange admin center when you need fine-grained mail-flow control.

  • Core Contact Properties
  • Display name — what appears in the GAL and on outgoing mail

Alias — the local part used to form the internal mail-routing address ( bob becomes bob@contoso.onmicrosoft.com for routing, even though delivery is to the external address)

External email address (TargetAddress) — where mail actually goes; this is the only address external senders see on replies

Hide from address lists — yes/no toggle to suppress GAL visibility while keeping mail flow (useful for internal-only routing contacts)

GAL Visibility and Using Contacts for Distribution

Contacts appear in the GAL by default, so any internal user can resolve the name in Outlook's address book and send mail — the contact routes the message to the external address. Contacts can also be added as members of distribution lists and Mail-enabled security groups , which is how an external partner gets looped into a recurring mailing list without being granted any tenant access.

A hidden contact (Hide from address lists = Yes) is not visible in the GAL but still accepts mail addressed to its routing address — useful for system mailboxes that forward to an external address but should not clutter the address book.

Differentiating Contacts from Guest Users and Shared Mailboxes

These three object types are frequently confused because they all relate to external mail addresses or external people. They are not interchangeable.

Decision Table

You need to… Use this Why

Let internal staff email an external person who has no access to your tenant Mail contact No identity, no license, GAL-reachable

Give an external contractor sign-in access to Entra-managed apps while their mail stays external Mail user Has managed credentials; mail routed externally

Invite an external partner to collaborate in Teams/SharePoint/M365 Groups Entra B2B guest user Issues a guest object with #EXT# UPN; home tenant authenticates them

Provide a generic mailbox (info@, support@) that several internal users open together Shared mailbox One mailbox, multiple delegates, no separate license up to 50 GB

Exam angle: Contacts never authenticate and never consume licenses. Guest users authenticate with their home identity and collaborate in workloads. Shared mailboxes are for internal delegates sharing one address — they are not for external recipients.

Managing and Updating Contacts

Bulk operations — Exchange admin center and PowerShell ( Set-MailContact , Set-MailUser ) support bulk property updates and CSV import

Mail-tip — a short hint shown in Outlook when a user addresses the contact (e.g., 'This is a third-party vendor — do not share internal data')

Hide from GAL — toggle when a contact should remain mail-reachable but not discoverable

Delete — removing a contact is immediate (no 30-day window like user accounts); the GAL entry disappears within directory sync latency

Common Misconfiguration

Creating a Mail user when you meant to create a Mail contact leaves an orphan Entra identity that someone could sign in with — a real security gap if the external party was not supposed to have credentials. Always confirm which object type the wizard selected before saving.

Quick Reference: Where Each Object Lives

Object Created in Managed in Authenticates against License?

  • Mail contact M365 admin center or EAC Exchange Online No No
  • Mail user EAC or PowerShell Exchange Online + Entra ID Yes — Entra credentials Only if you assign one

B2B guest user Entra admin center / invitation API Entra ID Home identity provider Generally no host M365 license

Shared mailbox M365 admin center or EAC Exchange Online No (delegates use their own creds) No up to 50 GB; Plan 2 over 50 GB or with archive