Metadata Xfer Not Supported Today

All of those attributes travel with the payload when you move data the same system (e.g., copy a file on a Linux box). But once you cross a boundary—different OS, different API, different cloud provider— the contract changes .

# 2️⃣ Extract only the fields you care about (e.g., custom user metadata) CUSTOM=$(jq -r '.Metadata' src-meta.json) metadata xfer not supported

| Type | Example | Where you see it | |------|---------|------------------| | | Created , Modified , Accessed | File systems, S3 Object Versioning | | Permissions / ACLs | rw-r--r-- , IAM policies | POSIX FS, Azure Blob BlobACL , S3 Bucket ACL | | Custom tags / key‑value pairs | department=finance , env=prod | S3 Object Tags, Azure Blob Tags, GCS Labels | | Content‑type / encoding | application/json , gzip | HTTP headers stored with the object | | Checksums / ETags | MD5 hash, x-amz-checksum | Used for integrity verification | | Retention / Legal Hold | retain-until=2028-12-31 | S3 Object Lock, Azure Immutable Blob | All of those attributes travel with the payload

# 2️⃣ Copy blob *without* tags first az storage blob copy start \ --destination-blob path/file.txt \ --destination-container destc \ --destination-account-name destacct \ --source-uri "https://srcacct.blob.core.windows.net/srcc/path/file.txt" Accessed | File systems