SMTP vs smtp: The Microsoft 365 Alias Case Rule Guides Miss
Every site you sign up for wants an email address, and handing out the same one everywhere turns your primary inbox into a spam funnel. The usual fix is a stack of email aliases on your own domain, and if your organization runs Microsoft 365, the admin center is where those aliases get created. That sounds simple until you touch PowerShell and discover that the case of a single prefix, SMTP: versus smtp:, decides which address becomes the user’s primary and which one stays a secondary alias. Get it wrong and the mailbox quietly starts sending mail from an address nobody planned to make public.
This guide walks the full path: what aliases actually do in Exchange Online, how to add them through the admin center click by click, and how to choose the correct proxy address case for primary and secondary entries. Along the way it covers the limits that shape the design. Microsoft 365 documents a proxy address limit of roughly 300 addresses per mailbox, Google Workspace allows up to 30 aliases per user on a business mailbox, and Gmail itself lets you send as up to 99 other addresses while capping gmail.com address changes at three times. None of those are truly unlimited email addresses, which is why a catch-all domain, one that accepts mail for every address on the domain, is described as the only genuinely unlimited option.
The case rule is the part most tutorials skip. Setting an alias with an uppercase SMTP: prefix promotes it to primary, demotes the old primary, and changes the default From address for every message the user sends. Lowercase smtp: adds it as a secondary alias without touching the primary. Read the next sections in order and you will be able to add aliases, audit every proxy address prefix before changes go live, and spot a mis-cased entry before a user notices their signature no longer matches their sender address.
How Microsoft 365 Email Aliases Work and Why You Need Them
An alias in Microsoft 365 is a second address that delivers mail into the same mailbox. It is not a separate account, not a distribution group, and not a shared mailbox. It is a proxy address attached to an existing recipient object, which means the user reads alias mail in the same inbox as everything else. That simplicity is why admins reach for aliases when they want unlimited email addresses without paying for extra licenses.
Every alias is stored as a proxy address on the mailbox. The primary address carries the uppercase SMTP: prefix and becomes the default From address. Secondary aliases carry lowercase smtp:. Section 3 covers that case rule in detail, but you need the vocabulary now because every admin center screen and PowerShell output you touch will show these prefixes.
Microsoft 365 documents a proxy address limit of roughly 300 addresses per mailbox. That is generous compared with Google Workspace, which allows up to 30 aliases per user on business mailbox aliases. Neither platform offers genuinely unlimited addresses on a single mailbox, though plus addressing stretches the practical count: a plus tag such as you+shopping@contoso.com reaches the base mailbox without consuming a proxy address slot. Plus addressing is enabled by default in Exchange Online, so any tag you type at signup works immediately.
Aliases, Catch-All Routing, and Plus Tags: What Each One Actually Does
A catch-all domain accepts mail for every address on the domain, whether or not a mailbox or alias exists. Point @contoso.com at one mailbox and anything@contoso.com lands there. This is the only genuinely unlimited option in the sense that no per-address configuration is required, but it also means every typo, spam probe, and dictionary attack hits the same inbox. Most organizations use a catch-all on a secondary domain for email registration on sites they do not trust, not on their primary domain.
Plus addressing is the lighter tool. Gmail users know it as Gmail aliases: the plus tag delivers mail to the base Gmail address, and Gmail allows sending as up to 99 other addresses from the same account. Exchange Online behaves the same way for inbound mail without any configuration. The difference is outbound: a plus tag is not a sendable identity unless you add it as a proxy address or configure send-as permissions.
Where aliases win is identity. A role address like billing@contoso.com attached as an alias to a real person’s mailbox keeps the public-facing name clean while the reply comes from a human. An email address per website, one alias for each vendor portal, keeps your primary address out of breach dumps and makes filtering trivial. When an alias starts attracting spam, delete it and the base mailbox is untouched.
One number worth memorizing before you open the admin center: Gmail limits gmail.com address changes to three times per account, so Google users treat address changes as scarce. Microsoft 365 admins have no such ceiling on aliases, which is why sloppy alias hygiene accumulates quietly. AllMail publishes an unlimited email addresses guide that covers the cross-platform comparison; the practical takeaway here is that Microsoft 365 rewards discipline because it does not enforce it.
Know which of the three mechanisms you are configuring before you click anything: a proxy address (identity, per-mailbox limit), a catch-all (domain-level routing, no limit, no isolation), or a plus tag (free, inbound only, zero setup). Most alias problems start with an admin confusing one for another.
Adding an Alias in the Microsoft 365 Admin Center Step by Step
The admin center path to an alias is shorter than most guides suggest, but every click matters because the Save button commits the change immediately and triggers directory sync. Sign in at admin.microsoft.com with an account holding at least User Administrator rights. Expand Users in the left navigation, then choose Active users. If the tenant is large, use the search box at the top of the list rather than scrolling; the grid paginates at 50 rows by default.
Click the display name of the target user (not the checkbox to the left, which opens bulk actions). The flyout panel opens on the Account tab. Confirm the Username field shows the primary address, then click Manage username and email under the Aliases section. A second panel appears listing every proxy address currently attached to the mailbox. On a fresh mailbox you see one entry: the primary, marked with a “Primary” label.
Adding each alias type and verifying propagation
Click + Add email alias. The dialog offers two options. Pick Add a new alias to this user’s Microsoft 365 mailbox and type the local part only; the domain dropdown lists every verified domain in the tenant, so choose deliberately. A custom domain mailbox alias resolves to the same inbox as the primary, which is exactly what you want for an email address per website or a role address like billing@. Click Save changes, then Close twice to exit the panels.
Repeat the flow for each additional address. Microsoft 365 documents a proxy address limit of roughly 300 addresses per mailbox, so the GUI is fine for a handful and painful for a hundred. Note that the alias becomes usable for email registration and inbound routing within minutes, but outbound identity is separate: the address will not appear in Outlook’s From list until you grant Send As permission or wait for the client to refresh its offline address book, which can take up to 24 hours.
| Field in the dialog | What to enter | Common mistake |
|---|---|---|
| Alias type | New alias to this mailbox | Choosing an existing contact instead |
| Domain dropdown | Verified custom domain | Leaving the tenant.onmicrosoft.com default |
| Local part | Lowercase, no spaces | Mixing case, which confuses later PowerShell work |
Verification is the step people skip. Open the alias panel again and confirm the new address is listed without the Primary label. Then send a test message from an external account to the alias and check that it lands in the user’s inbox, not in a catch-all mailbox or a quarantine. If the tenant routes unknown recipients through a catch-all domain, a typo in the alias will still deliver somewhere, which masks configuration errors during testing. Wait 15 minutes after saving before concluding anything is broken; directory replication across regions is not instant, and a second save during that window can produce a duplicate proxy address error.
SMTP vs smtp: Choosing the Correct Proxy Address Case for Primary and Secondary Aliases
Proxy addresses in Exchange Online are case-sensitive in exactly one place: the prefix. SMTP: in capitals marks the primary address. smtp: in lowercase marks every secondary alias. The domain part is case-insensitive, so SMTP:Jane@contoso.com and SMTP:jane@contoso.com are the same address. The prefix is not.
This trips people up because the admin center hides the raw strings. The GUI shows a tidy list of addresses with a “primary” label, and you never see the prefix. The moment you export or import via PowerShell, the prefix becomes the whole interface. Set-User -UserPrincipalName jane@contoso.com -EmailAddresses @{Add=”smtp:j.smith@contoso.com”} adds a secondary alias. Drop the case and write SMTP: instead, and you have just promoted j.smith@contoso.com to primary, demoted the old one to secondary, and changed the default From address in Outlook on the web, Outlook desktop after a sync, and any mobile client that respects the primary SMTP.
Nothing errors out. The cmdlet returns, the mailbox updates, and the user finds out when a customer replies to the wrong address or their signature looks wrong.
The underlying rule comes from the Exchange address model: every mailbox has exactly one proxy address with the uppercase SMTP: prefix, and any number of lowercase smtp: entries. Microsoft 365 documents a proxy address limit of roughly 300 addresses per mailbox, which is generous but finite. That is one reason a catch-all domain, which accepts mail for every address on the domain, is described as the only genuinely unlimited option for inbound routing, in contrast to the finite proxy address list that constrains unlimited email addresses for SEO tools. The catch-all lives at the domain level, not in the proxy address list.
Detecting a mistaken promotion is straightforward once you know what to look for:
- Run Get-Mailbox -Identity jane@contoso.com | Select-Object -ExpandProperty EmailAddresses and read the prefixes literally. Anything with uppercase SMTP: is the current primary.
- Compare against your intended primary. If the uppercase entry is not the address you expect, the case got flipped.
- Check the WindowsEmailAddress property, which reflects the primary SMTP and is what most clients use for the From field.
- Audit in bulk with Get-Mailbox -ResultSize Unlimited | Select DisplayName, WindowsEmailAddress and diff against your naming standard.
Fixing it means rewriting the set so exactly one uppercase SMTP: exists and it is the correct address. Use Set-Mailbox with -EmailAddresses and pass the full list, not @{Add} or @{Remove}, so you control the final state:
- Build the array: “SMTP:jane@contoso.com” for the true primary, then “smtp:j.smith@contoso.com”, “smtp:jane.smith@contoso.com” for the rest.
- Run Set-Mailbox -Identity jane@contoso.com -EmailAddresses $list.
- Re-run Get-Mailbox and confirm one uppercase prefix.
- Have the user restart Outlook or clear the autodiscover cache so the From address refreshes.
Two habits prevent the whole class of error. First, always type the prefix by hand in scripts and never let a text editor auto-capitalize the line. Second, keep a naming convention where secondary aliases are visually distinct from the primary, so a wrong promotion is obvious in the audit output. The case rule is small, but it is the difference between a proxy address and a new identity for the mailbox.
Managing Aliases at Scale with PowerShell and Plus Addressing
Adding aliases one mailbox at a time in the admin center does not survive contact with a real tenant. Once you pass a few dozen users, PowerShell is the only sane path, and the commands below assume the Exchange Online PowerShell module with an account holding Exchange Administrator rights.
Bulk creation starts from a CSV with two columns: the user’s identity (UPN or primary SMTP) and the alias to add. The critical detail is the prefix. Secondary aliases must be written in lowercase smtp:, because a capital SMTP: tells Exchange this is the primary address. Get that wrong in a bulk run and you have silently reassigned the default From for every user in the file.
Read the current state before writing anything:
Get-Mailbox -ResultSize Unlimited | Select DisplayName, PrimarySmtpAddress, EmailAddresses
For a large tenant, flatten that output so you can audit prefixes in a spreadsheet:
Get-Mailbox -ResultSize Unlimited | ForEach-Object { $_.EmailAddresses | Where-Object { $_ -like "*smtp:*" } | ForEach-Object { [PSCustomObject]@{ User = $_.ToString(); Prefix = $_.PrefixString } } }
The PrefixString property returns either SMTP or smtp, which makes case errors trivial to spot. Filter for Prefix -eq "SMTP" and you should get exactly one hit per mailbox. Two hits means someone set a secondary alias with the wrong case and the mailbox now has competing primaries, a condition that produces odd reply-to behavior rather than a clean error.
To add aliases in bulk, use Set-Mailbox with -EmailAddresses @{Add="smtp:alias@contoso.com"}. Microsoft 365 documents a proxy address limit of roughly 300 addresses per mailbox, which sounds generous until a catch-all domain or a shared role address starts receiving forwarded copies. A catch-all domain accepts mail for every address on the domain, so if you point one at a single mailbox, that mailbox’s proxy list grows with every address anyone invents. Keep catch-all routing separate from user mailboxes.
Plus addressing is the other lever. Plus addressing delivers mail to the base Gmail address when you append a tag, and plus addressing is enabled by default in Exchange Online as well, so jdoe+newsletter@contoso.com lands in jdoe’s inbox without any admin action. That behavior gives every user an unbounded set of per-site addresses with zero proxy address cost. Where it matters:
- Use plus tags for one-off email registration on sites; they need no admin center change and no proxy slot.
- Reserve real aliases (lowercase
smtp:) for addresses that must appear in the From field or survive a reply. - Keep catch-all domains on a dedicated mailbox or a forwarding domain, never on a user’s primary mailbox.
- Audit
PrefixStringbefore and after every bulk run, not just after.
One more check before changes go live: confirm no alias in your CSV already exists on another mailbox. Get-Recipient alias@contoso.com returns the owner instantly, and a duplicate proxy address will fail the whole batch rather than the single line, so validate the list first and save yourself a partial run.
Testing, Troubleshooting, and Best Practices for Alias Configuration
Every alias change deserves a delivery test before it is trusted. Send a message from an external mailbox (not another tenant mailbox, which can mask routing problems) to each new address, then open the message header and confirm the To: line shows the alias and the resolved mailbox is correct. Reply once to verify the outbound From behavior, especially if the alias was intended to become primary.
Watch the message trace rather than the inbox alone. In the Exchange admin center, run a trace filtered on the alias as recipient, with a 24-hour window, and confirm status Delivered. If the alias is on a custom domain mailbox, check the domain’s MX record points at your tenant before blaming the alias. A plus tag test (send to name+tag@domain.com) confirms whether plus addressing is enabled by default in Exchange Online for that mailbox, since plus addressing delivers mail to the base address only when the recipient accepts it.
The most common failure is a duplicate proxy address. Two objects cannot share one SMTP address, so the save fails with “The proxy address is already being used.” Before adding anything, run a tenant-wide audit:
- Export all proxy addresses with Get-Mailbox -ResultSize Unlimited | Select DisplayName, EmailAddresses.
- Sort and count duplicates in a spreadsheet or with Group-Object on the address string.
- Resolve collisions by removing the stale alias from the old object, waiting for directory sync, then re-adding.
Sync conflicts come second. If the mailbox is synced from on-premises Active Directory, the cloud copy is read-only for proxy addresses; edit proxyAddresses in AD and let the connector replicate. Editing in the cloud produces changes that revert on the next sync cycle. Hybrid environments also fail silently when the on-premises object lacks the accepted domain, so confirm the domain exists in both places.
Case mistakes account for the quietest errors. A secondary alias written as SMTP: instead of smtp: becomes primary on save, and the user’s default From changes without any warning dialog. Always verify prefixes with a script that flags every address where the uppercase form appears more than once per mailbox.
Best practices checklist:
- One primary per mailbox, uppercase SMTP:, documented in the ticket.
- Secondary aliases always lowercase smtp:, reviewed in bulk before commit.
- Naming convention: role addresses for shared functions, firstname.lastname for people, no free-form tags.
- Reserve a dedicated alias per website registration so a breach exposes one address, not the primary.
- Keep a spreadsheet of alias to owner to purpose, updated in the same change window.
- Re-test mail flow after every bulk PowerShell run, not just after GUI edits.
Microsoft 365 documents a proxy address limit of roughly 300 per mailbox, so bulk scripts should count before appending. For context on how other providers handle volume, Google Workspace allows up to 30 aliases per user, and Gmail allows sending as up to 99 other addresses. AllMail publishes the unlimited email addresses guide, which describes a catch-all domain as the only genuinely unlimited option, and that framing helps when a stakeholder asks why the tenant cannot simply absorb hundreds of aliases per user.
Before you close the admin center, run one last audit that catches the mistakes this guide warned about. Pull every proxy address on the affected mailboxes and confirm the primary is the only one carrying uppercase SMTP:, then compare the count against the documented ceiling of roughly 300 proxy addresses per mailbox on Microsoft 365. A quick PowerShell export to CSV gives you a baseline you can diff after the next change window, which is far cheaper than reconstructing history from a user complaint about mail landing in the wrong inbox. If you also run Google Workspace for any team, remember the Workspace alias limit of 30 per user and the three-change cap on gmail.com address changes; those constraints belong in the same spreadsheet so nobody promises a user an alias the platform will reject.
For the next step, pick one low-risk mailbox and rehearse the full cycle: add a secondary alias with lowercase smtp:, send a test message from an external account, verify it arrives, then send as that address to confirm the From header is what you expect. Repeat with a plus tag (base address + tag) to prove inbox routing still works, and check whether your tenant inherits plus addressing, which is enabled by default in Exchange Online. Once the test passes, scale it: script the aliases for a pilot group, document each address in a naming register, and only then touch the catch-all domain or your domain email hosting records. AllMail publishes the unlimited email addresses guide if you want the broader map of aliases, forwarding, and per-site addresses before you commit. The habit that prevents most incidents is boring: one change, one verification, one line in the log. Do that and the case rule stops being a trap and becomes a detail you check without thinking.

