How I Used Blob Storage to Host My Podcast .mp3 Files

By David Voyles

I host a podcast called The Indie Dev Podcast where I interview game developers from around the world in 30 minute segments. I’m always fascinated by what people are able to create, and I’m even more curious about how they make these games happen.

I store the most recent episodes of the podcast on PodOmatic, which allows them to be picked up by iTunes and other podcast feed readers, but I am limited by the number of podcast episodes that I can store at once because I am using the free tier. My older episodes are lost unless I upgrade to the premium tier.

What Problem Does Blob Storage Solve?

With blob storage, I can take all of my .mp3s, store them in a container, and then allow the public to download them from the container.

When I upload my files to a blob container, I am given an HTTP endpoint, which I can use as a link to download an episode. Click on this link to download the most recent episode with Michael Hicks. You could do the same for videos that you record, too.

In this tutorial, I’m going to walk you through the steps of how I set up my container to host all of the .mp3s of the podcast.

How Does Blob Storage Work?

Blob01 - Storage diagram

Blob storage is a service for storing large amounts of unstructured data, such as text or binary data, that can be accessed from anywhere in the world via HTTP or HTTPS. You can make these files public or private as well, which means that you can use it as a storage repo for your own content for only you to access, or perhaps use it as a cost-effective way to store large amounts of media to share with others.

Common uses of Blob storage include:

  • Serving images, documents, audio, or video directly to a browser
  • Storing files for to be distributed to others
  • Streaming video and audio
  • Performing secure backup and disaster recovery

You can find out more about Blob Storage here.

Blob concepts and terms

  • Storage Account: All access to Azure Storage is done through a storage account.

  • Container: A container provides a grouping of a set of blobs. All blobs must be in a container.

  • Blob: A file of any type and size. There are two types of blobs that can be stored in Azure Storage: block and page blobs. Most files are block blobs, and we’re going to use those for this tutorial. A single block blob can be up to 200 GB in size.

  • URL format: Blobs are addressable using the following URL format:
    The following example URL could be used to address one of the blobs in the diagram above:

How Do I Get Blob Storage?

You’ll need a cloud storage solution like Azure. You can sign up for a free Azure trial, or reach out to me about information on how to obtain a BizSpark account. This is what I use to host the files but you can follow along if you prefer other solutions too.

Creating a Storage Account

You’ve got an understanding of how blob storage works now, as well why you’d want to use it. Let’s go through the process of creating an account and a container. This is directly from the blob storage blogs on the Azure portal:

To use Azure storage, you’ll need a storage account. You can create a storage account by following these steps. (You can also create a storage account by using the Azure service management client library or the service management REST API.)

Log into the Azure Management Portal.

At the bottom of the navigation pane, click NEW.

Blob02 - New

Click DATA SERVICES, then STORAGE, and then click QUICK CREATE.

Blob03 - Quick Create

In URL, type a subdomain name to use in the URI for the storage account. This value becomes the host name within the URI that is used to address Blob, Queue, or Table resources for the subscription.

Choose a Region/Affinity Group in which is closest to your current location.

Optionally, you can select the type of replication you desire for your account. Geo-redundant replication is the default and provides maximum durability, meaning your files will be backed up across multiple datacenters in the same area. So if Godzilla takes out one datacenter, your info is still backed up in another one.


You’re ready to roll. Now you can create a container which will host your files.

Creating a Container

In the Azure portal, click on the Storage icon on the left hand side of the screen. A new screen will appear with the name of the account you created above. In my case, it is called blobindiedev.

Blob04 - Create Container

Click on the name of the blob, then Containers at the top of the page. You’ll make a new one here. At the bottom of the page, click on Add to create a new container.

Blob05 - Add

I called mine podcastep , as this will hold all of my episodes.

By default, the container is private and can be accessed only by the account owner. To allow public read access to the blobs (.mp3s)in the container, but not the container properties and metadata, use the “Public Blob” option. To allow full public read access for the container and blobs, use the “Public Container” option. We want Public Container.

Blob06 - New Container

We’re ready to upload files to this container from Visual Studio now.

Uploading Files from Visual Studio

