Review overwrite intent before a PowerShell block-blob upload

Source facts

Microsoft says Set-AzStorageBlobContent creates a missing blob but prompts before overwriting an existing one. Supplying Force bypasses that overwrite confirmation. The upload identifies the local file, destination container, and storage context as separate inputs. Microsoft Learn

Applicability

This guide applies to an Azure PowerShell block-blob upload, particularly when an automation script could target an object that already exists.

DSE recommendation

DSE recommends making overwrite behavior an explicit decision in the upload request. Record the local source, storage account, container, and intended blob name before running the command. For a batch, enumerate the input files and review naming collisions before enabling unattended replacement. Agree how the current destination content will be protected or recovered when replacement is authorized, and keep that decision visible in the script’s operational handoff.

Verification

Run the approved upload and inspect the returned account, container, and object information. Compare the destination content with the intended local input and confirm the observed outcome for any pre-existing object. Retain the transfer result and the overwrite authorization together. Treat an unexpected prompt or replacement as a finding to investigate before extending the operation to more files.

Official references

• Microsoft: Manage block blobs with PowerShell – Azure Storage | Microsoft Learn