Office 365 Send Email from Alias or Proxy Address

How to let Exchange Online users send email from an alias or proxy address, using the admin centre or PowerShell with the current EXO V3 module.

Office 365 Send Email from Alias or Proxy Address

A mailbox often has more than one address, such as a personal address plus info@ or an old domain kept as a proxy address. Users then want to reply from the address the customer actually wrote to. In Exchange Online you cannot send email from an alias out of the box, because the setting that allows it is off by default. Here is how I switched it on in 2022, and what has changed since.

Why it happens

Exchange Online has an organisation-wide setting called SendFromAliasEnabled. Until an administrator turns it on, users cannot send messages using their aliases (proxy addresses). Microsoft first released the feature as a public preview. It is now generally available, so it is fully supported.

The parameter exists only in the cloud service. On-premises Exchange does not have it.

Fix 1: Turn it on in the Exchange admin centre

This is the quickest route if you only manage one tenant.

  1. Sign in to the Exchange admin centre at admin.exchange.microsoft.com with an Exchange administrator account.
  2. Open Settings → Mail flow.
  3. Turn on Turn on sending from aliases and save.

Fix 2: Use PowerShell to send email from alias addresses

My original method was to connect to Exchange Online and run one cmdlet:

Set-OrganizationConfig -SendFromAliasEnabled $true

That cmdlet and parameter are still current in Microsoft's Set-OrganizationConfig reference. What has changed is how you connect.

Update: Remote PowerShell for Exchange Online has been retired. REST API connections replaced it in October 2023. All tenants must now use the Exchange Online PowerShell V3 module with Connect-ExchangeOnline, without the -UseRPSSession parameter. Old scripts that build a remote session will no longer work.

The current steps are:

  1. Open PowerShell and install the module (skip this if it is already installed):
Install-Module -Name ExchangeOnlineManagement
  1. Connect with an admin account:
Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com
  1. Record the current value before you change it:
Get-OrganizationConfig | Format-List SendFromAliasEnabled
  1. Enable the feature:
Set-OrganizationConfig -SendFromAliasEnabled $true
  1. Disconnect when you have finished:
Disconnect-ExchangeOnline -Confirm:$false

How to check it worked

  1. Run the check again. It should return SendFromAliasEnabled : True:
Get-OrganizationConfig | Format-List SendFromAliasEnabled
  1. Be patient. Microsoft says the change can take up to 60 minutes to take effect in your tenant.
  2. Test with a real user. In Outlook on the web, show the From field, enter one of the user's aliases, and send a message to an external mailbox you control. Check that the message arrives showing the alias as the sender, and that replies go back to the alias.

Cautions before you switch it on

This setting changes nothing in mailbox data, but it applies to the whole organisation. Treat it as a tenant-wide change.

  • Note the original value. Step 3 above gives you a record. To roll back, run Set-OrganizationConfig -SendFromAliasEnabled $false.
  • Hybrid environments. If outbound mail passes through on-premises Exchange servers, the alias address may be rewritten to the primary address. Test this path specifically.
  • Shared mailboxes. Outlook desktop does not support sending from an alias of a shared mailbox. Users may need Outlook on the web for this.
  • Rules. Microsoft warns that journaling, routing or other rules that do not take aliases into account may not behave as expected. Review any rule that matches on sender address.
  • Other domains. This point comes from general practice rather than Microsoft's article on the feature. If an alias uses a different domain, check that the domain has SPF, DKIM and DMARC set up correctly. Otherwise mail sent from it may fail delivery checks or land in spam.

Quick checklist

Step Done?
Current value recorded ☐
Connected with Connect-ExchangeOnline (V3) ☐
SendFromAliasEnabled set to True ☐
Waited up to 60 minutes, then tested externally ☐
Hybrid routing, shared mailboxes and rules reviewed ☐
SPF, DKIM and DMARC checked for alias domains ☐

The core fix has not changed since 2022: it is one setting, either a toggle or one cmdlet. What has changed is the connection method, so update any old scripts to the V3 module. Test the hybrid and shared mailbox cases before you tell users the feature is ready.

Sources & further reading

  1. Set-OrganizationConfig (ExchangePowerShell) – Microsoft Learnlearn.microsoft.com
  2. Connect-ExchangeOnline (ExchangePowerShell) – Microsoft Learnlearn.microsoft.com
  3. Sending from email aliases – General Availability (Microsoft Exchange Team)techcommunity.microsoft.com
  4. Sending from email aliases – Public Preview (Microsoft Exchange Team)techcommunity.microsoft.com
  5. Deprecation of Remote PowerShell in Exchange Online (Microsoft Exchange Team)techcommunity.microsoft.com
  6. Send email from aliases in Exchange Online – 4sysops4sysops.com

📝 First written from my own work in 2022; updated and expanded in November 2026 with AI assistance, keeping my original fix. Spotted something wrong? Tell me.

Akam Omer
Written by

Akam Omer

IT leader, engineer and security specialist from Erbil with 20+ years across higher education, telecoms, healthcare and government. Founder of BulkSMSIraq, VerifyWay and Kurd.ai.