Share via

Consolidating Email and SMS Under Azure Communication Services

Sharma, Ritika 345 Reputation points
2025-08-01T08:30:13.75+00:00

I’m looking to implement both email and SMS communication features for our application using Azure. I noticed that Azure provides both a general "Azure Communication Services (ACS)" resource and a more specific "Email Communication Service" blade in the portal.

Could you please clarify the following:

  • Can a single ACS resource be used to manage email, SMS, voice, and url-shortener functionalities together?
  • Is the Email Communication Service in the portal just a specialized view/setup of ACS Email, or is it a separate resource/service altogether?
  • For production usage, do you recommend using one ACS resource for all channels (email, SMS, url-shortener), or should they be managed separately?
Azure Communication Services

Answer accepted by question author

Divyesh Govaerdhanan 10,905 Reputation points MVP Volunteer Moderator
2025-08-03T17:03:00.9166667+00:00

Hello Sharma, Ritika,

Welcome to Microsoft Q&A,

Azure Communication Services (ACS) is designed to support multi-channel communication (SMS, Email, Voice/Video, Chat), but there are a few nuances to understand when it comes to resource consolidation and management practices.

  1. Can a single ACS resource be used to manage email, SMS, voice, and URL-shortener functionalities together? Yes, but with caveats. A single ACS resource can technically support multiple modalities, including:
    • SMS
    • Voice & Video calling
    • Chat
    • Email (requires domain verification & capabilities enabled)
    However:
    • Some capabilities (like Email) require separate configuration steps (e.g., setting up verified domains and DKIM for Email).
    • Features like URL Shortener are not natively part of ACS but can be built as an adjacent service via Azure Functions or Logic Apps.
  2. Is the “Email Communication Service” in the portal a specialized view/setup of ACS Email, or is it separate? It’s essentially a specialized blade/view for setting up ACS Email within the Communication Services umbrella. When you create an "Email Communication Service" in the Azure portal:
    • It still links to the same backend ACS resource model
    • It simply preconfigures your setup for email use (like domain management, DKIM, SMTP routing)
    So, it is not a separate service, just a tailored provisioning flow within the broader ACS framework.
  3. Should I use one ACS resource for all channels or separate them? Recommendation: Use a single ACS resource for most channels (Email, SMS, Voice) if:
    • You want centralized billing and access control
    • Your app serves a single domain/tenant
    • Your workload and throughput stay within ACS quotas
    Use separate ACS resources when:
    • You serve multiple tenants/clients with different compliance requirements
    • You want environmental isolation (e.g., dev/test/prod separation)
    • You require granular role-based access control (RBAC) per communication channel

For Reference,

https://learn.microsoft.com/en-us/azure/communication-services/overview

https://learn.microsoft.com/en-us/azure/communication-services/concepts/sms/concepts

https://muhammadimran-dev.medium.com/azure-communication-services-fbc5f8d84949

Please Upvote and accept the answer if it helps!!

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.