Azure Storage: inventory first, approve data transfer

Use Azure MCP or CLI to inspect storage and distinguish listing, download, and upload.

Skills

Confirm account and resource scope. Prefer read-only inventory with Azure MCP `storage_account_list`, `storage_container_list`, and `storage_blob_list`. Explain Blob/File/Queue/Table/Data Lake fit, access-tier, and redundancy differences; Cool/Cold/Archive have different access and rehydration costs. Before downloading, confirm blob name, sensitivity, and local output path. Before upload/overwrite via `storage_blob_put` or `az storage blob upload`, confirm destination and overwrite policy to avoid writing production data accidentally. Access uses configured identity/RBAC; never print connection keys.

Permissions

Prerequisites

For Azure Blob, File, Queue, Table, or Data Lake choices and operations, including tiers and redundancy.
Confirm account, container/share, target object, and read/write intent.

Permissions

May list accounts/containers/objects and download or upload blobs; uploads write data to cloud storage.
Uses configured Azure identity/RBAC; downloads write a local workspace file.

Limitations

Inventory read-only first. Confirm object, data classification, destination, and overwrite behavior before transfer. Archive blobs require rehydration.