Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
Hi Miloš Petrović,
WinSCP cant select tier. Use storage account default tier or lifecycle management policy to move blobs to Cool or Archive automatically. WinSCP itself cant choose Azure Blob access tier during upload. It just uploads the blob and the storage account assigns the default tier, usually Hot unless configured otherwise. WinSCP has no native control over blob tier headers. U also cannot set Archive at container level automatically. Access tier is defined per blob, not per container. A storage account can have a default access tier Hot or Cool, but not Archive. Archive must be set explicitly per blob after upload.
If users only upload files and never read them, the proper approach is one of these, set the storage account default access tier to Cool if that fits ur pattern. U can use a lifecycle management policy to automatically move blobs to Cool or Archive after upload or after 0 days. This is the cleanest solution for WinSCP scenarios.
example )))) move blobs to Archive immediately after creation or after 1 day. That way users upload normally and Azure handles tiering automatically.
rgds,
Alex