CTO Executive at a tech services company with 11-50 employees
Real User
Easy to implement and affordable with a fast deployment
Pros and Cons
  • "The price is one of the most important aspects of the product. It's quite affordable."
  • "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."

What is our primary use case?

We tend to use every aspect of the product. We use Azure Front Door, the Web Application Firewall on Front Door, and the Application Gateway. We implement all of these solutions for our customers. It depends on the need of our customers. The solution supports a lot of data publishing work.

What is most valuable?

The price is one of the most important aspects of the product. It's quite affordable.

The ease of the implementation is a helpful aspect. It's really, really vital. It's very easy to implement for our customers. We simply handle the first phase and Microsoft does all the rest. The cloud makes it easy. The deployment is fast.

What needs improvement?

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.

Which solution did I use previously and why did I switch?

We tend to only focus on Microsoft products, including Azure.

Buyer's Guide
CDN
April 2024
Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Cloudflare and others in CDN. Updated: April 2024.
768,857 professionals have used our research since 2012.

How was the initial setup?

The setup is not overly complex or difficult. It's quite easy to implement. The deployment is fast and is mostly handled by Microsoft. It's a great aspect of the product overall.

What about the implementation team?

We help our clients implement the solution.

What's my experience with pricing, setup cost, and licensing?

The pricing is pretty good. It's reasonably priced in general.

What other advice do I have?

We are a Microsoft partner. We implement a lot of products from Microsoft for our customers. We're a partner specializing in Azure and therefore we implement many features that Azure has. We implement Azure Front Door and Microsoft Azure Application Gateway.

Usually, Azure is a public cloud. We deploy only Azure. We don't deploy anything on-prem and so we deploy AWS specifically only in the Azure cloud. A lot of our clients these days are moving over to the cloud, and we are assisting with that process.

I'd rate the solution at an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
CTA - Entrepreneur at a manufacturing company with 11-50 employees
Reseller
It inspects the traffic at the network level and is stable, scalable, and easy to set up
Pros and Cons
  • "It inspects the traffic at the network level before it comes into Azure. We can do SSL offloading, and it can detect abnormalities before the traffic comes into the application. It can be used globally and is easy to set up. It is also quite stable and scalable."
  • "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."

What is our primary use case?

We use it for external security filtering to protect our external traffic that is coming into Azure.

What is most valuable?

It inspects the traffic at the network level before it comes into Azure. We can do SSL offloading, and it can detect abnormalities before the traffic comes into the application. 

It can be used globally and is easy to set up. It is also quite stable and scalable.

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for three years.

What do I think about the stability of the solution?

It is quite stable.

What do I think about the scalability of the solution?

It is easily scalable. It is set up for the enterprise, and it is a global task manager. 

How are customer service and technical support?

Their technical support is pretty good.

How was the initial setup?

Its initial setup is easy.

What's my experience with pricing, setup cost, and licensing?

It is on a pay-as-you-go basis.

What other advice do I have?

I would rate Azure Front Door an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
PeerSpot user
Buyer's Guide
Download our free CDN Report and find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Cloudflare, and more!
Updated: April 2024
Buyer's Guide
Download our free CDN Report and find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Cloudflare, and more!