Microsoft Azure CDN Reviews

The documentation from Microsoft is in depth.

So far I don't find any bottleneck. I am happy with all features and functionality.

I am happy that I don't need to setup everything same as like in my physical infrastructure. There are many things which is only managed by azure and you just need to manage your resource. Such as CDN i am using AFD with WAF, i just make a CNAME and route it to my AFD endpoint then it can be redirected to any origin host in backend.

Everything is just perfect in Microsoft azure networking

Nothing everything is great in the Microsoft azure networking

It's beneficial for me any my work smooth implementation

The speed is awsome, you can radically decreased loading times and less lag. As a domain owner you can get benefits like increase user engagement rates,llower abandoned rates,increased ad impresionsz etc.

At the moment I didn't find any issue with the service. You have a Microsoft product that the name says a lot, security, quality, service, fast response, etc. You can find anything.

They provide security,efficiency, and ease of use on the part of the end user.

The Infraestructure, the servers are geographically distributed and work together to acelerate content delivery. Content delivery networks, make quick transfers of assets.

Extraordinary CDN and cheaplets you decrease load times, save transmission capacity and speed responsiveness—regardless of whether you are creating or overseeing sites or portable applications or encoding and appropriating streaming media, gaming programming, firmware updates or IoT endpoints.

The advantages of utilizing Azure CDN to convey site resources include: Better execution and improved client experience for end clients, particularly when utilizing applications in which numerous trips there and back are needed to stack content.

To get immediate help, you need to buy a help plan beginning from 29 USD every month.

Costs in different suppliers like Backblaze B2 are less expensive (around 0.005 USD per GB/month) for Standard access

All the diverse stockpiling choices wind up being confounding. It's not straight-forward for a tenderfoot to realize when to utilize Blob administration over File administration, for instance. As I would like to think, Amazon AWS and Google Cloud Storage make a superior showing clarifying and streamlining the contribution

pull out all the stops.

reserve static articles stacked from Azure Blob stockpiling, a web application, or any openly available web worker, by utilizing the nearest cdn worker

Its inexpensive; comes with pay as as yo go options to choose from, easy to set up and use, easily integrates to Azure and other services, helps to reduce load time of apps hence saving data bandwidth, great customer support, offers regular insights and analytics about product usage.

Certainly requires some programming background, does not integrate/support web sockets

Eases management of applications and guarantees security of your apps and api.

We needed to speed up our apps, save on bandwidth and improve our security of apps and apis.

My experience with MS Networking is seamlessly easy and user friendly with great customs configuration , Easy to understand and easy to configure with great enrich of ms documentation.

Till time not get any dislike for ms networking part.

For connecting my application outside or inside means connecting from internet or connecting internally .

its solve complex networking architecture

its some of services like application gate express routee solve security problem also

We started using Azure CDN by a requirement that made the department eCommerce company. To use one of the platforms where we published our online stores we requested that the images were hosted on a dedicated server images to display them properly froma web.

For this reason we decided to use Azure CDN, to thereby have two advantages: having its own image storage service in the cloud plus all the benefits of a CDN network.

Having the images distributed according to the proximity of the user, the platform achieved a much higher performance, allowing our customers to access the images of our products much faster.

We can also offer e-commerce department third-party tools for Llos themselves could upload online photographs of our products.

With respect to the negative things I could name the complexity of implementation. While it was not a very difficult task is quite confusing process for the CDN platform is configured correctly. The steps are few but confused when implemented. It should improve slightly this.

One point that should be corrected is to provide tools for uploading and downloading of images from the blob of Azure CDN. The administration of the images has to be done with third party tools.

Undoubtedly if someone needs to use a hosting service images and has an account must implement Azure CDN. It is very efficient and practical.

As I mentioned earlier, it was implemented in order to have a platform images distributed geographically efficient way for our e-commerce online stores. We managed to have a platform mounted within hours that largely met our expectations.

Best CDN that works seamlessly with the Azure stack offerings. Different locations can be chosen. And it applies to the whole of the App contents. the have a lot of regions especially in the US continent. This gave us a lot of performance improvement and faster page loads

More regions to be covered in the future.

Must try CDN for Cloud users . Especially those who are currently using the Azure cloud services

Publishing our Public website in Azure and using Azure CDN gave us a lot of performance improvement

For me, it is easy to set up and insight tool from the Azure Portal.

Still a bit confuse on the integration with some tecnologies, lack of servers at Australia

I am developing a new dashboard panel, and it must to be fast and clean.

Effective CDN, and provides detailed reporting on cached objects. Effective API to managing load and purge.

No complaints! The CDN fulfills all our use cases satisfactorily and under very heavy burts of activity/load.

Caching content used in email delivery use cases. Also convential web asset hosting use cases.