The Azure Content Delivery Network (CDN) is designed to send audio, video, apps, photos, and other files to your customers, faster and more reliably, using the servers closest to each user.
Important: The price in R$ is merely a reference; this is an int'l transaction and the final price is subject to exchange rates and the inclusion of IOF taxes and an eNF will not be issued.
|Outbound Data Transfers||Zone 1 1||Zone 2 1|
|First 10 TB 2 /Month||$0.087 per GB||$0.138 per GB|
|Next 40 TB (10 – 50 TB) /Month||$0.08 per GB||$0.13 per GB|
|Next 100 TB (50 – 150 TB) /Month||$0.06 per GB||$0.12 per GB|
|Next 350 TB (150 – 500 TB) /Month||$0.04 per GB||$0.1 per GB|
|Next 524 TB (500 – 1,024 TB) /Month||$0.03 per GB||$0.08 per GB|
|Next 4,096 TB (1,024 – 5,120 TB) /Month||$0.025 per GB||$0.07 per GB|
|Over 5,120 TB /Month||Contact us||Contact us|
CDN is not available in the Brazil South region. Please select another region.
CDN is not available in the US Gov Virginia region. Please select another region.
CDN is not available in the US Gov Iowa region. Please select another region.
CDN data transfer pricing is based on the CDN node location from where the transfers are served, not the end user’s location. The following geographic areas correspond to Zone 1 and Zone 2 for CDN.
Your CDN outbound data transfers are aggregated each month during your billing cycle. The first 10 TB are charged at the first price point, the next 40 TB at the second, and so on. For example, if you use 50 TB of data transfers in Zone 1, 10 TB will be billed at $0.087 per GB, and the next 40 TB will be billed at $0.08 per GB.
No. The CDN data center is selected based on the end users’ network configurations and cannot be controlled by the developer. Users may be served by locations that are preferred by their ISP, or nodes that are "closer" in a logical sense, not necessarily in physical proximity.
Availability of content in CDN's local caches (often called "cache efficacy" or "offload") is influenced by multiple factors including:
For example, a developer with high churn and high traffic has less cache efficacy than other users because objects are swapped in and out more frequently. This incurs higher Storage and Data Transfer charges since more origin requests are required.
To reduce the need to make origin requests, you can make longer max-age headers, allowing CDN to hold objects longer.