Azure CDN

This problem is a space that provides the administrative capacity to each of its users to have a quality and one hundred percent professional operational management.

Azure CDN allows you to have a better management of all your documents as well as preserve them in the best way in its cloud-based storage support.

The large number of options and shortcuts that this program shows and manifests requires prior training for new and interested users.

There are some small bugs in the interface to make clear the function of each tool, this aspect can be improved in a future update.

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

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.

Developing apps and websites.

Advanced analytics.

Pricing.

New infrastructure cost could be minimized.

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.

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).

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.