liveBook · Manning

Storage account

As explained in 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.

An Azure storage account is an Azure resource used to store files uploaded by automation. It belongs in a resource group and provides the storage boundary used by Azure Storage operations. section 8.2 section 8.4

Provisioning a storage account requires several operational decisions:

  • Choose a globally unique name containing 3–24 lowercase letters and numbers; appending a timestamp helps avoid collisions. section 8.2.3
  • Select a region compatible with related resources such as an Azure Automation account and Log Analytics workspace. section 8.2.3
  • Configure the account with a resource group, location, SKU, and access tier; the demonstrated configuration uses Standard_LRS and Cool. section 8.2.3
  • Use a storage context authenticated with an account key, then organize uploaded files in containers that can separate content and access. section 8.4

ZIP archive upload automation

A PowerShell runbook checks a local folder for ZIP files, obtains a storage account key, creates a storage context and container, verifies whether each blob already exists, uploads missing files, and deletes local files only after a successful upload. Azure Storage cmdlets provide built-in hash checks that allow execution to stop when an upload fails. section 8.4

Figure 8.1 Azure resources required for the storage upload automation. All resources are grouped into a single Resource Group, which resides under a subscription.

Shows how the storage account fits with the resource group, Azure Automation account, and Log Analytics workspace required for storage-upload automation. section 8.2

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

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 it assumes
Assumes an Azure subscription, Azure PowerShell modules, authentication, and awareness of resource-group and regional planning.
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.
How it connects
Connects storage accounts with resource groups, Azure Automation, Log Analytics, storage containers, Azure Blob Storage, and PowerShell.

Also explained in

Compare how 4 books explain storage account →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Practical Automation with PowerShell: Effective scripting from the console to the cloud. The section links point to the parts of the book it draws on.