While setting up custom domains URL for static web app Cannot add DNS record for alias because Microsoft DNS doesn't have option for alias and only cname

Question

While setting up custom domains URL for static web app Cannot add DNS record for alias because Microsoft DNS doesn't have option for alias and only cname

Constantin Dragomirov 0

At Microsoft 365 admin center -> Domains -> Manage DNS

While setting up custom domains URL for static web app Cannot add DNS record for alias because Microsoft DNS doesn't have option for alias and only cname.
Going through instructions on https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain-external cannot complete last step.
So, when typing my domain name connetco.com without "www" page doesn't redirect to [WWW URL]

Golla Venkata Pavani 3,415 Reputation points Microsoft External Staff Moderator

2026-03-06T18:57:06.54+00:00
Hii @Constantin Dragomirov ,

Thank you for reaching us regarding the issue.

This behavior is expected and by design when using Azure Static Web Apps with DNS managed in the Microsoft 365 admin center.

Azure Static Web Apps supports custom domains, but:

Subdomains (for example, www.connetco.com) are supported using a CNAME record that points to <your-app-name>.azurestaticapps.net.

Apex/root domains (for example, connetco.com without www) cannot use a standard CNAME record due to DNS standards. Apex domains require ALIAS/ANAME records, CNAME flattening, or Azure DNS–managed records.

The Microsoft 365 DNS management interface does not support ALIAS/ANAME records. It only supports standard records such as CNAME, A, TXT, MX, etc. Because of this limitation:

www.connetco.com works correctly when configured with a CNAME.

connetco.com (apex domain) cannot be directly mapped.

Azure Static Web Apps does not automatically redirect connetco.com > www.connetco.com.

The final validation step fails when attempting to add the apex domain in the Azure portal.

Recommended actions:
Option1 : Use www as the primary domain (simplest and fully supported)

In Microsoft 365 admin center > Domains > Manage DNS, add a CNAME record:

Host: www

Value: <your-app-name>.azurestaticapps.net

In the Azure portal > Static Web App > Custom domains, add and validate www.connetco.com.

Option 2: Redirect apex domain to www

Keep www.connetco.com configured as above.

At your domain registrar (outside Microsoft 365 DNS), enable URL/domain forwarding:

Redirect https://connetco.com > https://www.connetco.com using a 301 redirect.

Most registrars support this even if DNS is otherwise managed in Microsoft 365. This provides the expected user experience without requiring ALIAS support.

Option 3: Full apex domain support using Azure DNS

Change your domain’s nameservers to Azure DNS.

Create a public DNS zone in Azure.

In Static Web App > Custom domains, add the apex domain using Azure DNS.

Azure automatically creates the required TXT and ALIAS records for the root domain.

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

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.
Golla Venkata Pavani 3,415 Reputation points Microsoft External Staff Moderator

2026-03-09T15:31:14.11+00:00
Hii @Constantin Dragomirov ,

Thank you for sharing the additional details. Both points you raised are valid.

It clarifies that email functionality is controlled by MX, TXT (SPF, DKIM, DMARC), and related DNS records, not by where DNS is hosted. Microsoft explicitly supports hosting DNS in Azure DNS while continuing to use Microsoft 365 for email, as long as the required email records are present in the DNS zone.

Recommended Solution:
The only fully supported solution for apex domains with Azure Static Web Apps is to use Azure DNS.

Move DNS hosting to Azure DNS

Update the domain’s nameservers at Network Solutions to Azure DNS nameservers.

Create a public DNS zone in Azure for connetco.com.

Recreate Microsoft email records in Azure DNS

Copy all existing records from Microsoft 365 DNS: MX, TXT (SPF, DKIM, DMARC), Autodiscover

Email service will continue without interruption once records are in place.

Add apex domain to Azure Static Web Apps

In Static Web App > Custom domains, choose Custom domain on Azure DNS.

Azure automatically creates the required TXT and ALIAS records for the root domain (connetco.com).

This enables HTTPS and allows connetco.com to work directly without www.

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

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.
Golla Venkata Pavani 3,415 Reputation points Microsoft External Staff Moderator

2026-03-10T17:23:59.4933333+00:00

Hii @Constantin Dragomirov ,

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?
Shree Hima Bindu Maganti 6,955 Reputation points Microsoft External Staff Moderator

2026-03-30T17:56:27.5133333+00:00

