Adding an alias to a Microsoft account looks like a two-click job until the page throws an error you have never seen before. The truth is that Microsoft quietly enforces a stack of limits, and each one fails with its own message. Before you touch the “Add alias” button, run four quick checks in order: your current alias count, recent alias removals, the domain list on your account, and how many aliases you have created in the past hour. Each failed check points to a different fix, so knowing which one you tripped saves a support ticket and a lot of guessing.
Why alias limits exist and how they shape your setup
An email alias in Outlook is not a separate mailbox. It is another address that routes into the same inbox, whether that inbox lives on Outlook.com or in an Exchange Online mailbox under Microsoft 365. Microsoft caps how many aliases you can hold and how fast you can add them because aliases are a known vector for spam, impersonation, and account churn. The company limits how frequently users can add aliases for the same reason it throttles sign-ups: to keep automated abuse expensive. That is the context behind every error you will hit.
On the consumer side, Outlook.com attaches aliases to a Microsoft account, and the ceiling is 10 per account. On the business side, Microsoft 365 adds aliases to a mailbox, and an administrator adds aliases in the Microsoft 365 admin center or through PowerShell against Exchange Online. Business plans allow roughly 300 addresses per mailbox, which sounds generous until you remember that shared mailboxes, distribution lists, and resource accounts all compete for address space in the same tenant. The limits are different, but the discipline is the same: plan the alias before you create it.
One detail trips up almost everyone. Security codes are sent to the primary username, not to a freshly minted alias. If you plan to sign in with an alias, verify the alias first, then test the sign-in flow before you rely on it. An alias that cannot receive a code is a dead end for recovery purposes.
The four checks, in the order that saves you time
Count, cooldown, domain, and rate
Check one: current alias count under 10. On Outlook.com, open your account security page and count every alias attached to the Microsoft account, including ones you never use. If you are at the ceiling, the fix is not to add another alias but to remove an unused one and wait out the cooldown (more on that below). On Microsoft 365, the count is per mailbox, and an administrator can confirm it in the Exchange admin center under the mailbox’s email address properties, where each Microsoft 365 email alias is listed. If you are near the limit, decide whether an alias or a shared mailbox is the better tool. An alias vs shared mailbox decision matters here: aliases share one inbox and one set of credentials, while a shared mailbox gives a team its own address and delegation controls.
Check two: no alias removal in the last 30 days. Microsoft treats a removed alias as unavailable for re-adding for 30 days. If you deleted an alias last week and now want it back, the system will refuse, and the error will not always say why. This is the check most people skip, and it produces the most confusing failures. Keep a simple log of aliases you remove and the date, so you never have to reconstruct the timeline from memory.
Check three: the target domain is in your account’s domain list. An alias must use a domain added to Microsoft 365, or one of the domains Microsoft offers on Outlook.com. You cannot invent a domain and expect mail to flow. In a tenant, an administrator adds the domain under Settings, then Domains, and completes the DNS verification before any alias on that domain will work. If the domain is missing, the alias creation fails at the validation step, not at the save step, which is why the error can feel abrupt.
Check four: no more than 2 aliases in the past hour. The rate limit is the sneakiest of the four. Microsoft throttles alias creation per account, and exceeding the threshold produces a temporary block rather than a permanent error. Wait an hour and the same request will usually succeed. If you are bulk-provisioning addresses for a team, do not script them in a tight loop. Space the calls out, or hand the job to an administrator who can add aliases in the Microsoft 365 admin center with proper change control.
Once the alias exists, decide whether users need to send from it. An administrator enables sending from aliases via Set-OrganizationConfig SendFromAliasEnabled, a single PowerShell switch that flips the capability tenant-wide. Without it, the alias receives mail but cannot be selected as a From address in Outlook. New aliases can take up to 24 hours to work fully, so test with an external sender before you announce the address to anyone. Plus addressing provides aliases without setup if you only need a quick tag: append a plus sign and a word to your primary address and the mail still lands in your inbox, no configuration required.
The checklist maps cleanly to error messages once you have run it a few times. A count failure usually reads as a limit reached message on the account page. A cooldown failure looks like a generic “cannot add” notice with no explanation. A domain failure surfaces during validation and names the domain. A rate failure is the vague one, often a temporary error that clears on its own. When you see an error, match it to the check rather than retrying blindly, because retrying a rate limit only extends the block.
Keep the four checks in a note next to your admin bookmarks. Count the aliases, confirm nothing was removed in the last 30 days, verify the domain is on the account, and respect the two-per-hour pace. Run them in that order and the alias creation flow stops being a gamble. If you are managing a tenant, document the process for your team and point them at the admin center rather than letting everyone self-serve. A few minutes of checking beats an afternoon of troubleshooting, and your users get working addresses on the first try.