Blob Storage stores unstructured object data. A blob can be any type of text or binary data, such as a document, media file, or application installer. Blob storage is also referred to as Object storage.
    Table Storage stores structured datasets. Table storage is a NoSQL key-attribute data store, which allows for rapid development and fast access to large quantities of data.
    Queue Storage provides reliable messaging for workflow processing and for communication between components of cloud services.
    File Storage offers shared storage for legacy applications using the standard SMB protocol. Azure virtual machines and cloud services can share file data across application components via mounted shares, and on-premises applications can access file data in a share via the File service REST API.

    
Container -> Blobs
Table -> Entities
Queue -> Messages
Share -> Directories / Files

Access Tier

attribute which can be specified during account creation and modified later as needed. There are two types of access tiers that can be specified based on your data access pattern:

    A Hot access tier which indicates that the objects in the storage account will be more frequently accessed. This allows you to store data at a lower access cost.
    A Cool access tier which indicates that the objects in the storage account will be less frequently accessed. This allows you to store data at a lower data storage cost.

Block blobs are optimized for streaming and storing cloud objects
Append blobs
Page blobs are optimized for representing IaaS disks and supporting random writes

Table storage is a key-attribute store, meaning that every value in a table is stored with a typed property name. The property name can be used for filtering and specifying selection criteria. A collection of properties and their values comprise an entity. Since Table storage is schemaless, two entities in the same table can contain different collections of properties, and those properties can be of different types.

OS disk And Data disks

When an Azure virtual machine is created, two disks are automatically attached to the virtual machine.

1. Operating system disk

2. Temporary disk

OS disk

 - sda on Linux

 - The disk caching configuration of the OS disk is optimized for OS performance.

 * It should not host applications or data. For applications and data, use a data disk

Temporary disk - Temporary disks use a solid-state drive that is located on the same Azure host as the VM.

 - sdb on Linux

 - for operations such as temporary data processing

 * if the VM is moved to a new host, any data stored on a temporary disk is removed.

Ephemeral OS Disks - This type is non-persistent (i.e. volatile) storage

 * a result of a deallocate (stop) and start command, hardware or VM crash, or Azure fabric maintenance,
   the local storage is wiped clean and any data stored on it is lost.

Data disks

Additional data disks can be added for installing applications and storing data.

Data disks should be used in any situation where durable and responsive data storage is needed.

The size of the virtual machine determines how many data disks can be attached to a VM.