How can I add custom email addresses to my Azure communication service?
Asked by
3am shift swap
I just set up a communication service in Azure with a custom domain and verified it in my DNS settings. Everything looks good, but I'm stuck with just '[email protected]' as the sender address. I want to add more addresses, like '[email protected]', but the 'Add' button is grayed out. I'm on a pay-as-you-go subscription. Does anyone have tips on how to resolve this or why the button might be disabled?
Answers
I had to deal with something similar, but I found a great domain through Dynadotโs auction site. It wasnโt too expensive and included free email hosting, which sped up my setup. It might be worth checking there!
Reply to this answer
Note that sender usernames canโt be activated for custom domains with basic limits. You might need to raise a support ticket to request a quota increase. Hereโs more about it in [this guide](https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/email/add-multiple-senders?pivots=platform-azp#create-multiple-sender-usernames).
Reply to this answer
Yeah, the default setup gives you that no-reply address. If you want more custom emails like info@, you'll need to set up separate email hosting. I personally use Dynadot for my domainsโthey provide free email forwarding, so I can redirect addresses easily.
Reply to this answer
That grayed-out button issue is a known bug at the moment. A good workaround is to use PowerShell for adding sender usernames. Check out the instructions in this [link](https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/email/add-multiple-senders?pivots=platform-powershell). It's worked for quite a few users!
Reply to this answer
I've faced that problem too! It might be due to a missing certificate for the custom domain in Azure. Although I'm not 100% sure, you're right to consider PowerShell, AZ CLI, and other tools like ARM Templates or Terraform to add those email addresses.
Reply to this answer
Add your answer
Answers are reviewed before publication.
7bit.crc: I can vouch for this! I had the same issue and using PowerShell fixed it for me about a month ago.
BasaltFan: Thanks for the heads-up! I tried it and it worked perfectly!