Windows Azure CDN Reviews

We are using Windows Azure CDN, Azure AI capability for a translator, Azure Front Door for CDN, and from Microsoft's side, we are selling many Microsoft E5 licenses. We are using it for our client.

In my opinion, Windows Azure CDN is one of the best CDNs. We tried to replace it and made a business case to check other options such as Cloudflare, and we are using Cloudflare and tried Akamai, wanting to explore alternatives from OCI.

One of the best features of Windows Azure CDN is that it has integrated WAF; it is not only CDN alone and it is a very smart and capable WAF.

Windows Azure CDN is easily integrated with Azure services such as Azure Storage and Azure Web Apps, and sometimes we are using just Azure Front Door while the back end and database will be on OCI.

The impact of Windows Azure CDN's dynamic content acceleration on our application performance is very significant. For one of our clients, we could not use anything other than Azure Front Door.

It is not a weakness of Windows Azure CDN; rather, it is the fact that it is outside Saudi Arabia, leading to some regulation issues.

For computing, they could make a flex engine similar to other providers which would be more beneficial for end-users.

I have been working with Microsoft for more than 12 years.

We do not need technical support for our Azure or Microsoft solutions because we sell a managed service and support contract along with our proposal.

Positive

I take part in implementation only for DR projects for the product I bring to the company at first. We were not using Acronis before but I convinced my company that we should use it.

In terms of pricing for Windows Azure CDN and the whole Microsoft products, you cannot compare networking alone or compute alone; you need a full solution.

We are dealing directly with Microsoft and we have substantial experience. We are one of the top two companies in terms of experts in Saudi Arabia.

I am not involved in the technicality of Azure Front Door. If it was OCI computing, I could be more helpful because I am from the presale side.

I am not dealing with Microsoft Azure products; Acronis is a different vendor.

I just only do architect and bill of quantity; I never do the real implementation.

On a scale of one to ten, I would rate Windows Azure CDN an eight.

We use the solution for hosting static web applications. We use it to cache images or files.

We mostly distribute images through the CDN. Earlier, we were directly caching from the server to CDN. Since we started using the solution, there has been a significant improvement in the response time.

The product is very fast. The data is cached faster, and the sites load faster because we use the tool. Our response time has improved significantly. It is easy to configure. The UI is very intuitive. It’s not very technical. It is easy to learn.

The response time of the support team must be improved. The team provides slow responses.

I have been using the solution for three to four months.

We haven't seen any downtime. As we add more features, we expect to see higher data traffic. For now, excluding human errors, we didn't experience any downtime. The tool is stable.

The tool is scalable. The scalability is available out of the box. We have 16,000 to 20,000 users daily as it is open to the public. We’re expecting to grow to 60,000 to 70,000 hits per day.

The support team takes time to understand our queries and respond to us. The response time must be improved.

We have used Amazon CloudFront. Windows Azure CDN’s UI is better and easier to use than CloudFront's.

The setup is very straightforward. The deployment doesn't take much time. Within a few weeks, the tool was up and running. We configure the solution, and the objects are stored.

The product is worth using. It is easier to use compared to Amazon CloudFront. The UI is intuitive.

I will recommend the solution to others. Overall, I rate the tool an eight out of ten.

We utilize Windows Azure CDN primarily for caching resources, alleviating the strain on our servers, and preventing excessive traffic to our data center. The tool comes into play when a public file or resource needs distribution to a wide user base. Using it, we distribute these resources to users, ensuring smoother access and reducing the load on our servers.

One of the tool's best features is its ability to handle edge cases. For instance, we encountered a situation where we needed to remove certain files from public access. The solution offered a purge feature that allowed us to remove these files. This feature ensured that the files were deleted from all edge servers. Subsequently, we were able to upload new versions of the files.

I believe Windows Azure CDN can improve monitoring and measuring overall end-user performance. Providing monitoring tools or agents that can be integrated into our pages would be highly beneficial. Setting up a custom domain with Windows Azure CDN involves proving domain ownership, which can take some time. The process is relatively straightforward if your DNS or domain registrar is already integrated with Microsoft. However, the verification process may be more time-consuming if you use a different service provider.

I have been using the product since 2018. 

