Cascade Regional Airlines' cloud team is choosing a storage account kind for a new workload that needs both blob storage for maintenance photos and table storage for structured inspection metadata, all under one account with the modern feature set including access tiers and lifecycle management? Which account kind should they choose?

A general-purpose v2 (StorageV2) account supports all Azure Storage services — blobs, tables, queues, and files — within a single account, and it is the account kind that supports access tiers (Hot, Cool, Cold, Archive) and lifecycle management policies, making it the correct choice for a workload that needs both blob storage for photos and table storage for structured metadata plus modern tiering features. A BlobStorage account is blob-only by definition, so it cannot host the table storage this workload also requires, immediately disqualifying it regardless of its tiering support. A legacy general-purpose v1 account does support multiple services but predates and lacks full support for access tiers and lifecycle management in the way v2 does, and Microsoft recommends upgrading v1 accounts to v2 specifically to gain those features. A Premium block blob storage account is blob-only, optimized purely for high-performance blob workloads, does not support table storage, and does not support access-tier or lifecycle-management tiering at all. A concrete check: before provisioning, confirm in the Azure portal's account-creation blade that 'StorageV2 (general purpose v2)' is selected as the account kind, since it is easy to accidentally leave a legacy default selected in older automation templates.