Microsoft Finally Makes Send Mail from Alias Generally Available and What It Means for You
Sending mail from an alias in Microsoft 365 means you can send emails that appear to come from any secondary email address linked to your account, not just your primary address. Microsoft 365 has now made this feature generally available, allowing users to send from these alternate addresses directly without complicated workarounds. This change simplifies email management and improves communication flexibility for both individuals and organizations.
What does sending mail from an alias mean and why does it matter?
Sending mail from an alias lets you send email messages that show an alternate email address associated with your account instead of your main address. For example, if your primary email is [email protected] but you have an alias [email protected], you can send a message as [email protected] without switching accounts or mailboxes.
This matters because many organizations assign aliases to represent different roles, departments, or functions without creating separate mailboxes. Before, users had to rely on workarounds like "Send As" permissions on shared mailboxes or distribution groups, which required admin setup and could be awkward to use. Sending directly from an alias improves productivity and clarity, letting recipients quickly identify the relevant context or team behind the message.
How does Microsoft’s general availability change previous restrictions?
Before this feature became generally available, sending from an alias was unsupported or only available in limited previews with certain clients. Users often had to create shared mailboxes or distribution groups and request "Send As" or "Send on Behalf" permissions to send from those addresses.
Now, eligible users can send from aliases directly within their primary mailbox. This removes the need for separate mailboxes or complex permissions. The feature works natively in Outlook on the web and recent Outlook desktop clients, offering a simple, integrated experience.
For example, someone managing both personal and customer support emails previously had to switch mailboxes or profiles to send as [email protected]. With this update, they just select the alias in the From field when composing an email, streamlining their workflow.
Who can use this feature and what are the requirements?
This feature is available to Microsoft 365 commercial customers with Exchange Online mailboxes. It supports users on most Microsoft 365 subscription plans that include Exchange Online, such as Business and Enterprise plans.
To use it, your account must have one or more SMTP aliases configured in Azure Active Directory or Exchange Online. The feature is supported in Outlook on the web and Outlook for Windows and Mac versions updated to support it. Mobile Outlook apps and third-party email clients may not fully support sending from aliases yet.
Admins control the feature using Exchange Online PowerShell or the Microsoft 365 admin center, enabling or disabling it tenant-wide. When enabled and configured, users see their aliases listed in the From dropdown when composing messages.
This feature doesn’t apply to on-premises Exchange servers without hybrid configurations connecting to Exchange Online. Also, your organization’s policies must allow sending from aliases for it to work.
Are there security or compliance considerations when sending from an alias?
Sending from an alias raises security and compliance considerations, especially around anti-spoofing and email authentication protocols like DMARC, SPF, and DKIM. Because aliases share the same mailbox and domain as your primary email, messages sent from aliases generally pass these checks, provided your domain’s DNS records are correctly configured.
Organizations should confirm that sending from aliases fits their email policies. Some may restrict which aliases users can send from to prevent impersonation or misuse.
Admins need to verify that anti-spoofing policies don’t block legitimate alias-sent emails. They should also use audit and logging tools to track alias usage for accountability. While sending from aliases is generally safe within Microsoft 365, careful management is necessary to avoid phishing risks or policy violations.
How do I enable and start sending mail from an alias in Outlook and Exchange?
To enable and use sending mail from an alias, follow these steps:
- Admin setup: Make sure users have aliases set up in Exchange Online or Azure AD. You can add aliases through the Microsoft 365 admin center or PowerShell.
- Enable the feature (if not already enabled):
Set-OrganizationConfig -SendFromAliasEnabled $true- User experience in Outlook on the web: When composing a new email, click the From field dropdown. Your aliases should appear alongside your primary address. Select the alias you want to send from.
- User experience in Outlook desktop: Use a version of Outlook that supports sending from aliases (generally recent versions). When composing a message, click the From button to see and select your available addresses, including aliases.
- Send the email: Write your message as usual and send it. The recipient will see the alias address as the sender.
If you don’t see your alias in the From dropdown, check with your admin to confirm the feature is enabled and aliases are correctly set up.
Admins can manage aliases or remove them via the Microsoft 365 admin center or PowerShell by modifying user proxy addresses.
Conclusion
With Microsoft now making sending mail from an alias generally available, you can simplify email workflows and represent different roles or teams without juggling multiple accounts. Check if your organization has enabled this feature and if your Outlook clients support it. Enabling it requires simple admin steps and integrates smoothly into the compose experience. Keep in mind your organization’s security policies and ensure your domain’s email authentication is set up correctly. This update reduces complexity and improves clarity across your Microsoft 365 environment.
Frequently Asked Questions
Can I send from any alias I want once this feature is enabled?
You can only send from aliases configured on your user account in Exchange Online or Azure AD that your organization allows. Admins control which aliases are available for sending.
Does sending from an alias affect email deliverability?
Generally, it does not. Because aliases share the same domain and mailbox, emails sent from aliases pass standard authentication checks like SPF, DKIM, and DMARC if the domain is properly configured.
Is this feature available in Outlook mobile apps?
Outlook mobile apps may not fully support sending from aliases yet. The feature is mainly supported in Outlook on the web and recent desktop versions.
Do I need admin permissions to enable sending from alias?
Yes, enabling this feature tenant-wide requires Exchange Online admin rights. Users only need configured aliases once the feature is enabled.