An Outlook.com alias is a second address that lands in the same inbox, and it is genuinely useful. It is not, however, a cloak. Plenty of guides promise that creating an alias will keep your real address out of sight, and that promise falls apart the moment you look at a raw message header. The alias changes the address people write to and the address they see on the message you send back. It does not rewrite every trace of the account behind it. If your goal is to stop a sender from ever learning your primary address, an alias alone will disappoint you.
What an Outlook.com alias actually changes, and what it leaves exposed
Start with the mechanics. Outlook.com attaches aliases to a Microsoft account, and every alias shares the same inbox, the same password, and the same security settings. You can add up to 10 aliases on a consumer account, and Microsoft limits how frequently users can add aliases, so you cannot churn through them the way you might with a dedicated masking service. When you send a message from the Outlook.com web client and pick an alias in the From field, the recipient sees that alias. That part of the myth is true.
The header is where the story gets more complicated. Depending on the sending path, the account’s primary address can surface in the Return-Path or in authentication headers. The Return-Path is the address that receives bounces, and mail systems set it from the envelope sender, which does not always match the From line. Authentication headers record which account authenticated to Microsoft’s servers. If you send through a connected account, a mail client, or a third-party relay, the envelope and authentication data can point back to the primary username even while the visible From line shows the alias.
Treat this as a rule rather than an edge case. An alias is a routing label, not an anonymizing layer. Anyone who knows how to open the full header in Outlook, Gmail, or Yahoo can inspect what your server stamped on the message. As explained at allmail.one/blog/outlook-email-alias, if a sender is determined enough to read those fields, your primary address is not hidden. The alias protects you from casual exposure and from address harvesting on the To line. It does not protect you from a careful reader.
- Alias on the From line: visible to the recipient as the sender address.
- Return-Path: can carry the primary address depending on how the message was sent.
- Authentication headers: identify the authenticated account, not the alias.
- Sign-in behavior: security codes are sent to the primary username, which is a useful reminder of which address is the real one.
- Replies: land in the shared inbox, so replies to an alias do not create separation between identities.
Where aliases earn their keep, and how to set them up without false expectations
The alias still does real work. It keeps your primary address out of mailing lists, signup forms, and forum profiles, which cuts down on spam and makes it easier to spot which vendor leaked your address. It also gives you a clean address to hand out for a specific purpose, like a shopping account or a newsletter, and you can delete that alias later without touching the primary one. Plus addressing provides aliases without setup: append a plus sign and a tag to your address and it still arrives in your inbox, which is handy for filtering and for catching a list that resold your data.
For work, the picture shifts. Microsoft 365 adds aliases to a mailbox, and an administrator adds aliases in the Microsoft 365 admin center or with PowerShell against Exchange Online. An alias must use a domain added to Microsoft 365, so you cannot invent a domain on the fly. Business plans allow roughly 300 addresses per mailbox, which is enough to give a person several role addresses or to add a legacy domain after a rebrand. New aliases can take up to 24 hours to work, so plan ahead if you are switching a public address. Keep the alias vs shared mailbox distinction in mind: an alias is not a separate mailbox with its own login and permissions, and if you need delegation or a distinct sent-items trail, a shared mailbox is the right tool.
Sending from an alias in Microsoft 365 needs an extra step. An administrator enables sending from aliases via Set-OrganizationConfig SendFromAliasEnabled, and until that switch is on, the From field will not offer the alias. Even with it enabled, the primary SMTP address remains the account’s identity for sign-in and for many header fields, which is the same trade-off you see on Outlook.com. If you want a true secondary identity for outbound mail, a separate mailbox or a shared mailbox with Send As permission is more honest about what it does. If you are simply consolidating addresses, an alias is cheaper and cleaner than a second license, and it keeps your mail flow settings in one place.
Build your alias plan around what you actually want. Use aliases to reduce spam, to retire an old address gradually, and to keep a public-facing address separate from the one you sign in with. Do not use them as a privacy shield against a determined sender, and do not assume a deleted alias erases the messages already delivered. If you need real separation, look at a dedicated masking service or a separate account. If you need a tidy inbox and a shorter list of addresses tied to your name, an Outlook.com email alias or a Microsoft 365 email alias does the job well, provided you know that the primary address can still show up in the headers when the sending path calls for it. Check a test message’s full header before you rely on an alias for anything sensitive, and adjust your setup from there.