Hi @Ernesto ,
Thanks for the question. Like Luke mentioned in his detailed answer, it all depends on your requirements and what you're trying to achieve with your web app.
It's generally a good practice to use different custom domains for each environment (e.g. dev, test, prod) to avoid confusion and ensure that each environment is clearly identified. This can also help with security and compliance, as it allows you to apply different policies and settings to each environment.
When setting up custom domains in Azure App Service, there are a few best practices shared in the Azure docs that you should keep in mind:
-To clearly identify each environment, it's a good practice to use a subdomain for each environment (e.g. dev.example.com, test.example.com, prod.example.com).
-If you are using SSL/TLS for your custom domains, it's a good practice to use a wildcard SSL certificate that covers all subdomains. This can simplify the management of SSL certificates and ensure that all subdomains are secured.
-Consider using Azure DNS for domain management. Azure DNS is a managed DNS service that can be used to manage custom domains in Azure App Service. Using Azure DNS can simplify the management of DNS records and ensure that your custom domains are configured correctly.
- If you have multiple instances of your application running in different regions, you can use Azure Traffic Manager to load balance traffic across the instances. This can help improve performance and ensure high availability.
Check out these docs for more detailed info: Custom domains in Azure App Service, Azure DNS overview, Azure Traffic Manager overview
-Grace