For this part you’ll need Visual Studio. You can download the VS 2013 Community Edition for free from here. You’ll also need the Azure SDK to access your Azure account from Visual Studio. Download the SDK here. You’ll need the SDK that matches the version of Visual Studio you are using. If you have VS 2013 installed, you’ll want to use the VS 2013 Azure SDK.

With that installed, open Visual Studio, click on the Server Explorer and look for the Azure button. Click on Storage and it should ask you to log in to your account.

Blob07 - Upload from VS

Click on Storage and you should see the new Blob storage account you created as well as container which will host the episodes.

Blob08 - Blob Storage Account

Click on the Blobs icon / text to see your container. I see podcastep, as well as any files I have uploaded there.

Blob09 - Container

To upload your own files, click on the Upload Blob icon, which is an arrow pointing to a horizontal line.

Blob10 - Upload Blob Icon

A pop-up window will appear, and ask you to browse to the file you want to upload.

Blob11 - Upload New File

In my case, I’m looking for podcast episodes. You should see the Azure Activity Log appear at the bottom of the screen, which notifies you of the file’s current status.

Blob12 - Azure Activity Log

Once it has completed uploading, right click on the file, and copy the URL.

Blob13 - Copy Blob URL

That URL is how others can download your files now! On my webpage I provide a link to that URL on every episode, and folks now all of my episodes are made available!

If you navigate back to the Azure Portal, you can see that they are all there too.

Blob14 - Azure Portal


Azure Blob Storage is a cost-effective way of saving and service content across the internet. The blob storage page has more information, but hopefully after this, you understand the value in it. I can record my podcast and easily serve it to anyone around the world, without having to pay monthly fees or build any hardware on my own. Best of all, it took me a total of 5 minutes to get the files online.

Any questions? Feel free to reach out.

Here’s a full list of the tutorials in this series:

This article is part of the web dev tech series from Microsoft. We’re excited to share Microsoft Edge and the new EdgeHTML rendering engine with you. Get free virtual machines or test remotely on your Mac, iOS, Android, or Windows device @ dev.modern.ie


Thank you for this great article David.

I’ve been doing this for my podcast since January, after moving my podcast from LibSyn, but I’ve added some more things:

  1. I’ve also enabled the Microsoft Azure CDN and linked that to the Blob storage containing my podcast episodes.
  2. I’ve added a nice URL. This way I can take my podcast to, say, Amazon S3 and keep that URL without the need of changing the RSS feed.
  3. I’ve also created a small PHP script that writes into a MySQL database each time an episode is loaded to keep track of all hits. I am calling this script from a nice domain like traffic.mypodcasturl.com and the script adds the data into the DB table then responds with the appropriate MP3 file for my podcast. I can provide more details on this in case anyone is interested.

Having the episodes uploaded using Visual Studio is OK for some. I am a .NET developer and Microsoft Partner and I need to have Visual Studio installed, but there are some who don’t need that (not even the Community version of Visual Studio). Thus, anyone who don’t want Visual Studio can upload their episodes using Azure Storage Explorer for Windows or Cyberduck for Mac OS.

Good luck!

-- Razvan


Thanks for the detailed response!

You raise a great point about enabling the CDN and linking the blob storage to that. I should include that in another article, or add an ammendment to this one. It's a great way to improve performance for the end user.

How did you add a nice URL? Did you use a shortner service of some type?

I agree -- Visual Studio is not for everyone. Moreover, it can be cumbersome to add each file individually. I also go bac kadn forth between OSX and Windows, so I should look into Cyberduck. Thanks for the recommendation!


For the Azure Blob Storage you have a "Manage Domain" link which will open a modal window titled "Manage Custom Domain" where you may add a custom domain, confirm that you own it (by adding the CNAME to your DNS provider's zone editor) and it's set.

For the CDN Custom Domain, please check this.

Apparently Cyberduck is available for Windows too, so if you like it you may use it both on Mac OS and Windows.

A fellow podcaster told me about CloudBerry Explorer, which is also a good tool.

Good luck!

-- Razvan



Because We Like You
Free Ebooks!

Grab SitePoint's top 10 web dev and design ebooks, completely free!

Get the latest in Front-end, once a week, for free.