
The SFTP fee also isn't the whole bill. Capacity, transactions, redundancy, data transfer, monitoring, and automation all add to it.
This article covers the current hourly rate, formulas for always-on and scheduled setups, the other Azure charges that apply, and practical ways to avoid surprise costs. All prices below are USD retail, checked on 2026-11-18. Treat them as estimates, not quotes.
Key Takeaways
- The SFTP endpoint costs $0.30 per enabled storage account-hour in the East US example.
- You pay for enabled hours, not transferred gigabytes.
- Capacity, tier, transactions, redundancy, retrieval, and egress are billed separately.
- Short, predictable transfer windows keep costs lowest.
- Match the setup to workload needs, not just price.
How Much Does Azure Blob Storage SFTP Cost? (Pricing Overview)
There's no single all-in monthly price. The endpoint charge depends on how long SFTP stays enabled, and the underlying storage account generates its own usage on top.
Current hourly SFTP endpoint price
The Azure Blob pricing page lists $0.30 per hour under "SFTP enabled for storage account (per hour)." That rate is shown with hierarchical namespace, East US, LRS, and USD selected.
Key billing details:
- The unit is the storage account, not users, connections, or gigabytes.
- Idle time is billed whenever SFTP is enabled.
- Microsoft doesn't publish partial-hour proration, rounding, or minimum enabled intervals.
- Only one SFTP rate is shown. No regional or account-type rate matrix is published, so confirm your region in the pricing calculator.
- If your billing currency isn't USD, Azure converts through its monthly exchange-rate process, and your agreement can change the actual price.
Usage-based pricing scenarios
The 730-hour month below is a common calculator convention, not an SFTP billing rule. These are illustrative calculations at $0.30/hour.
Always-on: hourly rate × hours enabled → 730 hours × $0.30 = $219 per month for one account.
Scheduled: hourly rate × daily active hours × operating days → 2 hours × 22 days × $0.30 = $13.20 per month.

Build the window with room for transfers, retries, and operational checks. A schedule that's too tight causes failed jobs.
Each storage account carries its own endpoint charge. Production, test, and disaster-recovery accounts multiply the cost, so estimate each one separately.
What the hourly fee includes and excludes
The hourly line covers the enabled SFTP capability. Storage capacity, transactions, data transfer, redundancy, and retrieval are separate. Date-stamp any pricing you quote internally, because Azure rates change.
Azure Blob Storage SFTP Cost Factors and Breakdown
Total cost mixes recurring service charges, usage-based charges, one-time setup effort, and ongoing operations.
SFTP endpoint availability (recurring)
The direct charge applies for every hour SFTP is enabled. Always-on accounts pay for idle time. Scheduled accounts pay only for the windows you enable.
Blob capacity, access tier, and retention (recurring)
Prices below are for East US, LRS, hierarchical namespace, first 50 TB per month.
| Tier | Capacity per GB-month | Retrieval per GB | Minimum retention |
|---|---|---|---|
| Hot | $0.021 | Free | None |
| Cool | $0.015 | $0.01 | 30 days |
| Cold | $0.0036 | $0.03 | 90 days |
| Archive | $0.00099 | $0.02 standard, $0.10 high priority | 180 days |

Microsoft's access tier documentation notes that early deletion, overwrite, or tier moves can trigger retention charges. Archive data needs rehydration of up to 15 hours before reading.
Transactions and data transfer (recurring, usage-based)
- Every SFTP command converts into a Read, Write, or Other transaction on the account.
- Writes and other operations are priced per 10,000; iterative writes per 100; deletes are free.
- Inbound data and same-region transfers are free.
- Internet egress includes 100 GB free monthly, then about $0.087/GB for the next 10 TB in North America.
- Inter-region transfer in North America runs $0.02/GB.

