The Azure Files hot tier is an HDD-backed choice for a file share. It sits between transaction optimized and cool: storage costs less than transaction optimized, while transactions cost slightly more. That makes it worth considering when storage charges matter but files are still accessed often enough that cool-tier transaction costs would add up. section 5.4
Choose the tier by weighing storage against access costs:
- Transaction optimized favors workloads with many transactions; storage costs more than hot. section 5.4
- Hot trades slightly higher transaction costs for slightly lower storage costs than transaction optimized. section 5.4
- Cool has the cheapest storage and highest transaction costs of these file-share tiers. section 5.4
Set the tier on a file share
When creating a share with PowerShell, use the `AccessTier` parameter: `New-AzRmStorageShare -ResourceGroupName BanningRG -StorageAccountName banningstorage -Name bannedfiles -AccessTier Hot -QuotaGiB 1024`. The example adapts a transaction-optimized share command by selecting Hot instead; `QuotaGiB` specifies the share’s provisioned size. section 5.4
Don’t confuse this with the Blob Storage hot tier. Blob hot is described in terms of readily available, frequently accessed data and can participate in blob lifecycle transitions to cool or archive; those blob rules are not a file-share configuration example. section 5.3.1 section 9.5.1
