• https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction

• storage accounts provide the logical container/namespace for storage services like, blob containers, file shares, queues and tables.
• By default, storage accounts are accessible from any network, including the Internet.
• If Public Access is enabled, but limited to certain networks, VNet traffic to the storage accounts will go over the Microsoft backbone and not the Internet, even though it is still going to a public endpoint.
• Blob containers are the only storage type that supports anonymous (unauthenticated access)

A massively scalable object store for text and binary data. Also includes support for big data analytics through Data Lake Storage Gen2.

• https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction

• block blobs
  • used for text and binary files
  • optimized for uploading large amounts of data efficiently
• append blobs
  • optimized for append operations. log files is a common use case
• page blobs
  • support random read/write operations for things like VHD disk images for VMs

Azure Files provides managed file shares that are accessible via SMB or NFS.

If you disable the public endpoint for a storage account you can only browse the share from the Azure portal on a machine that can reach the private endpoint (private) IP address.

If you are using Entra Kerberos authentication for Azure Files shares ACL management is only supported in the Azure Portal, not the Windows File Explore or icacls CLI tool.

When you configure an Azure Files share to use Entra Kerberos for authentication an Enterprise App/Service Principle is created. Admin consent needs to be granted to it for authentication to be enabled.

A messaging store for reliable messaging between application components.

A NoSQL store for schemaless storage of structured data.

Block-level storage volumes for Azure VMs.