The user interface needs improvement as it is difficult to create the mapping to link the problem with your private address sources.

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. 

My suggestion for improvement would be to enhance the Data Export feature to include specific tables, particularly the Azure Diagnostics table.

The product needs to improve its latency. 

The product's features are limited compared to Cloudflare. The tool also doesn't work well in a hybrid environment. I would like to see a way to add personalized APIs in the system. 

There is room for improvement and they're working on it. Every six months they come out with a preview of changes.

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.

This is a relatively expensive solution. 

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.