Azure Files and Queue Storage

Azure Files provides fully managed cloud-based file shares accessible over the industry-standard SMB (Server Message Block) and NFS (Network File System) protocols. This means you can mount an Azure file share on Windows, Linux, or macOS machines using the same mechanisms you use for network file shares on a local corporate network. Unlike Blob Storage, which requires a specific API or SDK to access, Azure Files works seamlessly with any application that can read from a mapped drive or UNC path.

Azure Files is designed for several common enterprise scenarios: Lift-and-shift shared storage — migrate applications that rely on on-premises file servers to use Azure Files instead, with no application code changes. Hybrid access — on-premises servers and Azure VMs can both mount the same share simultaneously using Azure File Sync. Configuration and settings shares — store config files in a share and mount them from multiple App Service instances or containers. Developer tool shares — share IDE plugins, build tools, and scripts across a development team.

Azure File Sync extends Azure Files to on-premises environments by synchronising an Azure file share with a Windows Server file server. The Windows Server acts as a local cache of frequently accessed files; files that are not accessed recently are replaced by cloud tiering placeholder files that appear in the directory but do not consume local disk space. When a user opens a placeholder, Azure File Sync transparently downloads the actual file from Azure in the background. This gives users fast local access while reducing the on-premises storage footprint.

Azure Files offers two performance tiers: Standard (HDD-backed) — cost-effective for general file sharing, batch workloads, and home directories. Billed per GB stored per month. Premium (SSD-backed) — designed for high-IOPS scenarios like databases, enterprise applications, and financial services systems. Billed per provisioned GB (you pre-allocate capacity) rather than per GB consumed. Choose Premium when your workload needs consistent, low-latency file I/O. Standard is sufficient for most office file sharing scenarios.

Azure Queue Storage is a service for storing large numbers of messages that can be accessed from anywhere via authenticated HTTP/HTTPS calls. Queues enable asynchronous, decoupled communication between application components — one component (the producer) adds messages to the queue, and another component (the consumer) retrieves and processes them at its own pace. This decoupling allows the producer and consumer to scale independently and prevents the producer from being blocked if the consumer is slow or temporarily unavailable.

A message in Azure Queue Storage can be up to 64 KB in size and can be retained for up to 7 days. When a consumer retrieves a message, the message becomes invisible for a configurable period (the visibility timeout, default 30 seconds). If the consumer processes the message and deletes it before the timeout, the message is permanently removed. If the consumer fails before deletion, the message becomes visible again for another consumer to pick up — providing at-least-once delivery semantics for fault tolerance.

Azure offers two queue services, and it is important to know when to use each: Queue Storage — simple, very large queues (up to 500 TB), HTTP-based polling, best for basic producer-consumer decoupling with millions of messages. Azure Service Bus — enterprise messaging with advanced features: message ordering (FIFO), dead-letter queues, sessions, duplicate detection, topics with multiple subscribers, and transactions. Use Queue Storage for simple decoupling at massive scale. Use Service Bus when you need enterprise messaging guarantees or publish-subscribe fan-out to multiple consumers.

A very common pattern is pairing Queue Storage with Azure Functions: a web application adds order messages to a queue (the producer), and an Azure Function with a Queue trigger (the consumer) processes each order. The Function scales automatically based on the number of messages waiting in the queue — more messages means more function instances. This pattern decouples the web frontend from the order processing logic, ensures orders are not lost even if the processing service is temporarily down, and allows the system to handle traffic bursts gracefully.

Azure Table Storage is a NoSQL key-value store for storing structured, non-relational data at massive scale and low cost. Data is organised in tables (not relational tables — think collections), and each row is an entity with a partition key, row key, and up to 252 additional properties of mixed types. Table Storage is schema-less — different rows in the same table can have different properties. It is best for scenarios needing fast lookups by key (like device telemetry or user preferences) but does not support JOINs or complex queries.

Azure Files supports two authentication methods: Storage account key — grants full access using the account's master key; simple but coarse. Identity-based authentication — authenticate using Microsoft Entra ID (for cloud-only VMs) or Active Directory Domain Services (for hybrid, on-premises-joined machines). Identity-based auth enables per-user and per-group access control lists (ACLs) on folders and files within the share, just like on-premises Windows file servers. This is the recommended approach for multi-user enterprise file shares.

To summarise the storage service decision: Blob Storage — for unstructured objects (images, video, backups, arbitrary files) accessed via API or URL. Azure Files — for structured file systems requiring OS-mounted drives via SMB/NFS, shared by multiple servers or users. Queue Storage — for durable, asynchronous messaging between application components. Table Storage — for structured NoSQL key-value data needing fast key-based lookups at low cost. Cosmos DB is the more powerful, scalable successor to Table Storage for complex NoSQL requirements.

Test your understanding of Microsoft Azure Fundamentals (AZ-900) concepts from this lesson.

In this lesson you learned: Azure Files provides SMB/NFS cloud file shares that integrate with existing applications and can be synchronised with on-premises servers via Azure File Sync, Queue Storage enables reliable asynchronous decoupling between application components with at-least-once message delivery, and Table Storage offers a cost-effective schema-less NoSQL key-value store for structured data. Next up we cover disk storage types and storage security with SAS tokens and private endpoints.