How to Connect Azure Communication Services (ACS) to SuperSend

This guide walks you through setting up your Azure account to send messages through SuperSend using Azure Communication Services (ACS). You'll create an App Registration, generate a Client Secret, create a Communication Services resource, authenticate your domain, and configure sender identities to complete the setup.

Prerequisites

Before you begin, make sure you have:
Access to the Azure Portal
Admin permissions in your Azure tenant

Step 1: Register a New Application in Microsoft Entra (Azure AD)

Go to the Azure Portal
In the top search bar, type "App registrations" and select it
Click "New registration"
Fill in the following:
Name: SuperSend (or any name you prefer)
Supported account types: Choose Single tenant
Leave the Redirect URI blank
Click "Register"
You will be redirected to the app's overview page

Step 2: Generate a Client Secret

In the left menu, click "Certificates & secrets"
Under "Client secrets," click "New client secret"
Add a description like "SuperSend Secret"
Set an expiration (for example, 6 or 12 months)
Click "Add"
Copy the Value immediately — this is your Client Secret
You will not be able to retrieve this again after you leave the page

Step 3: Gather Your Azure Credentials

Go to the "Overview" tab of your App Registration and copy the following:

Field	Where to Find It	Use in SuperSend
Application (client) ID	Overview section	Part of the Connection URL
Directory (tenant) ID	Overview section	Part of the Connection URL
Client Secret	Certificates & secrets	Input in SuperSend

Step 4: Create a Communication Services Resource

In the Azure Portal, search for "Communication Services"
Click "Create"
Fill out the form:
Subscription: Choose your Azure subscription
Resource Group: Create or select one
Resource Name: Choose a name (e.g., supersend-acs)
Data Location: Choose a region (e.g., United States)
Click "Review + Create," then click "Create"

Step 5: Create an Email Communication Service

Navigate back to the Azure Portal
Search for "Email Communication Service"
Click "Create"
Fill out:
Name: e.g., supersend-email
Region: Global (works across regions)
Data Location: Match your region (e.g., United States)
Click "Review + Create," then click "Create"

Step 6: Connect a Custom Domain

Go to your Email Communication Service
Select "Provision domains"
Click "+ Add domain" and choose "Setup a custom domain"
Enter your domain (e.g., yourcompany.com) and confirm
Azure will generate DNS records: SPF (TXT), DKIM1 & DKIM2 (CNAME), and optionally DMARC
Add these DNS records to your domain registrar (GoDaddy, Cloudflare, etc.). TTL can be set to 300–3600 seconds.

Step 7: Wait for DNS Propagation and Verification

Once the records are saved:
Wait 15–30 minutes (or up to 48 hours in rare cases)
Use tools like MXToolbox to confirm DNS is live
Return to Azure and click "Refresh" on the domain
Verification is complete when:
SPF status = Verified
DKIM1 + DKIM2 status = Verified
You will not be able to add senders until all records are verified.

Step 8: Add Sender Identity

Once SPF and DKIM are verified:
Go to your Email Communication Service
Click into your verified domain
Navigate to "MailFrom addresses"
Click "+ Add"
Enter:
MailFrom: e.g., kurtis@yourdomain.com
Display Name: e.g., Kurtis from SuperSend
Click "Create"
Now this sender address can be used in SuperSend.

Step 9: Construct the Communication Service Connection URL

Use this format:

<resource-name>.<application-id>.<tenant-id>

Example:

supersend-acs.12345678-abcd-1234-abcd-1234567890ab.87654321-dcba-4321-dcba-0987654321fe

Step 10: Enter Details Into SuperSend

In your SuperSend account, choose to add an Azure sender and fill in the following:

Field	What to Enter
Communication Service URL	<resource-name>.<client-id>.<tenant-id>
Client Secret	Paste the value from Step 2
Send As	e.g., Kurtis from SuperSend <kurtis@yourdomain.com>
Reply To	The email address to receive replies

Setup Complete

You're now set up to send messages via Azure using SuperSend.

Troubleshooting Tips

DNS propagation may take up to 48 hours
Use external tools to verify DNS record visibility
Ensure proper permissions (Contributor or Owner role) to modify sender identities
Refresh Azure after waiting if verification seems stuck
Contact support if you're unable to verify records or activate senders after propagation.

Updated on: 17/06/2025