Support for Dynamic '+' Email Aliases in Office 365
I am familiar with using a plus sign following my email alias to create dynamic unique addresses for a Gmail account. e.g. email@example.com will arrive at my Gmail mailbox, where I can then apply rules based on the 'To:' address. See this page for details: https://support.google.com/mail/answer/22370
I tested this on my Office 365 address and it works, but only for email addresses in my parent domain. Using the aliases on subdomain addresses results in a 'recipient not found' NDR.
Does anyone out there have more information on this feature or if it even is one for 365 / Exchange?
I’m pleased to announce that the plus addressing feature is now available for Exchange Admins to enable. This can be done through Powershell using the following command:
Set-OrganizationConfig -AllowPlusAddressInRecipients $true
For instructions on how to use Powershell, you can find out more here:
The setting may not instantly take effect so please expect a delay before you can start using plus addresses.
The Exchange Transport team
Nem Schlecht commented
And it works with "@live.com" accounts, but not with our O365 Tentant. Frustrating.
That is not even a feature, it's a RFC compliance bug. MS somehow has plenty of dev time to add gizmos and promoted products but not for bugfixes to core features.
Thinking about going back to GSuite because of this. COMPLETELY ridiculous that paying users don't have this and free users do.
Tim Phang commented
As an exchange admin you can set this up for specific addresses. Follow the instructions in:
https://durdle.com/2015/01/11/office-365-email-suffix-matching/ and change the match rule in step 6 to be something along the lines of:
This will catch "firstname.lastname@example.org" and redirect it to the appropriate mailbox. This will need to be configured for each user who needs the functionality. For a team of developers to be able to use for testing, I'd recommend creating a shared inbox and applying the rule there.
Wil Stevens commented
Good lord I need this, and my company is owned by Microsoft!
Very much needed
Scott Carlow commented
A bit late, but to the person who asked this:
"The E-mail standard says that comments can be included by surrounding them in () at the beginning or end of the local part. Example:
- or -
Has anyone tried this with 365?"
You are referencing RFC822, which was made obsolete be RFC2822. "Comments" are referring to things like the friendly name of a person or system name, and that syntax was replaced with addr-spec (e.g. [Comment or folding whitespace] "<"local@domain">". So in any case, this is not subaddressing, but addressing syntax.
That said, It's mind boggling that outlook.com implements this but not Office 365. While 365 accepts messages from addresses that use subaddressing and you can add subaddresses to mailboxes via Powershell and ECP, the implementation is quite poor especially when compared to their own *consumer* product. I am extremely surprised that Business and Enterprise clients even need to ask for this.
UserVoice team, keep in mind that this request is also in the Office 365 Admin suggestion page with over 1100 votes.
This option is a must for user that migrated from GSuite / GMail.
Please add "Plus Addressing" in office 365.
It's embarrassing to use gmail for this service while selling office365.
Bellamkonda Bharat Kumar commented
I used this "+" sign technique for dev testing with gmail. Add it to office 365.
We once wanted to use Office 365 and startet with configuration, but then realised there's no support for + adressing. That's really bad, cause we couldn't use office365 then with all other benefits.
We will sorely miss this feature now that we are with exchange. Please add this. Our development team has used this extensively and now we'll have to use an alternate email service to continue using it.
Paul Chapman commented
I find it totally ironic that Outlook.com free email service supports RFC 5233 sub addressing, but not the paid Office365. Go figure.
Not having support for this is turning out to be a real pain for folks "upgrading" from G Suite to O365. Not only is RFC 5233 not supported in O365, but addition of aliases with "+" signs in them is also not supported, so using aliases as a workaround is even out!! #fail
Kris Barnhoorn commented
Please add support for subaddressing.
Andy Doyle commented
Come on Microsoft... you already have this working for Hotmail/Outlook accounts and these sit on Office 365 now.
This is dumb that it is not supported.
We need this!
It's really time this gets added. It's a great way to find out when a company has sold your email address.
Please support this standard.
Jason Hoos commented
We have system needs that require our QA department to be able to generate unique email addresses on the fly, and they are all using personal Gmail accounts to do this via RFC5233 because we can't do it in O365. We're actually at the point of putting a Postfix instance on an alternate domain to do address rewriting to get our users to stop using Gmail to do this.
Please support this in O365 natively so we can stop with the ugly workarounds!