The tool is very stable, and we haven't encountered any downtime. 

The  scalable tool proved highly advantageous when we launched the public service for one of our projects. Users worldwide could access our services. Throughout the project duration, we encountered no issues reported by end-users related to the product. 

The users are limited to around 10-20 people within the infrastructure team, including the operations team. However, when considering end-users who are not employees of our company, such as public users accessing our products through Windows Azure CDN, the number could reach over a hundred thousand users or more.

The reachability of Azure primarily drove the decision to go with Windows Azure CDN within the specific areas we were targeting, such as Europe, the US, and the UK. We found that Microsoft products, including Windows Azure CDN, were readily available in these regions, making it our most viable choice. While there were other options like Akamai, the fact that all these options were available within the Azure ecosystem influenced our decision to choose it.

The tool's initial installation and setup were very easy. It only required a few clicks to set up a CDN name, and the process was completed quickly. However, if you need to use your domain name with the CDN, there is a process involved that may take around eight to twelve hours to complete.

The tool's pricing is cheap. 

I would advise you to use Windows Azure CDN if it meets your requirements. For instance, it would be a suitable choice if your user base is located in regions with a strong presence. However, it may not be the best fit if you intend to use it in regions where Windows Azure CDN lacks public presence.

The tool's integration process with our existing infrastructure was smooth. We leveraged Microsoft blob storage integration, where we uploaded our files to the blob storage using the REST API.

I rate the overall product an eight out of ten. 

When considering Azure CDN needs, optimizing delivery across various platforms to meet business requirements and ensure global reach is essential. By distributing content across multiple regions, Azure CDN enhances availability, benefiting clients worldwide.

I like that CDN offers a routing feature. 

Azure is continuously improving its CDN but the documentation should be up-to-date.

I have been using Windows Azure CDN for two years.

The solution’s scalability is good.

Azure facilitates timely delivery through a platform tailored for multi-region retailing. It ensures efficient product delivery, facilitates product checking, and provides a seamless login experience on web pages. These integrations are essential for any retail company looking to optimize its solution.

Azure CDN integrates directly with actual resources. It's really easy to integrate or add resources, whether through our API management or other methods.

I recommend integrating the value service by switching from Azure to another CDN provider to deliver content to the final user.

Overall, I rate the solution an eight out of ten.

The geolocation feature is very important because many colleagues travel worldwide and need to access information from anywhere. The product has improved security. 

Windows Azure CDN should lower its prices. 

I have been using the product for eight years. 

Windows Azure CDN is stable. 

The tool is scalable. It can be used by smaller or big businesses, depending on your needs.

We do not use technical support. We have technical personnel on site. Our colleagues are certified, and we do everything on our own.

Windows Azure CDN's deployment is very easy. However, if you are setting everything up at a company level, you need to adapt to many things, so it would take considerable time to make everything functional again. Similarly, transferring from on-premise to the cloud will take some time. It depends on the case, but you cannot set it up in just a few days.

The pricing of the solution depends on usage and varies based on the company's needs. If you want additional features like advanced logging, it will be pricier. However, it could be cheaper if you don't need those features. It all depends on the resources and requirements.

Everything is improving daily and changing fast, so you need to adapt to that. I think it's going in the right direction. The tool suits more enterprise customers. I can't suggest the tool to anyone because they need to understand what they are doing and know their business needs. It's not like buying a simple product; it has a business impact. If someone needs it, they should ask for a demonstration and decide if it fits their needs.

I rate the overall solution an eight out of ten.

We primarily use this solution for migration cases, in a construction company. At times, a hybrid solution is necessary, as I implemented for one customer. Some applications remain on-premise, while others migrate to the cloud. We aim to blend them based on the performance requirements they entail. 

I enjoy engaging in discussions with colleagues possessing unique expertise. I leverage the three platforms—Azure, Google, and AWS extensively. This allows me to offer diverse solutions to customers, commonly referred to as a multi-cloud approach.

I aim to enhance the reporting.

I have been working with Windows Azure CDN for the past 5 years. 

I would rate the scalability 8 out of 10. 

It’s been a while since I worked in technical support because my role has shifted to being a solution architect. While I propose solutions, providing support is not part of my current responsibilities.

