MC1515939 High
Sending from Aliases
Summary AI-generated
Sending from Aliases is now generally available for Exchange Online, enabling users to send emails from any alias configured on their mailbox.
Suggested actions AI-generated
- Enable the feature via PowerShell or Exchange Admin Center Settings
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1423106 Introducing cross-tenant message recall in Exchange Online
- MC1243552 (Updated) High Volume Email for Microsoft 365 now generally available
- MC1526668 Change Optics Report
- MC1239176 (Updated) Outlook: Delimiter setting admin policy
- MC1247637 (Updated) Microsoft 365 Copilot: Draft and send Outlook email directly in Copilot Chat
- MC1469962 Change in sender email address for Copilot emails
Original post from Microsoft
[What and Why:]
We're pleased to announce that Sending from Aliases is now generally available for Exchange Online. We are continuing to investigate additional capabilities, including per-alias display names, further filtering and default controls, and calendar support post GA. For more details on the feature, review the blog post below.
[Rollout Schedule:]
Available now.
[Impact on Your Organization:]
Who is affected:
- Users and admins in organizations using Exchange Online.
What will happen:
- This feature allows users to send emails from any alias configured on their mailbox, improving flexibility and reducing the need for workarounds.
[Action Required/Recommendations:]
Admins can enable this feature via PowerShell or the Exchange Admin Center Settings.
Learn more: Sending from Aliases is now generally available
[Compliance considerations:]
No compliance considerations identified. Review as appropriate for your organization.
Additional details from Microsoft
- Summary
- Sending from Aliases is now generally available in Exchange Online, allowing users to send emails from any mailbox alias. Admins can enable it via PowerShell or Exchange Admin Center. Additional features are being explored, and no compliance issues have been identified.