India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
Azure Blob, Files & Managed Disk Storage Services
Azure Storage is Microsoft's durable cloud storage platform covering Blob Storage for objects, Azure Files for SMB and NFS shares, and Managed Disks for VM block storage. NTSPL designs storage accounts in Indian regions for media houses, universities and insurers, choosing hot, cool, cold or archive tiers, lifecycle rules, redundancy and immutability so each byte sits on the cheapest tier its retrieval need allows.
Microsoft Azure services in scope
The Problem Azure Blob Storage (hot, cool, cold, archive tiers) and Blob lifecycle management Solve
Indian organizations accumulate data faster than they retire it: broadcasters keep every bulletin, labs keep raw instrument output for grant audits, and insurers keep signed proposal forms for decades. On-premises this lands on NAS filers and LTO tape that nobody can search, with refresh cycles every four to five years. Azure Storage separates the question into access frequency, retention obligation and performance, then bills each accordingly. The engineering problem is getting tiering, minimum-retention charges, redundancy and rehydration latency right, because a wrong lifecycle rule either leaves petabytes on the hot tier or triggers early-deletion penalties.
NTSPL starts by profiling the data, not the hardware: object size distribution, last-access age, retrieval SLA and legal retention per dataset. From that we define storage accounts by purpose (active media, archive, compliance records, shared drives), set redundancy per account, and write lifecycle policies keyed to last-access tracking where reads are irregular. For file shares we decide between Azure Files with File Sync caching and full cloud mounting, and for VM disks we provision Premium SSD v2 IOPS and throughput to measured load.
When Azure Blob, Files and Managed Disks Fit Your Data (and When They Don't)
Signals that point to storage on Microsoft Azure
- On-premises NAS or SAN is above 80 percent capacity and the refresh quote assumes all data stays on primary-performance disks.
- More than 60 percent of files on a share have not been opened in 12 months but users still expect them to be findable.
- LTO tape archives are older than two drive generations and restoring a single clip or document takes days.
- An auditor or regulator asks for evidence that records cannot be altered or deleted within the retention period.
- A database VM is buying larger Premium SSD disks only to get more IOPS, leaving most provisioned capacity empty.
When a different approach is better
- Transactional application data that needs queries and joins: use Azure SQL Database or Azure Database for PostgreSQL rather than storing records as blobs.
- Short-lived backups for Azure VMs and SQL databases: Azure Backup Recovery Services vaults handle retention, consistency and restore orchestration better than hand-built blob containers.
- Low-latency shared storage for high-performance computing with thousands of parallel clients: Azure Managed Lustre is built for that pattern, not Azure Files.
Azure Storage Building Blocks: Blob Tiers, Azure Files, File Sync, Premium SSD v2 and WORM
| Service | Role in the architecture | Choose it when |
|---|---|---|
| Azure Blob Storage (hot, cool, cold, archive tiers) | Stores unstructured objects with per-blob access tiers whose storage price falls and read price rises from hot to archive, with archive blobs offline until rehydrated. | Data is written once and read with predictable decay: media, backups, scanned documents, instrument output. |
| Blob lifecycle management | Applies rule-based tier transitions and deletions by prefix, blob index tag, creation time, last-modified time or last-access time. | More than a few terabytes age out of active use on a predictable schedule and manual tiering is not realistic. |
| Azure Files and Azure File Sync | Provides fully managed SMB and NFS file shares, with File Sync caching hot files on Windows Server at branches and tiering the rest to the cloud. | Users and applications depend on mapped drives or UNC paths and the on-premises file server is out of capacity. |
| Azure Managed Disks (Premium SSD v2, Ultra Disk) | Supplies block storage for VMs; Premium SSD v2 and Ultra Disk let capacity, IOPS and throughput be set independently and changed online. | A database or analytics VM needs sustained IOPS above what its capacity-linked Premium SSD tier would give. |
| Immutable storage for Azure Blob Storage | Enforces WORM state through time-based retention policies and legal holds at container or blob-version level, so data cannot be modified or deleted until retention ends. | A regulator, auditor or litigation process requires proof that records were not altered or deleted. |
| Azure Data Lake Storage (hierarchical namespace) | Adds a true directory hierarchy and POSIX-style ACLs to Blob Storage for analytics engines and per-folder permissions. | Multiple teams need directory-level permissions on the same storage account or Spark and analytics tools read the data directly. |
Tiered media, records and shared-file storage in Central India
Tiered media, records and shared-file storage in Central India
Producers and applications write through private endpoints into purpose-specific storage accounts; lifecycle rules move blobs from hot to cool, cold and archive by last-access age, while compliance containers carry locked immutability policies. Branch file servers cache active files via Azure File Sync, and geo-redundant replication copies critical accounts to South India.
Select any component
Tiered media, records and shared-file storage in Central India: click any of its 9 components to see its role and the design choice NTSPL makes for it, or trace the 5-step primary path.
Azure Storage Engineering Decisions: Tiering, Redundancy, Account Layout and Disk Performance
Tier choice and minimum storage durations
Cool, cold and archive tiers carry minimum durations of 30, 90 and 180 days; deleting or moving a blob earlier incurs a prorated charge. Choose cold for content read a few times a year but needed online in milliseconds, archive only where hours of rehydration latency are acceptable. Read costs rise sharply down the tiers, so a dataset scanned monthly by analytics belongs on cool, not cold, even if storage looks cheaper.
Last-access tracking versus last-modified rules
Last-modified rules suit write-once data with predictable decay, such as finished news packages. Where reads are irregular, such as policy documents pulled at claim time, enable last-access-time tracking so a recently read blob is not archived. Combine with the option to move a blob back to hot automatically on access for cool-tier data. Scope rules by prefix or blob index tag so compliance and scratch data never share one rule.
Redundancy per account
LRS keeps three copies in one data centre, ZRS spreads them across three zones, GRS and GZRS add an asynchronous copy in the paired region. NTSPL uses ZRS for active accounts in Central India, GZRS or RA-GZRS for records whose loss is unrecoverable, and LRS for reproducible scratch or proxy files. Because redundancy is set per account, separate datasets with different durability needs into different accounts.
File share model: cloud-only or File Sync hybrid
Mount Azure Files directly when users are on a VNet-connected network with under 30 ms latency to the region. Use Azure File Sync with cloud tiering when branches have limited bandwidth or applications need local SMB performance; the cache holds hot files while cold ones become pointers. Keep each sync group to one share to simplify restore. Choose SSD (premium) shares for profile containers and databases, HDD shares for document stores.
Managed disk performance provisioning
Premium SSD v2 includes a 3,000 IOPS and 125 MB/s baseline and lets IOPS and throughput be raised independently of size, up to 80,000 IOPS per disk. Use it for SQL Server and PostgreSQL data disks. Ultra Disk suits log or transaction-heavy volumes needing sub-millisecond latency beyond that. Neither can be an OS disk, and Premium SSD v2 does not support host caching, so keep OS disks on Premium SSD.
How NTSPL Moves Archives and File Shares into Azure Storage Tiers
Blob and file inventory profiling
Scan source NAS, tape catalogues or existing accounts for object counts, size distribution and last-access age to decide tier boundaries.
Account and container layout
Create purpose-specific storage accounts with redundancy, private endpoints, CMK and RBAC set per account, and a prefix and tag scheme lifecycle rules can target.
Lifecycle and immutability policies
Deploy lifecycle JSON and immutability policies in editable (not yet locked) state, verify behaviour on test containers, then lock compliance policies after sign-off.
Bulk transfer with Data Box or Storage Mover
Move historic data with Azure Data Box for large volumes or AzCopy and Storage Mover over the network, writing directly into the target tier.
File Sync cutover per site
Register branch servers, sync shares to Azure Files, enable cloud tiering and switch DFS namespace targets in a weekend window.
Cost and capacity review
Read blob inventory monthly for the first quarter and adjust tier thresholds, then purchase reserved capacity for stable volumes.
What you receive
Securing Azure Storage Accounts: Private Endpoints, Entra RBAC, CMK and Immutability Policies
The main storage threats are a leaked account key or SAS token, a publicly readable container and ransomware or insider deletion. NTSPL disables shared-key authorization where applications allow, grants Entra ID data roles per container, blocks public access by policy, and puts regulated data behind private endpoints. Soft delete, versioning and locked immutability ensure an attacker with write access still cannot destroy records.
- Shared-key authorization disabled and user-delegation SAS only, so leaked keys cannot grant blanket access
- Blob soft delete and versioning, so overwritten or deleted objects are recoverable within the retention window
- Locked version-level immutability policies, so not even an account owner can delete records before retention ends
- Customer-managed keys in Key Vault with purge protection for accounts holding personal data under the DPDP Act
- Defender for Storage malware scanning to catch infected uploads before downstream systems open them
Azure Storage Pricing Levers: Access Tiers, Lifecycle Rules, Reserved Capacity and Transactions
Azure Storage bills capacity per GB-month by tier and redundancy, plus read, write and list transactions, data retrieval for cool, cold and archive, early-deletion charges, and egress. Managed Disks bill provisioned size, with Premium SSD v2 and Ultra adding provisioned IOPS and throughput. Archive is the cheapest to keep and most expensive to read, so retrieval patterns decide the real cost.
- Lifecycle rules aligned to 30/90/180-day minimums to avoid early-deletion charges
- Azure Storage reserved capacity for predictable hot or cool volumes over 100 TB
- Bundling small files into larger objects before archiving, to cut per-blob transaction and metadata overhead
- LRS for reproducible proxies and scratch data; GZRS only for unrecoverable records
- Right-sizing Premium SSD v2 IOPS monthly instead of buying larger disks for performance
Azure Blob cool vs cold vs archive tier: which one should hold my old data?
Choose on four criteria. Read latency: cool and cold are online with millisecond access; archive is offline and must be rehydrated, taking up to 15 hours at standard priority. Read frequency: cool suits data read monthly, cold data read a few times a year, archive data read once in several years or never. Minimum duration: 30 days for cool, 90 for cold, 180 for archive, with prorated charges for earlier deletion or tier change. Object size: archive favours large objects, because per-object transaction charges dominate millions of small files. In practice, NTSPL puts news clips older than a year on cold for instant producer search and raw rushes on archive, while an insurer's policy documents sit on cool for the first years and cold thereafter.
Key facts about storage on Microsoft Azure
Storage on Microsoft Azure in Practice
3 storage scenarios from Broadcast media, Higher education & research, Life insurance: the starting position, the services chosen, the architecture, the rollout and the measured outcome.
News channel moves 1.4 PB of footage from LTO tape to tiered Blob Storage
University gives 40 research labs governed, per-lab storage with 10-year retention
Life insurer locks 38 million policy documents in WORM storage with 2 s claim retrieval
Audit firm moves 22 Windows servers to Azure and serves 180 staff via Virtual Desktop
Electronics maker scales PCB traceability to 22 TB on Azure SQL Hyperscale
Storage on Microsoft Azure: Frequently Asked Questions
How is Azure Blob Storage billed?
Blob Storage is billed on stored GB per month by tier and redundancy, plus per-operation transaction charges, data retrieval charges on cool, cold and archive, early-deletion charges if data leaves a tier before its minimum duration, and outbound data transfer. Lifecycle tier changes count as write operations. NTSPL models all of these in INR from a blob inventory report so the estimate reflects actual object counts, not just terabytes.
How long does it take to get a file back from the archive tier?
Standard-priority rehydration from archive can take up to 15 hours. High-priority rehydration may complete in under an hour for objects smaller than 10 GB, at a higher cost. You can rehydrate by changing the tier or by copying the blob to an online tier. NTSPL builds a self-service request flow so users know retrieval is asynchronous and pick priority based on urgency.
How do we move hundreds of terabytes from tape or NAS to Azure?
For under roughly 50 TB on a good link, AzCopy or Azure Storage Mover over the network is usually fine. Above that, Azure Data Box devices ship to your site, are filled locally and returned to the Azure data centre for upload. NTSPL indexes data before transfer and writes it directly into the target tier and prefix structure so lifecycle rules apply from day one.
Can data in Azure Storage stay within India?
Yes. Choose Central India, South India or West India for the storage account and LRS or ZRS to keep all copies in one Indian region, or GRS and GZRS to replicate between Central India and its pair, South India. This supports DPDP Act commitments and IRDAI or RBI expectations on where records reside. NTSPL also restricts replication and copy targets through Azure Policy.
Does immutable storage meet regulatory WORM requirements?
Azure immutable Blob Storage has been assessed by an independent firm against SEC Rule 17a-4(f), CFTC and FINRA record-keeping requirements, which Indian regulated entities often use as a benchmark. Once a time-based retention policy is locked, the retention interval can be extended but not shortened, and blobs cannot be deleted or modified. Your compliance team still defines the retention periods.
Should we replace our Windows file servers with Azure Files or keep them with File Sync?
Keep a small Windows Server cache with Azure File Sync where branches have limited bandwidth or applications need local SMB speed; cloud tiering keeps hot files local and the rest in Azure. Retire file servers entirely where users connect over ExpressRoute, VPN or Azure Virtual Desktop with low latency to the region. Many organizations run both models across different sites.