Neutral

The setup is challenging, as there are always potential impacts. However, I approach it with caution and am diligent in preventing or addressing issues in advance.I have experience working on both cloud and on-premise bots. Currently, my projects focus on migrations between clouds, specifically from on-premise to the cloud. The last deployment lasted three months, while another took six months.

The pricing is extremely high, almost 9 out of 10. 

Overall, I would rate this 8 out of 10.

We use the product for faster content delivery with low latency. 

We have experienced issues with switch connectivity.

I have been working with the product for four years. 

The tool's pricing is cheap.

I would rate the product an eight out of ten. 

I use Windows Azure CDN in my company to forward different stuff.

The most valuable feature of the solution stems from the fact that one can access Windows Azure CDN from anywhere.

The high price of Windows Azure CDN is an area of concern where improvements can be made.

I have been using Windows Azure CDN for three years. I am an end user of the solution who mostly uses the solution with Azure Storage.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten.

Almost 20 people in my company use Windows Azure CDN.

Windows Azure CDN is used daily in my company.

I rate the initial setup phase of Windows Azure CDN an eight on a scale of one to ten, where one is difficult, and ten is easy.

The initial setup phase of Windows Azure CDN is easy.

The solution is deployed on a private cloud.

The solution can be deployed in a day.

One of my company's in-house teams was involved in the deployment process of Windows Azure CDN.

The price of the solution is too high. I rate the price of Windows Azure CDN a six on a scale of one to ten, where one is cheap, and ten is high. My company makes monthly payments towards the licensing costs attached to Windows Azure CDN, which comes to around 20 USD per user.

I rate the overall product a nine out of ten.

We use Windows Azure CDN for content delivery in our company. So, we use it for images and static content.

The fact that it just delivers what it is supposed to do is its most valuable feature.

Right now, we don't really need any improvements. We would improve Microsoft Windows Azure CDN if we could, but that's a story for a much longer call. There were a few bugs that were very disappointing. So, that is a part of the reason why we started using Fastly.

I would like the support team to be faster. So, improvements are required in the solution's technical team.

I have been using Windows Azure CDN for five-plus years.

Stability-wise, the product was okay. We never had any issues with the stability, so whenever I needed it to work, it worked fine.

I won't be able to comment on scalability since we never had any issues with the solution. The users using the solution were around a million to a million and a half in a month.

It's amazing when you get to speak to direct and technical people. Whether the technical support is faster, more knowledgeable, or customer friendly depends on who you are talking to, and I recall that when we had a big problem that our issue required dealing with Verizon, which meant we spent a month back and forth until the problem was solved b the technical team, which I believe they could have solved by spending some time on an afternoon. So with that experience, we were very disappointed.

The initial setup is very straightforward. Actually, Microsoft offers one of the most straightforward setup phases. Originally, it took literally minutes to deploy the solution, after which you are just waiting for the certificate. When there was a bug, we couldn't get it to work for a month.

One person should be able to deploy and maintain the solution.

The implementation was done in-house.

It is a good solution that delivered what it was supposed to, and so it's very hard to quantify because we didn't really invest in finding its return on investment. For us, we paid for a service because we needed that service.

The solution's price depends on how much traffic you have. So, it was okay for us. Payments are to be made on a monthly basis since one has to pay for what they used.

If you want something to start quickly and not bother with anything, then it's a perfect solution. It's a very good entry-level solution when you just want to turn it on and not worry about it. If you want to worry about the price or somebody to talk to, I would recommend that once you have enough traffic to start talking to other companies, you can choose the solution.

Overall, I rate the solution an eight out of ten.

I use it to cache and download files quickly.

One of the most valuable aspects is the capability to store extensive datasets and objects in the cloud, enabling their download through shared access signatures.

Exploring shared access solutions with cloud accounts would be a beneficial choice.

I have been using it for about four years.

The initial setup is a straightforward process involving the creation of blog containers or file systems. It is intuitive, especially for those familiar with systems administration.

It comes at a relatively affordable cost.

I would recommend watching informative video training courses to ensure a proper understanding and emphasize the importance of implementing security measures effectively. Overall, I would rate it eight out of ten.