Azure portal need to mass change tier on a directory within container

For an immediate mass tier change, use AzCopy recursively against the directory’s virtual path; the Azure portal does not provide an immediate bulk Change tier operation for a folder.

Immediate recursive change with AzCopy

Blob “directories” are virtual: the path is part of each blob’s name. AzCopy applies the operation to every supported block blob beneath the specified prefix. Tier changes do not apply to append or page blobs, so verify the directory’s blob types if every item must change.^1^

1. Install AzCopy v10.
2. Authenticate with Microsoft Entra ID using an identity authorized to modify blob data:

      azcopy login
   

   Alternatively, use a SAS with sufficient blob permissions by appending it to the resource URL.^2^
3. Run the recursive operation, replacing the account, container, directory, and target tier:

      azcopy set-properties \
        'https://<storage-account>.blob.core.windows.net/<container>/<directory>' \
        --block-blob-tier=cool \
        --recursive=true
   

   Valid target tiers include hot, cool, cold, and archive, subject to the storage account and blob supporting that tier. In Windows Command Prompt, use double quotes instead of single quotes.^1^
4. Review the AzCopy summary for failed or skipped objects, then inspect several blobs in Storage account → Containers → container → directory to verify their Access tier.

Changing tiers with azcopy set-properties is currently documented as a preview capability.^1^

Portal-only alternative: lifecycle management

For automatic, age-based tiering rather than an immediate bulk edit:

1. Open the storage account in the Azure portal.
2. Select Data management → Lifecycle management → List View → Add a rule.
3. On Details, select Limit blobs with filters and the applicable blob type.
4. Under Base blobs, choose the target tier and a time-based condition, such as days since modification.
5. Under Filter set, enter:

      <container-name>/<directory-path>
   

6. Select Add.

The prefix is case-sensitive, must start with the container name, and does not support wildcards. For example, documents/reports/2026 matches blobs whose names begin with reports/2026 in the documents container.^3^

Lifecycle management runs once per day and evaluates time-based conditions, so it is not an immediate portal equivalent to the recursive AzCopy operation.^4^

Tier restrictions to check

• Lifecycle tier actions do not support append blobs, page blobs, or blobs in premium block blob accounts.
• Archive lifecycle actions additionally do not support encryption-scoped blobs or blobs in ZRS, GZRS, or RA-GZRS accounts.^3^
• Moving an archived blob back to Hot, Cool, or Cold is a rehydration operation and is not immediate. Also review existing lifecycle rules, because an age-based rule can move a rehydrated blob back to Archive.^2^

References

1. Set a blob's access tier
2. Replace blob properties and metadata by using AzCopy v10
3. Azure Blob Storage lifecycle management policy structure
4. Configure a lifecycle management policy