Redundancy and account configuration (recurring)
Standard general-purpose v2 accounts support LRS, ZRS, GRS, RA-GRS, GZRS, and RA-GZRS. Premium block blob accounts support LRS or ZRS.
- Geo-replication adds $0.02/GB in transfer
- Archive supports only LRS, GRS, and RA-GRS
- Disable SFTP before changing redundancy, then re-enable it
Setup and integration (mostly one-time)
- Hierarchical namespace is required, on a general-purpose v2 or premium block blob account.
- Local users authenticate with a password or SSH key, not both. Azure generates passwords and can't show them again.
- Limits: 50,000 local users, 10 keys per user, 100 containers per user.
- Budget engineering time for client integration, testing, and any scheduled enable/disable automation.
Security, monitoring, and operations (recurring)
Firewalls, virtual networks, and private endpoints are supported. Port 22 stays open at the platform level even when SFTP is disabled; unconfigured access just gets disconnected.
Diagnostic logs aren't free: Log Analytics charges for ingestion and retention. Add staff time for credential rotation and incident response.
Cost allocation and governance (recurring)
Use separate subscriptions, resource groups, or tags so the SFTP endpoint charge stays distinct from general Blob spend. Tag inheritance applies subscription and resource-group tags to child usage records within 24 hours.
Low-Cost vs High-Cost Azure Blob SFTP: What's the Difference?
"Low cost" shouldn't mean weak reliability or security. The real comparison is a scheduled setup versus an always-on one.
Performance, availability, and operational fit
- Lower cost: SFTP is enabled only during predictable windows, with slack for retries and maintenance.
- Higher cost: Always-on access suits unpredictable file arrivals but bills every hour and needs stronger availability controls.
Security, maintenance, and administration
- Lower cost: Automation cuts idle exposure and charges. You must still monitor schedules, time zones, failures, and emergency access paths.
- Higher cost: Continuous exposure simplifies connectivity but demands disciplined authentication, network restrictions, logging, and credential management.
Microsoft gives no guarantee about in-flight sessions when you toggle. The command itself is simple: az storage account update --enable-sftp false in the Azure CLI, or -EnableSftp in PowerShell.
Long-term value and best fit
Scheduled SFTP fits nightly batch jobs and predictable partner drops. Always-on access can be justified for business-critical or partner-driven flows where files arrive at unpredictable times.
At $219 versus $13.20 per month, the gap is real, but weigh it against automation and support effort before deciding.
How to Estimate the Right Azure Blob SFTP Budget
Base the budget on workload fit and total cost of ownership, not the hourly rate alone.
- Define the workload. Count accounts, environments, transfer windows, operating days, file volume, retries, and any off-window access needs.
- Inventory every billable component. Estimate endpoint hours, stored data, tier, redundancy, transactions, retrieval, egress, monitoring, automation, and implementation.
- Apply a transparent formula. Use the hourly rate for daily, monthly, and annual scenarios, then add Blob and networking costs separately.
- Compare scenarios. Model always-on, scheduled, and hybrid, with buffers for failed transfers, time zones, seasonal peaks, and disaster-recovery access.
- Validate with real data. Use the Azure pricing calculator, Cost Management budgets, and actual billing to refine assumptions.

When you validate, treat budget alerts as a warning layer only. They do not stop spending, cost data often arrives 8 to 24 hours late, and budgets evaluate every 24 hours.
What most people miss
- Enabled endpoints keep billing even while idle.
- Outbound downloads to on-premises clients incur bandwidth fees.
- Colder tiers can cost more once retrieval and early deletion are counted.
- Geo-redundant accounts generate replication transfer charges.
- Diagnostic logging adds ingestion and retention costs.
- Schedules must handle failed jobs, clock changes, and re-enable lag.
Block storage is a separate bill. If you also run Azure managed disks, Lucidity provides visibility and autonomous optimization for cloud block storage across AWS, Azure, and Google Cloud. It doesn't change the Blob SFTP endpoint fee.
Conclusion
Blob SFTP pricing is primarily an hourly enabled-service charge, but the final bill also reflects more than that single line item:
- Storage and redundancy
- Transactions and operations
- Networking and security. Start with the official hourly rate and a realistic count of active hours per endpoint.
These controls help balance availability against predictable spend:
- Scheduled activation for the hours you need
- Budgets and alerts on the SFTP charge
- Suitable storage settings and clear cost tagging
Frequently Asked Questions
How much does Azure Blob storage cost?
It depends on capacity, access tier, redundancy, transactions, retrieval, and data transfer. Use the official Azure pricing calculator for a US-specific estimate.
How much does it cost to use SFTP?
SFTP carries a separate endpoint charge, observed at $0.30 per enabled account-hour on 2026-11-18. Underlying Blob Storage usage is billed on top.
Can I use SFTP to access Azure Blob storage?
Yes, if the account meets Microsoft's prerequisites: hierarchical namespace, a supported account type, local users with password or SSH key authentication, and port 22 connectivity.
Is Azure Blob Storage SFTP charged when no files are transferred?
Yes. The hourly charge applies whenever SFTP is enabled, even with no connections. Storage and transaction charges are calculated separately.
How can I reduce Azure Blob Storage SFTP costs?
Enable SFTP only during transfer windows and disable it afterward. Pick tiers with retrieval and retention in mind, limit unnecessary operations, and watch egress.
What other Azure charges apply when using SFTP?
Expect charges for capacity, transactions, tier retrieval, replication, outbound transfer, logging, and any automation you add to schedule the endpoint.