5.2 Exchange Online and Outlook
Key Takeaways
- Exchange Online is the Microsoft 365 hosted messaging service for mailboxes, calendars, contacts, and tasks; Outlook is the client on desktop, the web (outlook.office.com), and mobile.
- A shared mailbox is a common inbox and calendar (for example info@ or support@) that licensed users open by delegation; it is not a sign-in account and is not the same as a distribution group.
- Distribution groups only fan email out to a list of people; Microsoft 365 Groups add a shared mailbox plus a SharePoint site, calendar, and other collaboration tools, and they are what Teams uses for membership.
- Focused Inbox splits a mailbox into Focused and Other so important messages are easier to see; calendar delegates and room-mailbox booking delegates are high-level Exchange calendar capabilities.
- Exchange hybrid — some mailboxes on-premises, some in Exchange Online — is the mail flavor of hybrid deployment taught in Chapter 3, not a second email product.
5.2 Exchange Online and Outlook
Quick Answer: Exchange Online is the service that hosts email, calendars, contacts, and tasks. Outlook is the client — desktop, Outlook on the web at outlook.office.com, and Outlook mobile. A shared mailbox is a common inbox. A distribution group only sends mail to many people. A Microsoft 365 group is a collaboration identity with mail plus a workspace.
The official MS-900 bullet asks you to describe the email and calendaring capabilities of Microsoft Exchange and Outlook. The most expensive mistake on this bullet is mixing up the two names. Exchange is the service. Outlook is the client. You can read the same Exchange Online mailbox in the Outlook desktop app, in the browser, and on a phone. You cannot “install Exchange” on a laptop the way you install Outlook.
Exchange Online: the hosted mailbox service
Microsoft Exchange Online is a hosted messaging solution. Official service-description language is that it delivers email, calendar, contacts, and tasks from PCs, the web, and mobile devices, and that it integrates with Microsoft Entra ID. Folders and messages live in Microsoft datacenters. Each user who uses the service needs a subscription that includes a mailbox. Conference rooms and shared mailboxes are the documented exceptions: those special mailbox types do not get their own sign-in; licensed users open them by delegation.
What that means in fundamentals language:
- A user mailbox is the person’s inbox, calendar, contacts, and tasks. That is what Outlook opens when you sign in as yourself.
- A shared mailbox is a mailbox several people work —
info@contoso.com,support@, a reception desk. Members with permission can read mail, send as or send on behalf of the shared address (when an admin grants that), and use the shared calendar that is created with the mailbox. Official admin guidance: a shared mailbox can hold 50 GB without its own license; growing it, archiving it, or placing it on litigation hold requires additional Exchange licensing. Users who open it must already have a licensed Exchange Online mailbox. Block sign-in on the shared mailbox account; it is not a person. You cannot give a Gmail user a key to a shared mailbox — if outsiders need to participate, Microsoft points you to a Microsoft 365 group instead. Microsoft also documents a practical concurrency limit: if more than 25 people hammer the same shared mailbox, consider a Microsoft 365 group. - Resource mailboxes (room and equipment) make a conference room or a loaner device reservable from Outlook. The room can automatically accept or decline based on booking rules, or a booking delegate can approve requests.
Calendaring is a first-class Exchange capability, not an Outlook-only gadget. People share calendars, see free/busy, book rooms, set out-of-office replies, and let an assistant manage an executive calendar. Those objects live in the mailbox on Exchange Online. Outlook is how you look at them.
Groups: distribution versus Microsoft 365 Groups
Exchange Online can address mail to more than one person without creating a shared inbox. The MS-900 distinction that matters:
| Type | What it is for | Has a shared inbox people work? | Also a workspace? |
|---|---|---|---|
| Distribution group | Broadcast email to a defined list (“everyone in Building A,” “all staff”) | No — mail is delivered to each member | No SharePoint site, no Teams team from the DG itself |
| Dynamic distribution group | Same idea, but membership is calculated when a message is sent from Exchange attributes such as department or location | No | No |
| Microsoft 365 group | Collaborate: group email plus a SharePoint site, shared calendar, Planner, and optional Teams or Viva Engage | Yes — a group mailbox, with a different model than a shared mailbox | Yes. Teams uses Microsoft 365 Groups for membership |
| Shared mailbox | Several people work one address and one calendar | Yes | No SharePoint team site is created just because you made the mailbox |
| Security group | Grant access to resources such as SharePoint sites | No (unless it is mail-enabled) | Access control, not a mailbox |
A distribution group is the right answer when the scenario is only “send the same announcement to these people.” It is the wrong answer when those people also need a shared file library, a shared calendar they manage together, or a team in Teams.
A Microsoft 365 group is the right answer when the scenario is a collaboration identity: the group has an email address and a SharePoint site (and can be the membership backbone of a team). Guests can be added when an admin allows it. Members can subscribe so group conversations appear in their own inbox. You cannot migrate a shared mailbox to a Microsoft 365 group; if you picked the wrong object, you create the right one and move the work.
A shared mailbox is the right answer when several internal people must work the same inbox and send as support@, and you do not need the full Microsoft 365 group workspace. You also cannot stop members from deleting messages in a shared mailbox; Microsoft’s documented alternative when you must restrict deletion is a Microsoft 365 group.
Retention, at the level this exam wants
Exchange Online can retain or delete mailbox items according to retention policies, labels, and tags. Encryption of data at rest, deleted-item recovery, and hold capabilities exist as service features; how deep they go depends on the plan. Do not treat retention as an Outlook client checkbox you invent, and do not memorize unpublished default periods as if they were printed on the MS-900 outline. Deeper Microsoft Purview retention, eDiscovery, and records work is a later chapter. For this bullet, know that retention is a service-side capability on the Exchange mailbox, not something Outlook stores only on the laptop.
Exchange hybrid is a pointer, not a new product
Some organizations keep Exchange Server mailboxes on-premises and put others in Exchange Online, with shared mail flow and a shared address book. That is Exchange hybrid — the mail flavor of the hybrid cloud model in Chapter 3. MS-900 may mention it so you recognize that not every mailbox has to move on day one. It is not a third email brand, and this chapter will not walk the Hybrid Configuration wizard. If a scenario says some mailboxes stay in the datacenter and some are already in Microsoft 365, you are looking at hybrid Exchange, and Outlook can still be the client for both.
Outlook: one mailbox, three common clients
Outlook is how people read Exchange mail and manage calendars. The three clients MS-900 expects you to name are:
| Client | What to picture | Why the exam cares |
|---|---|---|
| Outlook desktop | The Outlook app in Microsoft 365 Apps on Windows or Mac | Full client for mail, calendar, contacts, and offline work when the device has the desktop-apps license |
| Outlook on the web | Browser access, commonly outlook.office.com (also called Outlook on the web; older materials say OWA) | Same mailbox, no desktop install. Official docs still use this URL even in Microsoft 365 tenants |
| Outlook mobile | Outlook for iOS and Outlook for Android | Mail, calendar, and contacts on a phone, including shared-mailbox support when both mailboxes are in Exchange Online |
A user who “only has a browser” is not without Exchange. They use Outlook on the web. A user who “needs the desktop ribbon and offline mail” needs the Outlook desktop client. A user who “must approve a meeting from the airport” uses Outlook mobile. All three talk to Exchange Online. None of them is Exchange Online.
Other protocols exist (Exchange ActiveSync, IMAP, POP, SMTP) so non-Outlook clients can connect. Fundamentals items almost always want Outlook as the Microsoft client family, not a third-party app name.
Focused Inbox, booking, and delegates
Focused Inbox splits the Inbox into Focused and Other. Important mail stays on Focused; the rest remains available on Other. Microsoft documents it as the replacement for Clutter in Outlook on the web and newer Outlook clients. Users can train it by moving messages. Admins can influence organization defaults, but a user may still see the feature differ across desktop, web, and mobile. For MS-900, describe the idea: surface the mail that matters first. It is not a separate mailbox, not a retention policy, and not anti-malware.
Delegates are people you empower to act on a mailbox or calendar. The two pictures that show up in scenarios:
- A calendar or mailbox delegate (executive assistant) can manage someone else’s calendar, accept meetings, and sometimes send on their behalf, depending on the permissions granted.
- A booking delegate on a room or equipment mailbox approves or declines reservation requests when the room is not set to auto-accept. Booking options on the resource (window of days, maximum duration, whether repeating meetings are allowed) are Exchange calendar settings, not a different Microsoft 365 app. Microsoft Bookings — the customer-facing appointment page taught with the work-management apps — is a different product. If the question is “who approves the boardroom,” you are in Exchange resource booking, not Bookings.
People also share calendars directly (view, edit) and use out-of-office replies. Those are Exchange calendar and mailbox features you operate from Outlook.
Scenario mapping
- Company email and calendars with no on-premises mail servers → Exchange Online, opened in Outlook (desktop, web, or mobile).
- Several agents must work
support@contoso.comand send replies as that address → shared mailbox, not a distribution group. - Weekly all-hands announcement to 400 people, no shared files → distribution group (or a dynamic DG if membership should follow department).
- Project team needs a group inbox plus files and a team in Teams → Microsoft 365 group (and the team that uses it), not a shared mailbox alone.
- Conference room that people reserve from the Scheduling Assistant → room mailbox, auto-accept or a booking delegate.
- Assistant manages a vice president’s calendar → Outlook/Exchange delegate access.
- Inbox is noisy; important mail should sit on its own tab → Focused Inbox.
- Some mailboxes still on Exchange Server, some already in Microsoft 365 → Exchange hybrid (see Chapter 3), still accessed with Outlook.
Exam traps
- Exchange is the service; Outlook is the client. “We use Outlook, so we do not have Exchange” is false in Microsoft 365. The mailbox is still Exchange Online.
- outlook.office.com is not proof the tenant is “only Office 365.” Outlook on the web keeps that URL in Microsoft 365.
- A distribution group is not a shared mailbox. DG = send to many. Shared mailbox = several people work one inbox.
- A Microsoft 365 group is not “just email.” It is the collaboration object that also carries SharePoint (and Teams membership).
- Do not sign in as the shared mailbox. Grant delegates access from their own licensed mailboxes.
- Focused Inbox is not retention and not a hold. It is a reading view.
- Room booking delegates are not Microsoft Bookings unless the scenario is a customer-facing booking page.
- Hybrid Exchange is still Exchange. Some mailboxes on-premises, some online; Outlook remains the client.
Official sources
- Exchange Online service description — hosted mail, calendar, contacts, and tasks; clients; rooms and shared mailboxes without their own login
- Compare types of groups in Microsoft 365 — Microsoft 365 Groups, distribution groups, security groups, shared mailboxes
- About shared mailboxes in Microsoft 365 — when to use a shared mailbox, licensing, 25-user guidance, no external sign-in
- Create a shared mailbox — send as a common address; shared calendar
- Create room and equipment mailboxes — reserve resources from Outlook
- Configure Focused Inbox — Focused and Other tabs
- Exchange Server hybrid deployments — hybrid as a pointer to mixed on-premises and cloud mailboxes
A consultant reads mail in Outlook on the web at outlook.office.com. Which statement is accurate?
Four internal support agents must read and reply from support@contoso.com as a common inbox and shared calendar. Which object should you recommend?
What does Focused Inbox do in Outlook?
Leadership wants a weekly announcement sent to every employee. Nobody needs a shared inbox, a shared calendar, or a file library for that announcement. Which object fits?