When comparing Microsoft Azure vs KeyCDN, the Slant community recommends KeyCDN for most people. In the question“What are the best content delivery networks (CDNs)?” KeyCDN is ranked 7th while Microsoft Azure is ranked 11th. The most important reason people chose KeyCDN is:
Traffic [prices](https://www.keycdn.com/pages/pricing) are as low as $0.04/GB and volume pricing starts at 10TB/month.
Ranked in these QuestionsQuestion Ranking
Pro Supports running Windows Server
Most, if not all, of the major cloud PaaS providers offer a Linux variant to host your applications. Windows Azure, being a Microsoft product obviously, supports Windows in addition to Linux.
Pro Linux Instances
The Azure platform has been supporting Linux VMs for a while now and has Linux distributions readily available in the catalogue.
Pro Free Tier
Microsoft Azure offers a Free Tier option that allows you to spawn a BST-1 instance that has 750 free hours.
Pro Transparent, pay-as-you-go pricing
Traffic prices are as low as $0.04/GB and volume pricing starts at 10TB/month.
Pro Simple and easy setup
CDN configuration is instantly deployed.
Pro Free Lets Encrypt SSL certificates for custom zone names
Pro HTTP/2 Support
One of the 1st providers to support HTTP/2
Pro Custom SSL for free
Allows uploading own certificate at no extra cost. Shared SSL is also available.
Pro Brotli support
KeyCDN supports Brotli compression for users who have Brotli enabled on their origin server.
Pro POPs in Australia, Singapore, Hong Kong and Japan at no extra cost
Pro Real-time raw logs available for free
Pro Support SPDY 3.1
KeyCDN supports SPDY 3.1 for even faster secured connections.
Even though in the context of Pay-as-you-go services, it's cost effective, but monthly pricing for these services are quite higher than competitors.
Con Unreasonable anti-spam policy
Not suitable if you have an association with online advertising. A single email that may include your domain that appears on Spamcop will result in a threat to terminate your account and a requirement to disable the URL -- even if you are not responsible for the production or sending of the email.
Con Config changes take 5-10 minutes
Any config change is queued for several minutes before being applied, without any time estimate. Combined with caching and DNS delays, it can make debugging a bit more difficult.