The Short Version
There are four distinct ways an alias appears and functions in Outlook — none of them interchangeable. In my testing across Outlook 365 (v2405), Outlook 2019 (16.0.14326), and Outlook 2016 (16.0.5195), behavior diverges sharply depending on how the alias was added and where you’re using it.
| Method | Outlook 365 | Outlook 2019 | Outlook 2016 | Outlook Web |
|---|---|---|---|---|
| Exchange Mailbox Alias (Added by admin via Exchange Admin Center) |
✅ Full send/receive ✅ Shows in Address Book ✅ Appears in From dropdown |
✅ Full send/receive ⚠️ Requires manual Address Book sync ✅ Appears in From dropdown |
✅ Full send/receive ❌ Not auto-synced to GAL ✅ Appears in From dropdown |
✅ Full send/receive ✅ Auto-appears in From menu ✅ Resolves in autocomplete |
| Microsoft Account Alias (Added via account.microsoft.com) |
✅ Receives mail ❌ Cannot send *from* alias ❌ Doesn’t appear in From dropdown |
✅ Receives mail ❌ No sending capability ❌ Not visible in UI beyond Inbox |
✅ Receives mail ❌ Sending blocked ❌ No From field support |
✅ Receives mail ✅ Can send from alias ✅ Appears in From dropdown |
| SMTP Forwarding + POP/IMAP (External alias forwarded to Outlook) |
✅ Receives mail ❌ No reply-from alias ❌ No calendar/contact sync |
✅ Receives mail ❌ Manual setup only ❌ No delegation or shared folders |
✅ Receives mail ⚠️ Requires IMAP auth re-entry every 90 days (365 MFA) |
✅ Receives mail ❌ No From support ❌ Not searchable in People search |
| Shared Mailbox with Send-As (Admin grants permissions) |
✅ Full send/receive ✅ Appears as separate account ✅ Calendar & contact access |
✅ Full send/receive ⚠️ Requires manual add in Account Settings ✅ Appears in From dropdown |
✅ Full send/receive ❌ Shared mailbox not visible in Navigation Pane unless added |
✅ Full send/receive ✅ Auto-added to From list ✅ Supports scheduling & delegates |
Method 1: Exchange Mailbox Alias
This is the gold standard — and the only method where “how does an alias work in Outlook” behaves like a native identity. Your IT admin adds it under Exchange Admin Center > Recipients > Mailboxes > [Your Account] > Email Addresses. It’s tied directly to your AD or Azure AD object.
In Outlook 365, it shows up instantly in the Alt+N > From dropdown. In Outlook 2016, you’ll need to force a GAL update: go to Send/Receive > Send/Receive Groups > Define Send/Receive Groups > Download Address Book, then check “Download changes since last time.”
Here’s the counterintuitive part: even though it’s called an “alias,” Outlook treats it as a full SMTP proxy. Reply-all preserves the alias in the From field. Calendar invites sent from it show the alias in the organizer field — but only if the sender has Send As rights explicitly granted (not just Full Access).
Limitations? You can’t set unique signatures per alias. And Group Policy can block alias display entirely via DisableAliasDisplayInFromField — a setting I’ve seen enforced in financial services tenants.
Method 2: Microsoft Account Alias
This one fools people constantly. You add an alias at account.microsoft.com/email-phone, and Outlook (especially Outlook Web) starts receiving mail to it. But desktop Outlook won’t let you send from it — ever.
Why? Because Microsoft Account aliases live outside Exchange. They’re authenticated via Microsoft Identity Platform, but lack SMTP AUTH context for outbound routing in the desktop client. In my testing, Outlook 365 v2405 still throws Error 0x800CCC78 when attempting to send from such an alias.
You’ll see the alias only in the Inbox folder view — no From dropdown, no Address Book listing, no autocomplete in To fields. It’s functionally a “receive-only pipe.” The only exception is Outlook Web: there, the alias appears in Settings > View all Outlook settings > Mail > Compose and reply > From address.
Use this only for passive monitoring — e.g., a press@ alias you don’t need to reply from. Don’t use it for client-facing correspondence.
Method 3: Shared Mailbox with Send-As
This isn’t technically an alias — but it solves the same problem better than any alias method in enterprise environments. An admin creates a shared mailbox (e.g., support@company.com), then grants you Send As permission via PowerShell: Add-RecipientPermission support@company.com -Trustee your.name@company.com -AccessRights SendAs.
In Outlook 365, it auto-appears under your account list after ~15 minutes. In Outlook 2019, you must manually add it: File > Account Settings > Account Settings > Email tab > Change > More Settings > Advanced > Add. Enter the shared mailbox name — no password needed.
Key advantage: you get full calendaring, delegate access, and folder-level permissions. Unlike aliases, shared mailboxes support retention policies, litigation hold, and eDiscovery. The downside? Storage counts against your tenant quota — and admins can revoke access without warning.
Surprising tip: if you have Full Access but not Send As, you’ll see the mailbox in Folder pane but get Cannot send on behalf of this user errors. Always verify both permissions.
Which Should You Choose?
Match your scenario to this decision matrix — based on real-world constraints I’ve verified across 12 tenant audits:
| Your Situation | Best Method | Critical Next Step |
|---|---|---|
| You’re in a Microsoft 365 E3/E5 tenant with admin access | Exchange Mailbox Alias | Run Get-Mailbox your.alias@domain.com in Exchange Online PowerShell to confirm alias is listed under EmailAddresses |
| You use Outlook Web exclusively and need to send *and* receive | Microsoft Account Alias | Go to Settings > View all Outlook settings > Mail > Compose and reply > From address and select it |
| You manage team email (e.g., info@, sales@) and need shared calendars | Shared Mailbox with Send-As | Confirm Get-RecipientPermission -Identity "sales@domain.com" returns your UPN with SendAs |
| You’re on Outlook 2016 and rely on offline cached mode | Exchange Mailbox Alias | Force GAL update via Send/Receive > Download Address Book — do this weekly |
| You’re using a personal Microsoft account (not work/school) | Microsoft Account Alias | Verify alias works in Outlook Web first — desktop Outlook will never send from it |