Hii @Constantin Dragomirov ,
Thanks for the clarification. Moving your DNS from Network Solutions or Microsoft 365 to Azure DNS will not impact your email service, as email functionality depends on DNS records such as MX, TXT (SPF, DKIM, DMARC), and Autodiscover not on where DNS is hosted. As long as you recreate all existing Microsoft 365 DNS records exactly in Azure DNS before updating the nameservers, your email will continue to work without interruption. Microsoft fully supports using external DNS providers, including Azure DNS, with Microsoft 365. The important step is to copy and validate all required records before and after the migration. Once DNS is hosted in Azure, you can configure the apex/root domain properly for Azure Static Web Apps using ALIAS records.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/external-domain-name-system-records?view=o365-worldwide
https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide&tabs=domain-connect
Kindly let us know if the above helps or you need further assistance on this issue.

2 answers

Your answer

Golla Venkata Pavani 3,415 Reputation points Microsoft External Staff Moderator

2026-03-09T15:31:14.11+00:00

Hii @Constantin Dragomirov ,

Thank you for sharing the additional details. Both points you raised are valid.

It clarifies that email functionality is controlled by MX, TXT (SPF, DKIM, DMARC), and related DNS records, not by where DNS is hosted. Microsoft explicitly supports hosting DNS in Azure DNS while continuing to use Microsoft 365 for email, as long as the required email records are present in the DNS zone.

Recommended Solution:
The only fully supported solution for apex domains with Azure Static Web Apps is to use Azure DNS.

Move DNS hosting to Azure DNS

Update the domain’s nameservers at Network Solutions to Azure DNS nameservers.

Create a public DNS zone in Azure for connetco.com.

Recreate Microsoft email records in Azure DNS

Copy all existing records from Microsoft 365 DNS: MX, TXT (SPF, DKIM, DMARC), Autodiscover

Email service will continue without interruption once records are in place.

Add apex domain to Azure Static Web Apps

In Static Web App > Custom domains, choose Custom domain on Azure DNS.

Azure automatically creates the required TXT and ALIAS records for the root domain (connetco.com).

This enables HTTPS and allows connetco.com to work directly without www.

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

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.
Golla Venkata Pavani 3,415 Reputation points Microsoft External Staff Moderator

2026-03-10T17:23:59.4933333+00:00

Hii @Constantin Dragomirov ,

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?
Shree Hima Bindu Maganti 6,955 Reputation points Microsoft External Staff Moderator

2026-03-30T17:56:27.5133333+00:00

Hii @Constantin Dragomirov ,
Thanks for the clarification. Moving your DNS from Network Solutions or Microsoft 365 to Azure DNS will not impact your email service, as email functionality depends on DNS records such as MX, TXT (SPF, DKIM, DMARC), and Autodiscover not on where DNS is hosted. As long as you recreate all existing Microsoft 365 DNS records exactly in Azure DNS before updating the nameservers, your email will continue to work without interruption. Microsoft fully supports using external DNS providers, including Azure DNS, with Microsoft 365. The important step is to copy and validate all required records before and after the migration. Once DNS is hosted in Azure, you can configure the apex/root domain properly for Azure Static Web Apps using ALIAS records.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/external-domain-name-system-records?view=o365-worldwide
https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide&tabs=domain-connect
Kindly let us know if the above helps or you need further assistance on this issue.

Answer 1

Hi Constantin,

To be able to use ALIAS record you will need to switch your name servers to DNS provider that supports it. Before you switch, it is critical that you create all of the necessary DNS records on the new provider to support your Microsoft 365 services.

For example, let's say your plan is to switch to Azure DNS. First you would create the Azure DNS Public DNS zone for your domain, then examine your existing DNS records in M365 admin portal and re-create most of them in your Azure DNS zone.

Once you are confident you have everything correct you can switch the name servers to point to your Azure name servers in Network Solutions portal. After the switchover you would test periodically and continue to monitor things for several days in case there are any issues.

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

Thanks.

-TP

Answer 2

Constantin Dragomirov 0

There are two issues.

My registrar is Network solution and domain forwarding option is disabled.
I host my email at Microsoft.
How these changes will affect my email?

0 comments

Share via

While setting up custom domains URL for static web app Cannot add DNS record for alias because Microsoft DNS doesn't have option for alias and only cname

2 answers

Your answer