This article describes how to add an alias email address to a user's Microsoft Office 365 account by using Microsoft Exchange Online and how to configure Microsoft Outlook to send email messages as this alias. These steps involve setting up a "dummy" POP3 account by using the user's alias.
In Office 365 for professionals and small businesses
1. Open Outlook with the Office 365 profile.
2. Click File, then click Account Settings, and then click Account Settings.
3. On the E-mail tab, click New.
4. Click Manually configure server settings or additional server types, and then click Next
5. Click Internet E-mail, and then click Next
6. Enter the following information:
7. Click More Settings.
8. Click the Outgoing Server tab, and then click to select the My outgoing server (SMTP) requires authentication check box.
9. Click the Advanced tab, and then click to select the This server requires an encrypted connection (SSL) check box.
10. In the Outgoing server (SMTP) box, type 587.
11. In the Use the following type of encrypted connection list, click TLS.
12. Under Delivery, set the delivery options that you want.
14. Click Next. The account settings that you entered are tested. When these tests are completed, click Close.
15. Click Finish.
A POP3 account is created for the alias. However, you must also have to make sure that this POP3 account does not send and receive items in Outlook.
Note To change whom the email messages are sent from (either from the user's aliases or primary address), you may have to enable the From field in Outlook. To do this, follow these steps:
Microsoft Office 365 for Enterprise
Another option is to use a Distribution List to "hold" the email alias, then permission send as rights to the new DL. A detailed guide on how to do this can be found here:
Video www.youtube.com/watch might be useful for new outlook user who wants to know how to create and delete email alias
These instructions do not work if the company has Active Directory sync.
There does not appear to be a Manage option Under Exchange in Office 365 for Enterprises. I keep seeing this as a choice in the various solutions to adding an alias/proxy address but it is not there.
As mentioned in another comment, this does NOT work for tenancies using federated authentication (ADFS and DirSync). How do we set these properties in this scenario?
Using 365 that was implemented in 2013. There is no selection for "details" and no ability to add a secondary email address. Quite disappointed at how difficult 365 is to administer in comparison to Google Apps!
i want to confirm that this doesn't work on hybrid, the customer is asking, do we have a link that says so clearly
i tested it and it doesn't work
This is a stupid way of handling aliases because a business model was baked in to the pie.
Info is out of date e.g "Users & Groups" is now Recipients; "Details" is now double click on Display Name
These instructions don't help at all. I have Enterprise E1. Come on MS - where do we add an alias?!?!
ad the alias using smtp
The UI has changed. For Office 365 Small Business, see http://office.microsoft.com/en-us/office365-suite-help/add-an-email-alias-to-a-user-account-HA104072264.aspx?redir=0. For Office 365 Midsize and Enterprise, see http://technet.microsoft.com/en-us/library/bb123794(v=exchg.150).aspx.
Hi, how can I see when a mail comes IN, that its the mailalias, that has been used? Today I have several aliases, but all of them, is just called what my primary account is called. PLease avice. Thanks. Best regards, Michael
This does not work. No matter what is put in the From field the default address is always inserted by the mail server. Don't waste your time trying this.
I just performed these steps using my MSDN O365 Account (E3 type) and was able to successfully send as one alias, and then switch to the alternate account and send as another alias. Verification was done by sending two messages to a Lotus Notes account at another domain and expanding the 'From Details' to check the addresses. Each message had a different from address. The outstanding question I have is whether these aliases can cross over between different email domains (all managed within the same O365 tenant). I can't test that with MSDN.