Azure Content Delivery Network (CDN). You have a problem with latency whenever users in Hong Kong access the new company Web Application located in Chicago. You need to lower the latency users experience. Azure CDN enables users to access the data by accelerating data by placing a copy of specified data stored on edge servers close to the end-users. CDN is a perfect solution for lowering latency to centralized web content. Azure CDN can also accelerate dynamic content, which cannot be cached, using various “Optimized for” options. If the dynamic data cannot be stored locally, such as Shopping Cart contents, it remains on the distant web server data store.
Caching rules control how the CDN node or node’s function. Global caching rules control caching for all endpoints in your profile, affecting all endpoint requests. Custom caching rules set one or more custom caching rules for each endpoint in your profile. Custom caching rules match specific paths and file extensions, are processed in order, and override the global caching rule, if set.
Below is a test deployment I created to demonstrate CDN in Storage Accounts. I integrated an Azure Storage account with Azure CDN. The prerequisites are an Azure Account and a Storage Account. As you can see, there are two Azure CDN Endpoints.
Here are a few informative links describing CDN. CDN seems simple, but it can be complicated if implemented CDN without a plan.