2.1.1. Users and Contacts
💡 First Principle: A directory object should carry exactly the capabilities the person needs. Someone who works here needs a user account; someone who only needs to be emailed needs nothing more than a contact; someone external who needs to sign in to your resources needs credentials in your tenant.
Creating users. You can create cloud users in the Microsoft 365 admin center (Users > Active users > Add a user), in the Microsoft Entra admin center, in bulk from a CSV, or with Microsoft Graph PowerShell. The essentials are a display name, a user principal name (UPN) in one of your verified domains, a password, and — before you assign any license — a usage location. A license can be assigned only when the account has a valid usage location (a two-letter ISO country code), because licensing terms and service availability vary by country. A user created by script without a usage location is a classic reason a license assignment fails.
Managing users. Day-to-day tasks include resetting passwords, blocking sign-in (the account stays, but can't authenticate), changing the UPN, assigning licenses and admin roles, and converting a departing user's mailbox to a shared mailbox so the content stays available. Blocking sign-in is the right first move when someone leaves suddenly: it stops access immediately and is fully reversible.
Deleting and restoring. A deleted user is soft-deleted and can be restored, with its properties, for 30 days — in the admin center under Users > Deleted users, which needs at least User Administrator. After 30 days the account is permanently deleted and must be re-created from scratch. Restoring a user also restores the licenses it held, even if none are free, which can leave the tenant temporarily out of license compliance.
Contacts. Two recipient types represent people with an external email address, and they appear in the address book:
| Mail contact | Mail user | |
|---|---|---|
| External email address | Yes | Yes |
| Sign-in credentials in your tenant | No | Yes |
| Can access your resources | No | Yes |
| Exchange Online license needed | No | No |
| Typical use | A supplier's sales rep in the global address list | A contractor who signs in to your SharePoint but keeps their own mailbox |
Both are managed in the Exchange admin center under Recipients > Contacts, and mail contacts can also be added in the Microsoft 365 admin center under Users > Contacts. The deciding question is always: does this person need to sign in? If yes, it's a mail user (or a guest); if no, a mail contact.
⚠️ Exam Trap: "A partner needs to appear in the global address list so staff can email them" calls for a mail contact — not a guest user and not a mail user. Giving sign-in credentials to someone who only needs to receive email widens your attack surface for no benefit.
Reflection Question: An employee leaves on bad terms on a Friday afternoon. Why is blocking sign-in a better first step than deleting the account, and what's the deadline if you later decide you deleted an account by mistake?