Azure CDN improves application performance by caching content to the location nearest the customer.
CDN outbound data transfers
|Service||Standard version2||Standard Plus version3||Premium version4|
|CDN data transfer (0-10 TB1/month)||¥0.19/GB||¥0.396/GB||¥0.228/GB||¥0.45/GB|
|CDN data transfer (10-50 TB/month)||¥0.16/GB||¥0.347/GB||¥0.198/GB||¥0.42/GB|
|CDN data transfer (50-100 TB/month)||¥0.13/GB||¥0.297/GB||¥0.169/GB||¥0.39/GB|
|CDN data transfer (more than 100 TB/month)||¥0.1/GB||¥0.277/GB||¥0.139/GB||¥0.36/GB|
Which regions correspond to Zone 1 and Zone 2?
CDN data transfer pricing is based on the node location from where the transfers are served, not the end user’s location. The following geographic areas correspond to the zones for Azure CDN as listed above ：
• Zone 1 — Mainland China (Excluding Hong Kong, Taiwan and Macao).
• Zone 2 — North America, Europe, Asia Pacific, Mid-East, Africa, South America, please refer to oversea POP for more information.
Can I designate a CDN data center to provide services to end users?
No. The service will select a CDN data center based on an end user's network configuration, developers cannot decide which CDN data center to use. Users will be provided services according to their ISP's preferred location or a logically determined "closer" (not necessarily physically closer) node.
What’s the difference between Standard CDN service, Standard Plus CDN service and Premium CDN service?
- Standard CDN service refers to static contents acceleration, including Web Acceleration, Download Acceleration and Video-On-Demand Acceleration.
- Standard Plus CDN service refers to live-streaming acceleration.
- Premium CDN service refers to HTTPS with Azure supplied certificate. HTTPS with Azure supplied certificate is a legacy feature that only supports customers in use and will be deprecated starting July 1st 2019.
What factors impact the availability of content in the CDN's local caches, and how can I reduce the need to make frequent origin requests?
The availability of content in the CDN's local caches (often called "cache efficacy" or "offload") will be influenced by many factors, including:
- Expiration (“max-age”) header values
- Overall total size of the developer's content library (how much can be cached)
- Active working set (how much is currently cached)
- Traffic (how much is being provided)
- Cache churn (how often are objects being added to cache, or aging out)
For example, a developer with higher churn and traffic has less cache efficacy than other users because objects are swapped in and out more frequently. This will lead to higher storage and data transfer charges, as more origin requests are required.
To reduce the need to make origin requests, you can set longer max-age headers, thereby allowing the CDN to hold objects longer.
Are all data transfers charged at a higher rate once the amount of data transferred each month exceeds 10 TB?
No. Usage at each tier will be charged according to the rate for that tier. For example, if you generate 50 TB of Standard version CDN data transfers in Zone 1, the first 10 TB will be billed at a rate of ￥0.19/GB, and the remaining 40 TB will be billed at a rate of ￥0.16 per GB.
Do CDN charges include requests to Storage to retrieve data, and data transfers from Storage to the CDN location?
No. When the CDN receives an object request for a non-edge location, it will make a request to Azure Storage to obtain the data. Operations for reading data from Storage and transferring it from Storage to the CDN will be charged at standard data transfer rates.
Support & SLA
If you have any questions or need help, please visit Azure Support to select self-service or any other method to contact us for support.
We guarantee that CDN will respond to client requests and deliver the requested content without error at least 99.9% of the time. We will examine and accept data from any commercially reasonable independent measurement system that you choose to monitor your content. You must select a set of agents from the measurement system's list of standard agents that are generally available and represent at least five different geographical locations in major metropolitan areas of the People's Republic of China. If you want to learn more about the details of our server level agreement, please visit the Service Level Agreement page.