Azure Blob Storage on IoT Edge now includes Tiering and Time-to-Live functionalities

This post has been republished via RSS; it originally appeared at: Storage at Microsoft articles.

First published on TECHNET on Mar 07, 2019
This post was authored by , PM on the High Availability and Storage team. Follow her @arnuwish on Twitter.

Azure Blob Storage on IoT Edge is a light-weight Azure consistent module which provides local block blob storage, available in public preview. We are excited to introduce tiering and time-to-live functionalities to our "Azure Blob Storage on IoT Edge" module. Currently both these new features are available for Linux AMD64 and Linux ARM32, support for Windows AMD64 is coming soon.

Tiering is a configurable functionality, which allows you to automatically upload the data from your local blob storage to Azure with intermittent internet connectivity support. It allows you to: 

  • Turn ON/OFF the tiering feature
  • Choose the order in which the data will be uploaded to Azure like FIFO or LIFO
  • Specify the Azure Storage account where the data will be uploaded.
  • Specify the containers you want to upload to Azure.
  • Do full blob tiering(using Put Blob operation) and block level tiering (using Put Block and Put Block List operations).

When your blob consists of blocks, it uses block-level tiering to upload your data to Azure. Here are some of the common scenarios: 

  • Your application updates some blocks of a previously uploaded blob, this module will upload only the updated blocks and not the whole blob.
  • The module is uploading blob and internet connection goes away, when the connectivity is back again it will upload only the remaining blocks and not the whole blob.

Time-to-Live (auto-expiration) is a configurable functionality where this module automatically deletes your blobs from local blob storage when TTL(Time to Live) expires. It allows you to: 

  • Turn ON/OFF the Time-to-Live (auto-expiration) feature
  • Specify the TTL in minutes



Azure Blob Storage on IoT Edge – Version 1.1 (March 07, 2019)

In the diagram below, we have an edge device pre-installed with Azure IoT Edge runtime. It is running a custom module to process the data collected from the sensor and saving the data to the local blob storage account. Because it is Azure-consistent, the custom module can be developed using the Azure Storage SDK to make calls to the local blob storage. Then it will automatically upload the data from specified containers to Azure while making sure your IoT Edge device does not run out of space.

This scenario is useful when there is a lot of data to process. For example, data from industries who captures survey and behavioral data, research data, financial data, hospital data and so on. It is efficient to do the processing of data locally because there is a lot of data that is continuously being captured. Azure Blob Storage on IoT Edge module allows you to store and access such data efficiently, process if required, and then automatically upload that data for you to Azure and automatically deletes the old data from IoT Edge device to make space for new data.


Current Functionality:

With the current public preview module, the users can: 

  • Store data locally and access the local blob storage account using the Azure Storage SDK.
  • Auto tiering from IoT Edge device to Azure
  • Delete the data from IoT Edge device after a specified amount of time
  • Reuse the same business logic of an app written to store/access data on Azure.
  • Deploy multiple instances in an IoT Edge device.
  • Use any Azure IoT Edge Tier 1 host operating system

Next Steps:


  • Releasing tiering and time-to-live features for Windows AMD64
  • Integration with EventGrid, to light up the event-driven computing scenario on IoT Edge platform
  • Reverse tiering: On-demand tier back the data from Azure to IoT edge device
  • Support more sophisticated tiering and TTL policies, based on early customer feedback
  • Expanding the scope of Azure Storage consistency, e.g. Append Blob support

More Information:


Find more information about this module at




Your feedback is very important to us, to make this module and its features useful and easy to use. Please share your feedback and let us know how we can improve.

You can reach out to us at

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.