This is the final post in a two post series explaining how to utilise Microsoft Azure to serve Microsoft App-V 5.0 content.


For this scenario, we are building on the design from Part 1.

The changes include adding an Azure CDN in front of the Azure Blob Storage. This will allow clients distributed globally to get their App-V content from the [geographically] closest location. The goal is to create a faster, smoother experience for all users in all locations.


If you are following along with the steps in this blog post, I recommend running through the steps in the first part of this series. You will need an Azure Blob Storage account and container set up to publish with the CDN.


1. Create Azure CDN Endpoint

In the Azure Portal, create a new CDN Endpoint. Select the URL of the Storage Account we created in Part 1.

Note: The endpoint shows up straight away in the Azure Portal. The publishing takes around 15 min to be fully set up however.

2. Test URLs

The CDN base URL can be found on the main screen of your CDN endpoint.

This URL is equivalent to the base URL of your Storage Account. For example:

Storage Account URL:

3. Add custom domain (optional)

We can make this URL look a lot nicer by adding a custom domain, eg,

Create a CNAME DNS record from your chosen domain name pointing at your CDN endpoint domain name.

In the settings for your CDN Endpoint, click Manage Domains and add the new domain to the list.

Note: It will take another 15 min for these settings to be replicated out globally.

Custom domains can be used as the base URL. The after waiting for the replication you can use the following PowerShell command to test your CDN.

Add-AppVClientPackage -Path "" | Publish-AppVClientPackage -Global


Microsoft App-V 5.0 makes it really easy to scale the delivery of applications globally. Using Microsoft Azure or similar storage and CDN services, you can create a smooth experience for your users globally.