Unable to remove default domain email address added to shared mailbox / user mailbox as alias / Unable to delete email alias
some of the reasons microsoft doesn't allows us to remove the alias email address with the default domain.
i created a shared mailbox called firstname.lastname@example.org. when i created that it automatically created an email alias as email@example.com by default. Now i tried to create an additional shared mailbox firstname.lastname@example.org but cannot do so as the address is used by email@example.com.
When i try to delete the alias from the first mailbox the settings seems to be saved without any error message, but when i reopen the dialog box the alias address still there. when i try to edit the alias from firstname.lastname@example.org a new alias is created but the original one stays there.
i contacted Microsoft support but no luck. (SR: 616031993661261)
i suggest Microsoft to look into this issue with high priority. i suggest to create random email alias if the email address exist so that you can solve this issue.
Hope to see the changes soon.
Please refer below URL's everyone facing this issue
Thanks and Regards
Change username work for me as that alias was set as username for that mailbox.
****** Solution !!!!!!!!!!!!!!!!!
Change O365 username and try again. It will work this time!
Chris Johnson commented
I was able to correct this by going into 365 Admin Center, then go to Azure AD, click on the name, and edit the user name. Then go back into 365 or Exchange Online and remove the unwanted email address. levelcis.com
[Deleted User] commented
Thanks a lot =)
Jake Vanderrol commented
I found that if you convert the shared mailbox to a regular user (there is a link in the exchange admin panel for the account) you will find that the email alias you are trying to remove is the account's primary login. Change that login, remove the alias and convert back to a shared mailbox and you're good to go!
Thank you J. Bunne, lifesaver!
Thank you, J.Bunne. So helpful!
Chris Cadge commented
Cheers J.Bunne - worked for me :)
Joshua M. commented
Thank you J.Bunne! That seems to have worked for ours.
Hello, you have probably found your own solution for this issue by now. But for anyone else having this problem I solved it but using the following command in Powershell:
#This value for "MicrosoftOnlineServicesID" is the value of the MailBox property "WindowsLiveID" https://msdn.microsoft.com/en-us/library/ee423637(v=exchsrvcs.149).aspx
#We want to change this to our secondary domain to enable the removal of the default primary domain smtp alias
Set-Mailbox email@example.com -MicrosoftOnlineServicesID firstname.lastname@example.org
"WARNING: UserPrincipalName "email@example.com" should be same as WindowsLiveID "firstname.lastname@example.org", UserPrincipalName should remain as"email@example.com".
#Confirm the removal by issuing this command
Get-Recipient firstname.lastname@example.org | Select Name, EmailAddresses
Michael Burke commented
If a user mailbox already exists for finance@domainA.com, and they want a Finance shared mailbox, I just create finance1@domainB.com shared mailbox. Then go back and edit the default SMTP to finance@domainB.com. Unfortunately finance1@domainA.com will still be in place for now. That's the best work around I can come up with for now.
Alain Gouber commented
The same goes for us.
However, the other way around it works. If the address *@primarydomain.com does already exists, it will not be created in the new mailbox afterwards.
For now, we use a hidden distribution list, were we first create the not used alias @primarydomain.com, so that when it is needed, we can create a single address from it.
Shawn Hoy commented
The issue in my case was that once the shared mailbox was created it assigned the USERID to <name>@defaultdomain.com. Once I went in and changed that domain to what I actually wanted it to be the changes seemed to stick.
Note that it still took a good five minutes after removing/saving that it accurately reflected the change.
I'm facing the exact same situation.... any solutions now?