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)

1. Go to the Azure Portal
2. In the top search bar, type "App registrations" and select it
3. Click "New registration"
4. Fill in the following:

• • Name: SuperSend (or any name you prefer)
  • Supported account types: Choose Single tenant
  • Leave the Redirect URI blank

5. Click "Register"
   You will be redirected to the app's overview page

Step 2: Generate a Client Secret

1. In the left menu, click "Certificates & secrets"
2. Under "Client secrets," click "New client secret"
3. Add a description like "SuperSend Secret"
4. Set an expiration (for example, 6 or 12 months)
5. Click "Add"
6. 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:

Step 4: Create a Communication Services Resource

1. In the Azure Portal, search for "Communication Services"
2. Click "Create"
3. 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)

4. Click "Review + Create," then click "Create"

Step 5: Create an Email Communication Service

1. Navigate back to the Azure Portal
2. Search for "Email Communication Service"
3. Click "Create"
4. Fill out:

• • Name: e.g., supersend-email
  • Region: Global (works across regions)
  • Data Location: Match your region (e.g., United States)

5. Click "Review + Create," then click "Create"

Step 6: Connect a Custom Domain

1. Go to your Email Communication Service
2. Select "Provision domains"
3. Click "+ Add domain" and choose "Setup a custom domain"
4. Enter your domain (e.g., yourcompany.com) and confirm
5. 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:

1. Go to your Email Communication Service
2. Click into your verified domain
3. Navigate to "MailFrom addresses"
4. Click "+ Add"
5. Enter:

• • MailFrom: e.g., kurtis@yourdomain.com
  • Display Name: e.g., Kurtis from SuperSend

6. 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:

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