This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 57.99999999999999%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBP%3C/text%3E%3C/svg%3E)
Hello, I have an Azure App which I am trying to set up MailerSend for to be able to use their API. To do so, they require setting up several DNS records for the domain. I have created an Azure DNS Zone for my app and added the required records and double and triple checked that they are named properly (both apex and specified names) and contain the requested values. But, on attempting to verify, it fails saying that the records do not match(thinking it just can't see the records altogether). Does anyone have experience setting up a 3rd party SMTP client this way? I'm not sure where to go from here.
For reference, the three records are a SPF TXT record, a DKIM TXT record, and a RETURN-PATH CNAME record.
@Brian Prinjinski are you still getting verification errors? Is your custom domain for your app service already verified? How do your records look in Azure DNS?
If you're continuing to see this issue and need further assistance, please feel free to comment down below.
I am quite sure the issue is NOT the DNS set-up, but Azure blocking outbound traffic on port 25: https://learn.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity
@Bas Pruijn you are correct. In order to guarantee outbound traffic on port 25, you'll need an enterprise agreement as you've rightly discovered. With that restriction lifted, you'll be able to use on an ASE. I would check the diagnostics of app service though to be sure though. Since I don't believe MailerSend offers a relay service, maybe there's an API that you can leverage from your app service.