Static App Only Allows 10 Domains Forwarded from Front Door?

Question

I have a multi-tenant Saas offering that runs on a static app on the front end and azure functions for back end. One of the requirements is to give the option for each customer to bring their own domain so generally is 1 to 1 from tenant to custom domain. As we moved to onboard beyond our first couple of clients realized standard static apps only allowed 5 domains (understood premium allows for 10 now).

Finding that the question on how to go beyond 5 domains seemed to have been asked and answered in link below went down the path of using Front Door to handle custom domains. Hooked it up as described below, added some test domains, everything looked great.

Then I went to add around 20 domains in my staticwebapp.config.json file in the allowedForwardedHosts so that Front Door could forward on to my static app and got the following error on my pipeline build "No more than 10 allowedForwardedHosts can be specified for the forwardingGateway, but xx hosts are currently specified."

So, am I missing something or even going through Front Door am i permanently capped to max of 10 custom domains?

https://learn.microsoft.com/en-us/answers/questions/667238/more-than-5-custom-domains-per-static-web-app

https://learn.microsoft.com/en-us/azure/static-web-apps/front-door-manual?tabs=azure-portal&pivots=swa-afd-manual-afd

Answer 1

Hi Alexander, As I know thia is a hard limitation for the combination on Static web apps and Front Door of 10 hosts for allowedForwardedHost. There is one open issue for a future enhance on this topic (https://github.com/azure/static-web-apps/issues/1568)

Limitations - Static Web App:

• Standard plan: max 5 custom domains
• Premium plan: max 10 custom domains

Workarounds:

• Deploy multiple Static Web Apps and distribute domains across instances (see Deploy and Configure Azure Static Web Apps).
• Use Azure Application Gateway or NGINX as a reverse proxy to manage more custom domains (see Azure Application Gateway Documentation and Configure NGINX as a Reverse Proxy).
• Implement a custom API on Azure Functions to handle domain-based routing logic (see Create an Azure Functions HTTP Trigger and URL Routing with Azure Functions).

References:

• Custom Domains in Azure Static Web Apps
• Using Azure Front Door with Static Web Apps

If the information helped address your question, please Accept the answer.

Luis