Build Communication Services email and SMS configs with custom domains, sender addresses, phone numbers, and opt-out management.
Build Communication Services email and SMS configs with custom domains, sender addresses, phone numbers, opt-out management, and event subscriptions.
Required Fields
resourceNameresourceGroupdataLocationOutput will appear here...The builder validates that resourceName, resourceGroup, and dataLocation all resolve before accepting the JSON as a plausible combined Communication Services configuration spanning email and SMS capabilities; it can't verify the DNS records are actually published and correctly propagated, or that phone number provisioning requests will actually succeed for the requested capabilities and country, those are only confirmed against the live Communication Services resource provider and real DNS lookups.
Build an Azure Communication Services configuration spanning email (custom domain with SPF/DKIM DNS verification and a suppression list for bounced/complained addresses) and SMS (phone number provisioning with capabilities and keyword-based optOutManagement). Both SPF and DKIM DNS records need to actually be published and verified before the custom email domain can send mail through ACS, and separately, optOutManagement's keyword lists (STOP/UNSUBSCRIBE/QUIT for opt-out, START/SUBSCRIBE for opt-in) are enforced automatically by the platform once configured, meaning a phone number receiving one of those exact keywords stops receiving further SMS regardless of what the application's own code does, a compliance-relevant behavior that's easy to overlook when testing only the happy path of an SMS campaign.
Verify SPF and DKIM records are actually published and correctly formatted before assuming custom domain email is production-ready, domain ownership verification alone doesn't guarantee good deliverability, missing or malformed SPF/DKIM is a common cause of custom-domain email landing in spam.
Don't rely on application-level opt-out checking as the only compliance safeguard, ACS enforces configured opt-out keywords at the platform level regardless of application code, but verify the keyword list actually covers the variations your recipients are likely to send (case sensitivity and exact matching considerations).
Subscribe to delivery/bounce event types via eventSubscriptions proactively rather than only checking delivery status reactively through the portal, automated monitoring catches a deliverability problem (a sudden spike in bounces, say) faster than periodic manual checks.
No, that TXT record is specifically for proving domain ownership, separate from the SPF and DKIM records which are what receiving mail servers actually check to validate that the mail is legitimately authorized to be sent from that domain and hasn't been tampered with. All three (ownership verification, SPF, DKIM) need to be correctly published for the domain to both be usable and to have good deliverability, missing SPF/DKIM specifically tends to result in mail landing in spam even if sending technically succeeds.
Yes, once optOutManagement is configured with keyword lists, the platform enforces the STOP-equivalent keywords automatically at the ACS level, a recipient texting one of the configured optOut keywords stops receiving further messages regardless of what the sending application's own code does or doesn't check for, this is a platform-enforced compliance behavior, not something that depends on application logic being correct.
The suppression list behavior and scope depend on how it's configured (the example shows a named list, global-suppression, suggesting an account-wide list), check whether your configuration intends a shared suppression list across all sender addresses in the domain or something scoped more narrowly, since a bounce on one sender address should generally suppress that address account-wide, not just for the specific sender it originally bounced from.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.