liveBook · Manning

Storage account

A storage account is a top-level Azure resource that provides a namespace, access boundary, and configuration for storage services and their data.

How 4 Manning books explain it

Microsoft Azure in Action

An Azure Storage account is an Azure resource that provides a namespace and configuration boundary for storage services and their data.

How it is used
Uses storage accounts to organize Azure data services for applications, shared files, and connected workflows.
How deep it goes
Defines the logical container and works through portal and PowerShell creation, while initially leaving most portal settings at their defaults.
Examples
Uses a PowerShell account-creation command, a hybrid file-share setup, and a blob connection for an AI pipeline.
What you can do after
Operate/configure it through the Azure Portal or PowerShell, then connect its storage to workloads with appropriate permissions.

Read how Microsoft Azure in Action explains storage account →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A storage account is an Azure resource that provides an access boundary and configuration for stored data.

How it is used
Deploys cloud file storage behind a microservice that retrieves private videos for application customers.
How deep it goes
Explains account creation, containers, uploads, credentials, and retrieval code, while deferring vendor-specific storage internals.
Examples
Uses an Azure portal account, a videos container, an uploaded test video, environment variables, and a retrieval service.
What you can do after
Operate/configure private Azure file storage and connect a Node.js microservice to retrieve stored videos.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains storage account →

Practical Automation with PowerShell: Effective scripting from the console to the cloud

An Azure storage account is an Azure resource that provides a unique namespace and access boundary for Azure Storage services and data objects.

How it is used
Provides the storage destination and access boundary for files handled by Azure automation.
How deep it goes
Explains naming, regional placement, SKU configuration, key-based contexts, containers, uploads, and deletion safeguards without descending into storage-service internals.
Examples
Uses timestamped account names, Standard_LRS and Cool settings, and a ZIP-to-blob runbook with duplicate detection.
What you can do after
Operate storage uploads by creating an account, authenticating with a key-based context, organizing blobs in containers, and validating failures.

Read how Practical Automation with PowerShell: Effective scripting from the console to the cloud explains storage account →

Snowflake Data Engineering

An Azure storage account is a top-level resource that provides access to Azure Storage services and their data containers.

How it is used
Supports Snowflake external-stage access to files stored in an Azure container.
How deep it goes
Explains resource creation, container setup, naming constraints, uploads, and integration inputs.
Examples
Uses bakeryorders001/orderfiles and speedyorders001/speedyservicefiles with sample JSON order files.
What you can do after
Operate/configure Azure resources and connect a container to Snowflake through a storage integration.

Read how Snowflake Data Engineering explains storage account →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.