This is a platform that provides a better work balance to my entire work operation
This is a platform that provides a better work balance to my entire work operation, Azure CDN is created to take advantage of digital …
Overview
What is Azure CDN?
Microsoft offers a content delivery network, Azure CDN.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Pricing
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
6 people also want pricing
Alternatives Pricing
What is Amazon CloudFront?
CloudFront is the content delivery network (CDN) from Amazon Web Services.
What is Cloudflare?
Cloudflare, from the company of the same name in San Francisco, provides DDoS and bot mitigation security for business domains, as well as a content delivery network (CDN) and web application firewall (WAF).
Product Details
- About
- Tech Details
What is Azure CDN?
Azure CDN Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(38)Attribute Ratings
Reviews
(1-5 of 5)Companies can't remove reviews or game the system. Here's why
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.
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.
Azure Content Delivery Network (CDN) lets us reduce load times and It saves on managing and optimizing our websites bandwidth. Simple and user-friendly settings as well as personalization of resources. Our company is always launching new startups IT web based projects and we have to buy as many services as we need. That's why Azure helps us to buy and pay for server resources according to the project we have.
- Easy to use and customizable settings.
- You pay according to your resources usage.
- High speed and security CDN with great support team.
- Tutorials,‌ guides in English should be more easy to understand.
- Prices can be lower.
- Save costs.
- Increase security.
More user friendly and it’s so easy to learn, the prices may be close to each other, but the service is excellent.
March 19, 2019
Azure CDN Review
Azure CDN is Microsoft's cloud content distribution network custom-built for Azure. It shines for its ability to distribute static data easily to thousands -- or millions -- of clients while reducing the load to your origin servers. Azure CDN, like other CDN options, also speeds up client query times, by increasing the likelihood that file requests can be served quickly from a resource already available in the region nearest the request.
- Cost-competitive: Azure CDN is very similar to other options from Amazon and Google, as well as smaller third-parties, and is priced to compete with those other PaaS vendors.
- Like any solid CDN, helps alleviate load at origin nodes for static files.
- A large number of points of presence means that many queries are already available close to end users, reducing the amount of time required to load most files as compared to loading them directly from the origin.
- Unlike Cloudfront, Azure CDN does not yet support WebSockets.
- Limited options for deploying endpoints that support authentication.
- Azure CDN reduced origin instance load by removing the need to constantly serve large numbers of static files, meaning applications can be deployed with smaller/fewer instances.
- Azure CDN reduces apparent load times to customers by serving cached files out of POPs in the local region of those clients, instead of requiring those clients to make multiple, lengthy requests through to the origin servers.
Azure CDN is very similar to other CDN choices -- we generally choose it when the decision to deploy with Microsoft Azure has already been made and the software architecture requires a CDN. Because Azure CDN is very similar to choices from a number of other vendors, we usually choose it when its tie-ins with other Azure services is the key benefit.
October 09, 2018
Azure CDN: Global Delivery & Awesome Uptime
Azure CDN backs global distribution of all client-side code (JavaScript & CSS) plus supporting assets (images) for LiveTiles. It accelerates load times for every product (originally clocked in as 3x faster than raw storage) and allows for an evergreen deployment model for our SharePoint add-in solutions that can only use client-side code.
- Global reach - we have customers around the world and they all get excellent performance.
- Global availability - we've never had down time on Azure CDN.
- Easy management - you can do everything easily from the portal connecting things to a storage container and from there it's zero management except purging on new content.
- For the longest time they didn't have a robust SDK. They have one now, but it could be better.
- The different flavors of Azure CDN (Akamai, Verizon, etc) have different costs, but not well differentiated features. Might be confusing to new users.
- I'm not overly familiar with it, but AWS does have a programmability in their CDN offering (Lambda @ Edge) and Azure doesn't seem to have an equivalent (Azure Functions is region-specific).
- Performance improvements - On first change to Azure CDN, we had a great bump in page load times in our app.
- Evergreen Deployment - Simplified updating code in our apps by putting it all in one place.
Azure CDN is certainly the favorite when you're already working in Azure like us. CloudFront has programmability and should obviously be considered first if you're already on AWS. I've seen use of CloudFlare for one-off sites (EG, my friends who are WordPress people and are intimidated by Azure and AWS).
Our Marketing and Communications department was the primary user of the Azure CDN. In a small capacity, our HR and Training departments used it to host materials distributed throughout the company. In all cases, the material hosted within the CDN was distributed throughout the entire US for consumption. The primary reason we went with a CDN, instead of just serving content from a single Azure VM working as a file server, is because it allowed content to be delivered to remote users more quickly.
- I found the CDN very easy to setup and configure within the Azure Portal.
- Being Azure, there are plenty of free tools that allow you to manage the CDN from a UI that is not the portal. This was especially handy when I trained end users how to manage content within their specific realm.
- The primary complaint I had with the CDN was expiring content once it was distributed. I realize it doesn't make sense for each endpoint to refresh content frequently, however if you upload something and need to make a tweak and then upload it again, you are kinda stuck. The only option at that point is to rename the content, which doesn't help if you've already distributed a link. It would be nice if you could upload new content to the source and force a refresh.
- I would like to see more granular folder permissions. For instance, if I only wanted a single CDN but wanted to have folders for different divisions (marketing, hr, training, etc...) it would be nice to be able to get an access key at the folder level instead of the CDN level.
- Content cannot be stored at the root of the CDN, you must have it inside a folder. This isn't a huge deal on a brand new setup but if you are moving from a prior CDN to Azure and already have content at the root, it makes that transition more difficult.
- The speed at which we could stand up the CDN and push content made this significantly faster than putting together our own file server and pointing a CDN URL to it. The ease of management, from a plethora of free tools, allowed me to quickly get users up to speed on both Windows and Mac based PC's.
We did not evaluate any other CDN's before we selected Azure. We heavily use Azure for our development and infrastructure efforts so choosing the Azure CDN was easy. The only thing we compared it to was standing up a Windows Server VM and pointing a CDN URL to it allowing it to serve as a file server, which was much more cumbersome.