Section 5 – Implement platform protection - Implement advanced network security - Create and configure Azure Front Door

Frontend pool is the name of your instance, backend pool is the backend service what you want balance to.

If you want to use a custom domain, you will add it to frontend pool and you have to add an cname that points to your adf domain, like so.

Go to public dns and add it.

Once done go back to your AFD instance.

Then select "Add" and voila.

The next thing is to add the custom domain to your routing rule. Open and expand frontends / domains and select custom domain.

Once done and saved the config, you will open the custom domain.

Now you will enable the HTTPS and certificate request is pushed forward, it will take time, just have patience.

Wuhuu, now you have your own custom domain and MS generated certificate. That was easy.

From here you can see what Load balancer would be right for your.

Load-balancing options - Azure Application Architecture Guide

Learn about Azure load-balancing services and how you can use them to distribute your workloads across multiple computing resources.

Next generation of Front doors

So what's new with next gen versions of AFD.

Key features included with Azure Front Door Standard/Premium (Preview):

• Accelerated application performance by using split TCP-based anycast protocol.
• Intelligent health probe monitoring and load balancing among origins.
• Define your own custom domain with flexible domain validation.
• Application security with integrated Web Application Firewall (WAF).
• SSL offload and integrated certificate management.
• Secure your origins with Private Link.
• Bot Protection
• Customizable traffic routing and optimizations via Rule Set.
• Built-in reports with all-in-one dashboard for both Front Door and security patterns.
• Real-time monitoring and alerts that integrate with Azure Monitoring.
• Logging for each Front Door request and failed health probes.
• Native support of end-to-end IPv6 connectivity and HTTP/2 protocol.

Custom domains in next gen versions

The process is a little bit different. First you add the custom domain.

Need to verify

You will get the txt-record to add for public domain.

Go back and done.

What about the pricing?

Base fees (Billed hourly and only for number of hours used)​

Data transfer out from edge location to client (same price for Standard and Premium SKU)​

Data transfer in to origin (same price for Standard and Premium SKU)​

Request Pricing

Standard SKU

Premium SKU (includes WAF and Private Link at no additional cost)

Comparing the different versions

Azure Front Door

• Is an Application Delivery Network (ADN) as a service
• Offers various layer 7 load-balancing capabilities for your applications.
• It provides dynamic site acceleration (DSA)
• Provides global load balancing with near real-time failover.
• It is a highly available and scalable service, which is fully managed by Azure.

Azure Front Door Standard SKU

• Content delivery optimized
• Offering both static and dynamic content acceleration
• Global load balancing
• SSL offload
• Domain and certificate management
• Enhanced traffic analytics
• Basic security capabilities

Azure Front Door Premium SKU

• builds on capabilities of Standard SKU, and adds:
• Extensive security capabilities across WAF
• BOT protection
• Private Link support
• Integration with Microsoft Threat Intelligence and security analytics.

Things to remember

AFD has three different levels Basic, Standard and Premium.

AFD can generate a certificate for You or You can bring Your own.

When using a custom domain, You have to also define the used FQDN domain inside the custom domains.

Link to main post

Share this: