DDoS capabilities in Azure Front Door could certainly be improved. Although Microsoft states it comes with basic DDoS protections out of the box, I find it often ineffectual in mitigating thousands of requests from a single source in a short span of time. User then have to rely on the WAF module where users must configure rate-limiting rules, as it does not automatically sense malicious spikes in traffic. I believe Front Door should have an out-of-the-box premium DDoS protection that can automatically detect and block malicious traffic. I would appreciate improvements in the turnaround time for support, especially since issues with Azure Front Door are usually critical for businesses. If there is an issue, it often results in downtime for line of business applications. I have faced this situation multiple times as one of the largest financial institutions in India is hosted there, adhering to strict SLAs that require prompt responses.
There could be improvements regarding its pricing for large-scale projects. Additionally, if I could use Azure Front Door with private IP addresses, it would be more beneficial.
They can lower the price. Lowering the price should encourage customers to use and adopt Azure Front Door, especially since some customers are not using any security features. Positioning the pricing for Front Door more competitively would be appealing, leading to greater customer satisfaction.
I ran into an issue when I was setting up the rules. There's a limitation on the amount of global rules we can add. Rules Engine takes one big long string when we input the values. For example, if I insert a header name and a header value, it's one big long string that gets truncated. It would be nice to see all of it, or it could be broken down into the actual values.
Azure Principal Architect at Cloud Computech Consultancy
Real User
Top 20
2023-05-04T19:07:55Z
May 4, 2023
The solution needs more functionality and needs to be done close to the application. Redirection, rerouting, and support for private as well as public IP addresses are all features that could be included.
CTO Executive at a tech services company with 11-50 employees
Real User
2021-06-03T09:57:23Z
Jun 3, 2021
I'm not a product specialist. There are other people in the company I work for and they are specialists in each of the products of Microsoft. I'm responsible for the governance and cost control of Azure. I'm not a specialist in any products and therefore I couldn't really speak effectively to features that are lacking or missing.
CTA - Entrepreneur at a manufacturing company with 11-50 employees
Reseller
2021-01-14T03:15:16Z
Jan 14, 2021
We should be able to use Front Door defenders with multiple cloud vendors. Currently, they can be used only with the Azure cloud. Azure Front Door should also be able to do global load balancing and provide internal front door services. Microsoft should clearly define what Traffic Manager, Application Gateway, and Azure Front Door products do. These are similar products, and people get confused between these products.
Azure Front Door enhances web application performance and security by leveraging traffic inspection, SSL offloading, and a web application firewall. It enables intelligent routing, load balancing, and global resource deployment while providing essential features for online application security.Azure Front Door integrates GitOps for seamless deployment, offering significant capabilities in giant networks like CDN functionalities and DDoS protection. Its advanced configurations include traffic...
DDoS capabilities in Azure Front Door could certainly be improved. Although Microsoft states it comes with basic DDoS protections out of the box, I find it often ineffectual in mitigating thousands of requests from a single source in a short span of time. User then have to rely on the WAF module where users must configure rate-limiting rules, as it does not automatically sense malicious spikes in traffic. I believe Front Door should have an out-of-the-box premium DDoS protection that can automatically detect and block malicious traffic. I would appreciate improvements in the turnaround time for support, especially since issues with Azure Front Door are usually critical for businesses. If there is an issue, it often results in downtime for line of business applications. I have faced this situation multiple times as one of the largest financial institutions in India is hosted there, adhering to strict SLAs that require prompt responses.
The only significant adjustment required is with URL set parameters that need to be passed for an existing domain. I dislike the URL set parameters.
There could be improvements regarding its pricing for large-scale projects. Additionally, if I could use Azure Front Door with private IP addresses, it would be more beneficial.
The tool should improve its cost.
They can lower the price. Lowering the price should encourage customers to use and adopt Azure Front Door, especially since some customers are not using any security features. Positioning the pricing for Front Door more competitively would be appealing, leading to greater customer satisfaction.
I ran into an issue when I was setting up the rules. There's a limitation on the amount of global rules we can add. Rules Engine takes one big long string when we input the values. For example, if I insert a header name and a header value, it's one big long string that gets truncated. It would be nice to see all of it, or it could be broken down into the actual values.
The user interface needs improvement as it is difficult to create the mapping to link the problem with your private address sources.
The product needs to improve its latency.
The solution needs more functionality and needs to be done close to the application. Redirection, rerouting, and support for private as well as public IP addresses are all features that could be included.
There is room for improvement and they're working on it. Every six months they come out with a preview of changes.
I'm not a product specialist. There are other people in the company I work for and they are specialists in each of the products of Microsoft. I'm responsible for the governance and cost control of Azure. I'm not a specialist in any products and therefore I couldn't really speak effectively to features that are lacking or missing.
We should be able to use Front Door defenders with multiple cloud vendors. Currently, they can be used only with the Azure cloud. Azure Front Door should also be able to do global load balancing and provide internal front door services. Microsoft should clearly define what Traffic Manager, Application Gateway, and Azure Front Door products do. These are similar products, and people get confused between these products.