Azure not Providing ALIAS record after validating Custom domain and after CNAME has been successfully propagated on Domain provider.

Question

Azure not Providing ALIAS record after validating Custom domain and after CNAME has been successfully propagated on Domain provider.

Oluwaseun Deborah Adebayo 0

CNAME

CNAME 4

CNAME 3

CNAME 2

Hello Fams,

I need help in getting past this stage,

I have created a static web app on my MCT Azure subscription, my custom domain has been added to a different M365 tenant, but I added the custom domain to my Azure using the "custom domain on other DNS" option, I added the CNAME record provided by Azure on my DNS provide, and the custom domain was validated on Azure, it's been over 72 hours, and Azure is yet to provide the ALIAS record to make me complete this configuration. I will appreciate help from the experts. Kind regards.

Oluwaseun Deborah Adebayo 0 Reputation points

2026-07-02T13:01:23.3233333+00:00

@Aditya N thank you for your response, the domain shows it is validated on Azure and it marks green. Is it possible you assist me on a screenshare via google meet ?
Golla Venkata Pavani 6,190 Reputation points Microsoft External Staff Moderator

2026-07-02T20:58:53.1566667+00:00
Hi @Oluwaseun Deborah Adebayo

Thank you for providing an update.

You have correctly added the ALIAS record (@ > lemon-ocean-0ac6eb603.azurestaticapps.net). However, the domain is still showing a 404 because Azure has not yet fully validated the domain ownership and completed certificate binding.
Recommended Steps:

Remove the existing custom domain in the Azure portal (under your Static Web App > Custom domains). This is safe.

Re-add the custom domain:

Click + Add > Select Custom domain on other DNS provider.

Enter your domain (synexil.com).

In the validation step, select TXT as the hostname record type.

Click Generate code to get the verification value.

Add TXT records for validation (as per Microsoft’s instructions for apex + subdomain):

Create a TXT record with host: _dnsauth.www and the value provided by Azure.

For the apex domain, Microsoft also recommends a separate validation path using the _dnsauth prefix (often @ or _dnsauth depending on exact prompt).

Keep your routing records active:

Leave the ALIAS record for @ pointing to lemon-ocean-0ac6eb603.azurestaticapps.net.

Leave the CNAME for www pointing to the same hostname.

Wait for propagation (DNS changes can take time, up to 72 hours in some cases, though validation is usually faster).

Once validation succeeds, Azure will automatically handle certificate issuance and binding. The 404 error typically occurs when the domain is not yet fully bound or the certificate is not provisioned.

Note on the extra TXT record: The SPF record (v0spf1 include:amazonses.com ~all) is unrelated to Static Web Apps hosting and can remain.

Reference:
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain
https://learn.microsoft.com/en-us/azure/static-web-apps/apex-domain-external
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain#zero-downtime-migration

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.

2 answers

Your answer

Oluwaseun Deborah Adebayo 0 Reputation points

2026-07-02T13:01:23.3233333+00:00

@Aditya N thank you for your response, the domain shows it is validated on Azure and it marks green. Is it possible you assist me on a screenshare via google meet ?

Answer 1

TP 158.6K Volunteer Moderator

Hi,

Please sign-in to your Namecheap account and add ALIAS record, as below:

Type: ALIAS Record

Host: @

Value: lemon-ocean-0ac6eb603.azurestaticapps.net

TTL: Automatic

User's image

After saving the new record, please wait 2-3 minutes and then test your site using web browser.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Oluwaseun Deborah Adebayo 0 Reputation points

2026-07-02T16:15:22.7+00:00

@TP thank you for your help, I will do this and share the result with you as soon as possible. Thank you.
Oluwaseun Deborah Adebayo 0 Reputation points

2026-07-02T16:21:49.07+00:00

I have added the ALIAS record; I will give it some time and see if it works.
TP 158.6K Reputation points Volunteer Moderator

2026-07-02T17:08:49.8466667+00:00

I checked and the alias record is correct, but your SWA hasn't completed the process of provisioning the custom domain, issuing certificate, binding certificate, etc. You may need to delete synexil.com custom domain and re-create it.

Leave alias record as-is.

Before adding synexil.com custom domain back, delete the "_hdsixzuvtoz9imyholjmwf1gq82ha3n" TXT record from Namecheap. Optional but recommended: wait 30 minutes for TTL of this record to expire before proceeding.

Add the synexil.com domain back in Azure portal, click to generate new code for TXT record. This time, create 2 TXT records, detailed below:

Type: TXT Record

Host: _dnsauth.www

Value: <newly-generated code from Azure portal>

TTL: 5 min

Type: TXT Record

Host: @

Value: <newly-generated code from Azure portal>

TTL: 5 min

Please see below article for reference:

https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain#zero-downtime-migration

After creating the new TXT records, your custom domain should complete provisioning with proper certificate, etc., within about 15-45 minutes or so, depending on if the previous TXT record is still cached (it has TTL of 30 minutes).

Please let me know if anything above is unclear.
Oluwaseun Deborah Adebayo 0 Reputation points

2026-07-02T17:19:57.5266667+00:00

I have added the ALIAS record; I will give it some time and see if it works.

still not working @Aditya N @TP after generating the first TXT, how do I generate the second TXT? I have deleted the domain and want to re-add it to Azure. Also, I saw a TXT record on my namecheap with value as v0spf1 include:amazonses.com ~all I am not sure how that got there
TP 158.6K Reputation points Volunteer Moderator

2026-07-02T21:23:33.49+00:00

@Oluwaseun Deborah Adebayo For the second TXT record, just use the same verification code as the _dnsauth.www record. the _dnsauth should be enough, I was having you create both as an extra measure.

Please give it a try and reply back here.

Thanks.
Oluwaseun Deborah Adebayo 0 Reputation points

2026-07-03T12:13:53.28+00:00

@Aditya N @Golla Venkata Pavani @TP I appreciate you all for your support, I have been able to launch the web app, here is the url https://synexil.com kindly view on PC and Mobile and give your feedback using the Send us message field and the email icon on the bottom right. Also, I want to ask, is it possible for the site to launch using www.synexil.com because when i tried www.synexil.com, it returned error 404, but with https://synexil.com it was successful.
Aditya N 2,990 Reputation points Microsoft External Staff Moderator

2026-07-03T14:01:22.68+00:00

Hello @Oluwaseun Deborah Adebayo

Glad that it launched. I have checked just now its working.

synexil.com is apex domain. The setup was done for apex domain. That's why https://synexil.com works.

www.synexil.com is subdomain joined.

https://learn.microsoft.com/en-us/azure/static-web-apps/apex-domain-external

If you want to use subdomain i.e www.synexil.com then you can forward your apex domain to www subdomain. Once you sign in to your account with your registrar, look for domain forwarding options.

Answer 2

Hello @Oluwaseun Deborah Adebayo

Thank you for reaching out Microsoft Q&A. It looks like domain verification failed. In the provided screenshot comprises of your apex domain "synexil.com"

Please check below

In the Azure Static Web App → Custom domains, re-open the validation step and make sure you have the exact TXT token Azure generated for your apex domain.
Go to the place where the domain is truly authoritative
Add the TXT record there:
- Type: TXT
- Host/Name: @
- Value: the exact TXT code generated by Azure Static Web Apps
- Save
Return to the Azure portal → Static Web App → Custom domains and use Refresh/Retry validation (or delete/re-add the domain if needed).
If DNS propagation is involved, give it time, but the key is: the TXT must be visible from the authoritative DNS.

If still didn't work then

Create a DNS zone for your domain in Azure.
Update your domain registrar's nameservers to point to Azure DNS nameservers.
In Azure Static Web Apps → Custom domains, add the domain using Azure DNS option