Using Azure CDN
This topic walks through enabling Azure CDN by creating a new CDN profile and endpoint.
For an introduction to how CDN works, as well as a list of features, see the CDN Overview.
A CDN profile is a collection of CDN endpoints. Each profile contains one or more CDN endpoints. You may wish to use multiple profiles to organize your CDN endpoints by internet domain, web application, or some other criteria.
By default, a single Azure subscription is limited to eight CDN profiles. Each CDN profile is limited to ten CDN endpoints.
CDN pricing is applied at the CDN profile level. If you wish to use a mix of Azure CDN pricing tiers, you will need multiple CDN profiles.
To create a new CDN profile
In the Azure Portal, in the upper left, click New. In the New blade, select Media + CDN, then CDN.
The new CDN profile blade appears.
Enter a name for your CDN profile.
Select a Location. This is the Azure location where your CDN profile information will be stored. It has no impact on CDN endpoint locations.
Select or create a Resource Group. For more information on Resource Groups, see Azure Resource Manager overview.
Select a Pricing tier. See the CDN Overview for a comparison of pricing tiers.
Select the Subscription for this CDN profile.
Click the Create button to create the new profile.
To create a new CDN endpoint
In the Azure Portal, navigate to your CDN profile. You may have pinned it to the dashboard in the previous step. If you not, you can find it by clicking Browse, then CDN profiles, and clicking on the profile you plan to add your endpoint to.
The CDN profile blade appears.
Click the Add Endpoint button.
The Add an endpoint blade appears.
Enter a Name for this CDN endpoint. This name will be used to access your cached resources at the domain
In the Origin type dropdown, select your origin type. Select Storage for an Azure Storage account, Cloud service for an Azure Cloud Service, Web App for an Azure Web App, or Custom origin for any other publicly accessible web server origin (hosted in Azure or elsewhere).
In the Origin hostname dropdown, select or type your origin domain. The dropdown will list all available origins of the type you specified in step 4. If you selected Custom origin as your Origin type, you will type in the domain of your custom origin.
In the Origin path text box, enter the path to the resources you want to cache, or leave blank to allow cache any resource at the domain you specified in step 5.
In the Origin host header, enter the host header you want the CDN to send with each request, or leave the default.
For Protocol and Origin port, specify the protocols and ports used to access your resources at the origin. At least one protocol (HTTP or HTTPS) must be selected.
The Origin port only affects what port the endpoint uses to retrieve information from the origin. The endpoint itself will only be available to end clients on the default HTTP and HTTPS ports (80 and 443), regardless of the Origin port.
Azure CDN from Akamai endpoints do not allow the full TCP port range for origins. For a list of origin ports that are not allowed, see Azure CDN from Akamai Allowed Origin Ports.
Accessing CDN content using HTTPS has the following constraints:
- You must use the SSL certificate provided by the CDN. Third party certificates are not supported.
- You must use the CDN-provided domain (
<endpointname>.azureedge.net) to access HTTPS content. HTTPS support is not available for custom domain names (CNAMEs) since the CDN does not support custom certificates at this time.
Click the Add button to create the new endpoint.
Once the endpoint is created, it appears in a list of endpoints for the profile. The list view shows the URL to use to access cached content, as well as the origin domain.
The endpoint will not immediately be available for use, as it takes time for the registration to propagate through the CDN. For Azure CDN from Akamai profiles, propagation will usually complete within one minute. For Azure CDN from Verizon profiles, propagation will usually complete within 90 minutes, but in some cases can take longer.
Users who try to use the CDN domain name before the endpoint configuration has propagated to the POPs will receive HTTP 404 response codes. If it's been several hours since you created your endpoint and you're still receiving 404 responses, please see Troubleshooting CDN endpoints returning 404 statuses.