fbpx

Send email from alias

Introduction

One of the most long awaited and requested features in Exchange Online is the ability to send from an alias (proxy) address. Until recently (roadmap) (roadmap), it’s only been possible to receive email using an alias. There are many use cases for this feature, which in it’s absence, has required the use of additional mailboxes, typically user or shared mailboxes, as an alternative approach. For example, when a company has multiple domain names and a user is required to send and receive email from each.

With send as alias enabled, administrators can avoid the overhead of creating additional mailboxes when a user needs to send and receive from an email address other than their primary address. Additional mailboxes incur admin overhead, require support to configure in Outlook and create additional requests for helpdesk when setting up new users. With send as alias enabled, administrators can reduce the support overhead and achieve a better experience for their end users.

By default, send from alias is disabled and administrators must enable it to use the feature. We recommend enabling this feature for all tenants to create a consistent experience for your customers.

This MSPMagic setting allows you to configure send from alias to be either enabled (recommended) or disabled.

User Impact

Low – Enabling send from alias has little to no user impact.

Parameters

Enabled – True/False

Admin Portal Reference

Not available in admin portal

PowerShell Reference

To enable

Set-OrganizationConfig -SendFromAliasEnabled $true

To disable

Set-OrganizationConfig -SendFromAliasEnabled $false

The SendFromAliasEnabled parameter allows mailbox users to send messages using aliases (proxy addresses). It does this by disabling the rewriting of aliases to their primary SMTP address. This change is implemented in the Exchange Online service. At the same time, Outlook clients are making changes to natively support aliases for sending and receiving messages. Even without an updated client, changes in behavior may be seen for users using any email client as the setting affects all messages sent and received by a mailbox.

Set-OrganizationConfig (ExchangePowerShell) | Microsoft Docs

Further details – Set-OrganizationConfig (ExchangePowerShell) | Microsoft Docs

Additional Notes

The send from alias feature can take up to 24-48 hours to work after enabling the setting.

If Action is set to Notify

We report the setting as compliant if the setting matches the enabled value as set by the parameter.

We report the setting as non-compliant if the setting does not match the enabled value as set by the parameter.

If Action is set to Enforce

We report the setting as compliant if the setting matches the enabled value as set by the parameter.

We report the setting as compliant-fixed if the setting does not match the enabled value as set by the parameter and we adjust it to match.

Get Started!

The first three tenants are free! No credit card required.

Sign Up