I'm trying to see if I can associate multiple email domains to the same Azure Communication Service to be able to send emails from either one. Is this possible?

@Muriuki, Levi M Thank you for your response! Allow me to provide further clarification. With the Email Communication Service, you have the option to add multiple custom verified domains using the "Add domains" feature. However, when it comes to sending, managing, and tracking your emails in Azure Communication services, you can only connect and utilize one verified domain from your Email services resource. So, 1 domain resource to 1 ACS resource is the current limitation. The motivation behind is to enforce boundary around each application domains that is used for communication. Also, suggest you to send us an email with subject line “Attn:Sneha |thread title” to AzCommunity[at]microsoft[dot]com referencing this thread, I would like to understand better your usecase and solution on this. Hope this helps.

@SnehaAgrawal-MSFT : could you please let us know if this functionality is something we can expect in the next weeks? We do like ACS and want to stick to it, but creating a new ACS instance for every new tenant in a SaaS application is obviously a no-go...

Can we associate multiple domains to an Azure Communication Service?

Accepted answer

SnehaAgrawal-MSFT 19,921 Reputation points

2023-06-16T03:42:44.82+00:00

@Muriuki, Levi M

Thank you for your response! Allow me to provide further clarification. With the Email Communication Service, you have the option to add multiple custom verified domains using the "Add domains" feature.

However, when it comes to sending, managing, and tracking your emails in Azure Communication services, you can only connect and utilize one verified domain from your Email services resource.

So, 1 domain resource to 1 ACS resource is the current limitation. The motivation behind is to enforce boundary around each application domains that is used for communication.

Also, suggest you to send us an email with subject line “Attn:Sneha |thread title” to AzCommunity[at]microsoft[dot]com referencing this thread, I would like to understand better your usecase and solution on this.

Hope this helps.
Please sign in to rate this answer.
Michael Gressman 86 Reputation points

2023-06-16T18:43:59.91+00:00

I don't want to hijack Levi's question so please focus on answering whatever questions are posed there first.

I have been following this question because I am very interested in the answer for my scenario. I have a multi-tenant SaaS application. The application needs to send emails on behalf of each of the tenants. Mailchimp supports this via a feature known as subaccounts and Sendgrid uses subusers. We are currently doing this with a home built messaging platform, but I would much prefer to buy this feature rather than continue to support it in our own code and I was really hoping for an Azure solution since all of our other resources are already in Azure. It would seem the only way to make this work with ACS is to have multiple instances. One for each tenant. I currently have about 400 tenants which would mean 400 instances of ACS. We are managing our infrastructure via IaC so I am not worried about actually doing the work of spinning up and maintaining 400 instances, but my gut reaction is that 400 instances of any single resource may be the wrong solution. Can you confirm that a separate instance for each tenant is the recommended solution, no matter how many tenants my application needs to support?

Martin Dörig 25 Reputation points

2023-07-19T13:48:59.48+00:00

I'm currently building a system similar requirements as Michael, we have multiple tenants and it is very likely that they demand that notification emails are sent using their own domain name. Creating multiple ACS instances just feels wrong...

Jakub Pernica 215 Reputation points

2023-10-31T09:58:15.5666667+00:00

@Michael Gressman Martin Dörig

Hey guys, I was interested in learning what approach did you go with. Are you managing multiple instances of ACS? If so, have you encountered any limitations or other problems?

Peterson Salamat 11 Reputation points

2023-11-30T23:54:07.03+00:00

Yeah, we're also implementing a system similar to Michael and Martin's setup.

We would also need ACS to support multiple connected domains.

tstrong 45 Reputation points

2023-12-12T20:25:39.9633333+00:00

@Muriuki, Levi M

I agree with the others. It would be beneficial to have multiple domains available under one Communication Service.

Something that is misleading and would make oneself think that multiple domains per comm service is allowed, can be found on the Communication Service resource page. If you click on Try Email, the first question on the form (send email from) has a drop-box to select a domain. A drop-down box usually illustrates multiple choices.

I know, a bit condescending, but it seems like so many of the paths I take when trying to implement different azure resources end with a dead end and i have to go a different route or do some custom programming.

Ilias Michalarias 15 Reputation points

2024-04-29T12:00:01.6833333+00:00

is this for real? We also have a SaaS application with multiple tenants. Are we supposed to create a new ACS for every new tenant???

Why do you then even allow to add multiple provision domains on the Email Communication Service, in the first place ???

Jeremy Bradshaw 36 Reputation points

2024-06-17T11:33:51.27+00:00

This is so shortsighted. The fact that we already have to grant Entra ID apps access at the ACS resource level already makes it so we have 1 ACS resource to 1 Entra ID application/SPN. That is enough compartmentalization already right there! Why would we need to limit our apps to just 1 single domain? Instead we might have all different sets of requirements per application, where some send from multiple different domains, and others don't.

We have the ability to add the same domain into any number of different Email Communication Service resources, and then again we can add the same MailFrom addresses into any number of different ECS's verified domains too (e.g., DoNotReply@<domain> might be added to many of the ECS's, while Summer2024Contest@<domain> might only be added to a single ECS.

The design should be remain as 1 Entra ID app/SPN to 1 ACS to 1 ECS, and stop limiting it right there. Just let there be multiple domains in an ECS, each with multiple MailFrom addresses, and all of these things in the ECS be available to the ACS. Please reconsider this. I sent an email about this as well in hopes to get some traction.

Brent McAlpine 0 Reputation points

2024-07-02T05:25:14.18+00:00

We have the same issue as most everyone here. We are a Saas provider and do not want to have to add a new resource for every customer. It quickly becomes a logistical problem with the configuration of the services that need to connect to use the service.
Sign in to comment

Share via

Can we associate multiple domains to an Azure Communication Service?

1 additional answer