Alternative methods for custom domain validation in Azure Front Door?

Question

I' m thinking of putting Azure Front Door in front of a SaaS application. Customers can set up they own "vanity domains" (custom domains) by creating CNAME records at their DNS providers. For example:

hello.company.com -> CNAME -> hello.saasplatform.com

So that they can use hello.company.com instead of hello.saasplatform.com/company (which is provided by default).

The problem with AFD is that when adding a custom domain, it isn't enough for the customer to create a CNAME record, they must also create a TXT record for the validation? For us this is a showstopper and I was just wondering if there are other ways of validating custom domains?

Would it for example be enough to put the TXT record at our DNS provider?

Edit: Looking at the competition, both CloudFlare and AWS offer other types of validation, that doesn't require setting up TXT records.

Answer 1

Hello @Joel , welcome to the Microsoft Q&A forum.

For Azure FontDoor Premium/Standard tier custom domain validation is done using TXT records. You can explore Azure FontDoor Classic tier where you can validate a custom domain using CNAME record, you can go through this documentation for additional details. Here is the documentation for overview of Azure Front Door tiers.

Hope this helps! Please let us know if you have any additional questions. Thank you!