Can WordPress send from a Microsoft 365 alias?

Yes, once a Microsoft 365 tenant has sending-from-aliases turned on and the alias is listed as a proxy address on the sending mailbox. Microsoft Exchange Online made that configuration generally available on October 7, 2026, after nearly five years in preview. For WordPress operators who send transactional mail as noreply@ or billing@ from a human mailbox, this is the first time the setup is officially supported rather than a workaround.

The feature replaces the dedicated-shared-mailbox workaround that used to be the standard way to carry a different From address on a Microsoft 365 setup. The shared mailbox is still the right shape in a few cases, covered at the end.

The two switches that have to be on

Tenant switch. A global admin runs this once in Exchange Online PowerShell:

Set-OrganizationConfig -SendFromAliasEnabled $true

The default is off: Microsoft’s Set-OrganizationConfig cmdlet reference documents $false as the default and says “aliases on messages sent or received are rewritten to their primary email address.” The setting is tenant-wide; Microsoft does not publish a propagation window, but third-party admins report changes taking anywhere from a few minutes to an hour. Confirm with Get-OrganizationConfig | Format-Table Name, SendFromAliasEnabled before testing a WordPress send.

A per-domain opt-out exists for tenants that don’t want one accepted domain to be sendable from aliases on another:

Set-AcceptedDomain -Identity example.com -SendingFromDomainDisabled $true

Check which domains allow alias sending with Get-AcceptedDomain | Format-Table DomainName, SendingFromDomainDisabled.

Mailbox switch. The alias has to exist as a proxy SMTP address on the mailbox the WordPress site authenticates as. In the Microsoft 365 admin center, open the user, then Mail, then Manage email aliases, and add the alias ([email protected]) to the mailbox the site uses for OAuth. An alias is a secondary SMTP address on a real mailbox; it isn’t a shared mailbox. The GA feature covers the alias case specifically.

Both switches have to be on. One without the other produces the same visible symptom: Exchange rejects the send.

Setting the From address in each plugin

Each of the three Microsoft 365 mailers has a From Email field and an override toggle. The toggle decides whether the mailer sends what the plugin configured or what wp_mail() was called with. The toggle matters because WordPress core, WooCommerce, and most forms plugins all pass their own From addresses through wp_mail().

WP Mail SMTP (the Microsoft 365 mailer is Pro-only). Set From Email to the alias and tick Force From Email. The plugin sends via Microsoft Graph. The official documentation states the mailer “supports sending emails from different users, shared inboxes, and groups” once those addresses are configured on the Microsoft side, and that to use a different sender you “add the email as an alias on your Microsoft account.” If the alias sits on the OAuth mailbox and the tenant switch is on, the configured From travels through.

FluentSMTP (free, via Microsoft Graph). On the Outlook/Microsoft 365 connection, Sender Email is the primary mailbox used during OAuth. The Force From Email (recommended) toggle rewrites any From supplied by wp_mail() to that Sender Email. For the alias to leave the site intact, leave Force From Email off and set the From either on the sending plugin’s From field or through the wp_mail_from filter; the Outlook handler then passes phpMailer->From straight into Graph’s /sendMail from field.

Post SMTP (free Office 365 socket, via SMTP). The socket authenticates with XOAUTH2 against smtp.office365.com on port 587 with STARTTLS. Set Email Address on the Message tab to the alias. The checkbox Prevent plugins and themes from changing this is Post SMTP’s equivalent of Force From Email; leave it on when you want the configured alias to win against a form plugin’s From, leave it off when you want each sending plugin’s From to pass through.

What breaks and how to tell

Three failure modes recur, in the order to check them:

• Tenant switch off. Exchange rejects the send. Post SMTP’s log shows the SMTP response 550 5.7.60 SMTP; Client does not have permissions to send as this sender. WP Mail SMTP’s and FluentSMTP’s logs show an HTTP 403 from Graph whose JSON body carries ErrorAccessDenied (or ErrorSendAsDenied for shared-mailbox Mail.Send.Shared tokens). The fix is the PowerShell command above; wait a few minutes for the setting to roll out.
• Alias missing from the mailbox. Same error strings. The From address is valid, but it isn’t a proxy on the authenticated mailbox. Add it in the admin center and wait a few minutes for directory replication.
• Plugin overriding the alias. The mailer log shows the message leaving with the mailbox’s primary address, not the alias you configured. In WP Mail SMTP, Force From Email isn’t ticked. In FluentSMTP, Force From Email (recommended) is on, or the sending plugin didn’t set a From and the connection’s Sender Email is the primary. In Post SMTP, Prevent plugins and themes from changing this is on and the Message tab still holds the primary address.

The strings to grep each plugin’s log for are different: 5.7.60 on the SMTP path (Post SMTP), ErrorAccessDenied or ErrorSendAsDenied on the Graph path (WP Mail SMTP, FluentSMTP).

When a shared mailbox is still the right answer

Alias sending inherits the primary mailbox’s authentication and reputation. If noreply@ sends from a human’s licensed mailbox, every bounce and every spam complaint lands against that human’s reputation, and the alias counts against the per-mailbox cap that the human is also consuming (Microsoft Learn, Exchange Online limits, as of October 2026: 10,000 recipients per day, 30 messages per minute). For a dedicated transactional sender (no human reading the inbox, discrete reputation, meaningful volume), a shared mailbox is still the right shape. Above a few thousand transactional messages a day, a dedicated transactional provider is better than either.

Short answer: alias for low-volume mail from a working mailbox; shared mailbox or a dedicated provider for anything the site depends on. See Can I use Outlook for my WordPress email? for the parent decision, and What is the best way to set up email on WordPress? when the volume outgrows what a human mailbox should carry.