Lots of you may be familiar with Azure Front door but if not then let me summarize.
Azure Front Door is a cloud-based service from Microsoft Azure that provides a scalable and secure way to route traffic to various backend services, such as web applications, APIs, and microservices. It acts as a global load balancer that can intelligently distribute traffic across multiple regions based on geographic location, latency, and other metrics.
Some of the key features of Azure Front Door include:
- Global load balancing: Azure Front Door can intelligently distribute traffic across multiple backend services located in different regions, ensuring optimal performance and availability for users worldwide.
- Security: Azure Front Door provides SSL termination, DDoS protection, and other security features to help protect your backend services from malicious attacks.
- Traffic routing: Azure Front Door can route traffic based on user location, content type, URL path, and other criteria, making it easy to implement complex traffic routing scenarios.
- High availability: Azure Front Door is designed to provide high availability and reliability, with built-in redundancy and automatic failover capabilities.
- Analytics: Azure Front Door provides detailed analytics and monitoring capabilities, including real-time metrics, logs, and alerts, to help you optimize your traffic routing and improve the performance of your backend services.
Overall, Azure Front Door is a powerful tool for managing and optimizing traffic to your backend services, helping to ensure high performance, scalability, and security for your applications and APIs.
When you create an Azure Web application out of the box you get a wesbite that ends with the name .azurewebsites.net, many customers want to use a custom domain name so that it is much cleaner and nicer like gregorsuttie.com instead of gregorsuttie.azurewebsites.net
So if you are using Azure Front Door as part of a solution along with a custom domain and you wold like to restrict access to users so that they cannot go to the .azurewebsites.net part then you can go to Networking and use what’s called an Access restriction.
Now they will see this instead:-
You can even whitelist IP addresses so that certain users can still use the .azurewebsites.net as well as the kudu interface.