a fast, easy to use and reliable CDN for Azure Cloud architectures
July 06, 2021

a fast, easy to use and reliable CDN for Azure Cloud architectures

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Azure CDN

We started using Azure CDN when we developed a new version of our corporate website, which included an architectural cloud shift. The new PaaS-based architecture requested that the website images and documents be hosted on a dedicated CDN server.

As our cloud partner is Microsoft, we decided to use Azure CDN, and at the same time, try the Azure capabilities (including CDN) on a limited use case.

  • New websites can be boosted up quickly
  • Easily scalable according to our performance requirements
  • Easy integration with other Azure services
  • You only pay for what you need
  • Tough learning curve--you have to be comfortable with the Azure Cloud logic and UI to use it easily
  • Special or uncommon use cases' pricing can be hard to forecast/follow
  • Can be expensive for simple use cases
  • high level performance and scalability
  • security
  • seamless integration with the other Azure services we use
  • our website documents/images are far more fastloading
  • our website architecture is more robust and technically challenging
We did not evaluate any other CDN solution because we choosed Microsoft Azure as our cloud provider, so the Azure CDN choice was easy.
Furthermore, the speed at which we managed to stand up the CDN and push content in it was very appreciated during our website development, so we didn't even think about another CDN provider.

Do you think Azure CDN delivers good value for the price?


Are you happy with Azure CDN's feature set?


Did Azure CDN live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Azure CDN go as expected?


Would you buy Azure CDN again?


Azure CDN service integrates very well in a full or hybrid cloud architecture that is basically based on Azure services. In that scenario, the learning curve is shared among the different Azure services you need.