1 For Zone details, please refer to the FAQ below.2 1 TB = 1,024 GB The Australia Regions are available only to customers with billing addresses in Australia and New Zealand.

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.

Support & SLA

Technical support for all generally available Azure services, including CDN, is offered through Azure Support starting at $--/month. Billing and subscription management support is provided at no cost.

We guarantee that at least 99.9% of the time CDN will respond to client requests and deliver the requested content without error. We will review 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 geographically diverse locations in major worldwide metropolitan areas. For more details, visit the SLA page.

Asia Pacific

Japan

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.

No. When the CDN receives a request for an object that is not at an edge location, it makes a request to Azure Storage to obtain the data. The cost of reading data from Storage and transferring data from Storage to CDN is based on regular Storage and Data Transfer charges.

Availability of content in CDN's local caches (often called "cache efficacy" or "offload") is influenced by multiple factors including:

Expiration ("max-age") header values

Overall total size of the developer's content library (how much could be cached)

Active working set (how much is currently cached)

Traffic (how much is being served)

Cache churn (how often are objects being added to cache, or aging out)

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.