If you're running your WordPress site on Microsoft Azure, you may want to consider utilizing the CDN service that is available. By using the CDN service, you can host your static content such as images, scripts, and other theme components from the 31 different point of presence locations provided.
When you're trying to scale and provide content around the globe, the CDN provides a cost effective way to send static content to more users.
Before configuring WordPress, a few assumptions are made:
From the old Azure Management Portal:
Something to keep in mind: it may take some a few hours for all of your files to be propagated to the CDN service.
Note: if you want to optionally map a CNAME to this service so that you could have an address like cdn.mydomain.com, you can do that through this management portal area. When you set a CNAME, this also can take a few hours to propagate.
This is probably the most important part of this tutorial: this is what actually ties your statically-rendered, cached files to referencing the new Azure CDN for static content.
Note: if you're running a multi-site, especially one that utilizes multiple domains, you'll need to go to each domain's dashboard and configure these settings.
WP Super Cache needs to be configured for preload mode. Preload mode will cache every published post and page on the site, creating statically-rendered pages for non-authenticated users. This will give us content to serve through the CDN.
Doing this is easy; from the WordPress admin dashboard:
In the event that some cache was generated, you may want to Delete Cache on All Blogs under the Contents panel.
You should be all set; be sure to test your site to verify everything is hitting your proxy properly. Keep in mind it may take a few hours for all of your site content to propagate to your proxy; so you may have to flip back to the normal super cache behavior until the process is completed.