Azure Blob Storage SFTP Pricing: Hourly Charges Explained Azure Blob Storage SFTP gives teams a familiar, secure protocol for moving files into and out of Blob Storage. The catch is the endpoint itself. It carries an hourly charge that sits apart from ordinary Blob storage costs, and it keeps running whether anyone connects or not.

Your final bill depends on the US region, the number of storage accounts, how many hours SFTP stays enabled, stored capacity, transactions, data transfer, and any automation that switches the endpoint on and off.

This guide covers the pricing formula, each cost component, a budgeting method, and the trade-offs between scheduled and always-on setups.

Key Takeaways

  • Azure bills the SFTP endpoint per enabled hour, so check Microsoft's current rate before budgeting.
  • Endpoint cost equals the hourly rate times enabled hours, per storage account, plus Blob usage charges.
  • Scheduled SFTP cuts endpoint hours; always-on suits partners who need uninterrupted access.
  • VM costs apply only if you run a self-managed SFTP server.

How Much Does Azure Blob Storage SFTP Cost? (Pricing Overview)

There is no single universal total for Azure Blob Storage SFTP. The endpoint rate is fixed per hour, but your bill still depends on how many hours you keep it enabled and on related Blob usage.

Current hourly charge

On Microsoft's Blob pricing page, SFTP is listed at $0.30 per enabled storage-account-hour. The same rate applies in East US, East US 2, West US 2, and Central US (hierarchical namespace, LRS).

Rates as of November 18, 2026, in USD. Treat this as a snapshot. Microsoft doesn't list separate standard and premium endpoint prices, but actual pricing can vary with your agreement, purchase date, and exchange rate. Confirm the rate for your region before you commit.

Cost calculation formula

SFTP endpoint charge = hourly rate × hours enabled × number of storage accounts

For annual planning, multiply the monthly result by 12. Here is a hypothetical illustration at $0.30 per hour, not a guaranteed invoice:

Schedule Hours/month Monthly endpoint cost
2 hours daily (30 days) 60 $18
8 hours on weekdays (about 22 days) 176 $52.80
Always on (720 hours) 720 $216
Always on, 3 accounts 2,160 $648

Azure SFTP monthly endpoint cost by enabled-hours schedule

These figures cover only the endpoint. Storage, transactions, and transfer come on top.

Typical Cost Profiles

Scheduled or on-demand SFTP

You pay the endpoint fee only for hours when SFTP is enabled, plus normal Blob storage and transfer charges. For a nightly batch, enable the endpoint shortly before the job and disable it afterward.

Best for: workloads with defined transfer windows that tolerate SFTP being unavailable otherwise.

Part-time recurring SFTP

You pay the endpoint fee for a recurring block of monthly hours, plus Blob capacity, transactions, and any scheduling or monitoring service that toggles the endpoint.

Best for: processes that need access during business hours but not around the clock.

Always-on or multi-account SFTP

Every account pays for every enabled hour, on top of storage, operations, data transfer, and redundancy.

Best for: partners or applications that need continuous availability, several storage accounts, or unpredictable connection times.

What the hourly charge covers

The hourly fee covers the enabled SFTP capability. These items are billed separately:

  • Capacity and access tiers
  • Transactions and retrieval
  • Outbound transfer and redundancy
  • Monitoring and automation

Microsoft states there is no separate per-GB fee for data moved over SFTP, though underlying storage, transaction, and networking charges still apply.

Key Factors That Affect Azure Blob Storage SFTP Pricing

Pricing follows technical configuration, endpoint uptime, and the surrounding transfer workload. Stored data volume alone doesn't determine it.

Region and billing location

Compare the SFTP rate for the specific US region you plan to use. Currency conversion and agreement terms can change the effective charge. The storage account's region matters, not where your users sit, and one region's rate shouldn't stand in for all of Azure.

Hours enabled and scheduling model

Enabled hours are the main driver, including idle ones. Microsoft documents the charge as applying whenever SFTP is enabled, whether or not anyone is connected.

Microsoft's pricing table doesn't state a partial-hour or proration rule, so verify billing behavior against your own invoices.

Shorter windows lower the bill but demand reliable automation, alerting, and failure handling.

Number of storage accounts

Model the endpoint per account, then multiply across dev, test, production, regional, and partner-specific accounts. A quick worksheet:

  • Number of SFTP-enabled accounts
  • Enabled hours per account
  • Regional rate for each account
  • Account-specific exceptions

Storage account configuration and eligibility

Native SFTP requires hierarchical namespace. Supported accounts include Standard GPv2 (LRS, ZRS, GRS/RA-GRS, GZRS/RA-GZRS) and Premium BlockBlobStorage (LRS, ZRS).

Limits to know:

  • SFTP only; no FTP or FTPS
  • Maximum upload of 500 GB through the endpoint
  • Blob versioning, change feed, object replication, and point-in-time restore are unsupported on hierarchical namespace accounts
  • Disable SFTP before changing redundancy or replication settings

Redundancy, access tier, and soft delete don't change the SFTP line directly, but they shape the surrounding storage bill.

Workload, transfer volume, and commercial terms

SFTP hourly fees sit on top of normal Blob Storage usage charges. Activity that commonly increases the bill includes:

  • Larger files and higher file counts
  • Reads, writes, and directory listings
  • Retrievals and internet egress
  • Geo-replication traffic

Commercial terms need separate checks too:

  • Reserved capacity covers storage capacity only, not the SFTP account-hour meter
  • Savings plans exclude storage charges
  • Free-account credits may not cover the SFTP meter; confirm eligibility in your offer terms
  • Enterprise Agreement customers can download their price sheet to see their actual rates

Azure SFTP pricing factors from configuration to commercial terms

Cost Breakdown of Azure Blob Storage SFTP

The endpoint fee is one line in a full file-transfer estimate. Here are the others.

SFTP endpoint charge (recurring)

The current regional hourly rate applies to every enabled hour on every account, idle time included.

Blob capacity and access-tier charges (recurring)

Cost depends on GB or TB stored, access tier, redundancy, and performance tier.

  • Cool, cold, and archive tiers carry minimum retention of 30, 90, and 180 days
  • Early deletion or overwrite can trigger an early-deletion charge
  • Premium block blob accounts can't be tiered

Storage transactions (recurring)

Every SFTP command and API call converts into a Read, Write, or Other transaction, priced per 10,000 operations. Many small files or chatty clients make these charges material.

Data transfer, retrieval, and replication (usage-based)

  • Inbound transfer is free
  • Internet egress is billed, with the first 100 GB per month free
  • Cross-region transfers and geo-replication bandwidth are charged
  • Cool, cold, and archive reads carry per-GB retrieval fees

Automation, monitoring, and administration (recurring or usage-based)

Scheduling usually means Azure Automation, Functions, or Logic Apps. Automation jobs are billed by monthly runtime minutes above a free allotment.

Set-AzStorageAccount -EnableSftp $true flips the switch, and Automation schedules can run it hourly, daily, weekly, or monthly. Add alerts so the endpoint doesn't stay enabled by accident or stay off during a required transfer. Count engineering time too.

Azure SFTP endpoint automation workflow for scheduled transfers

Low-Cost vs High-Cost Azure Blob Storage SFTP: What's the Difference?

A higher hourly bill doesn't buy better performance. The trade-off is continuous availability against operational complexity and total workload cost.

Service availability and workload fit

  • Lower cost: a scheduled endpoint matched to predictable windows, where partners can't connect outside them.
  • Higher cost: an always-on endpoint for unpredictable connection times or processes that can't wait for activation.

Security exposure and maintenance

A scheduled endpoint limits internet-facing exposure time, but it needs tested automation, credential controls, network restrictions, monitoring, and a recovery path. One quirk: Microsoft notes port 22 can remain open at the platform level even when the account's SFTP option is disabled.

Always-on SFTP removes scheduling complexity but stays exposed and billable during quiet periods. Either way, follow Microsoft's guidance:

  • Restrict access with a firewall, virtual network, or private endpoint
  • Grant least-privilege container permissions, using ACLs for finer control
  • Store generated passwords safely, since they can't be retrieved later

Long-term value

Compare avoided endpoint hours with the cost of automation and incident handling. At $0.30 per hour, switching one account from always-on (720 hours) to 60 hours a month saves $198 monthly.

If automation, monitoring, and engineering upkeep cost more than that, always-on wins. For one account, the savings are modest. Across a dozen accounts, they add up fast.

How to Estimate the Right Budget for Azure Blob Storage SFTP

  1. Gather inputs: account names, regions, enabled hours, file volume, average file size, request activity, access tiers, redundancy, egress, and retrieval needs.
  2. Build two scenarios: scheduled and always-on, both using the current Microsoft rate. Add separate estimates for storage, transactions, transfer, monitoring, and support.
  3. Validate: run the numbers through the Azure pricing calculator, then compare against a recent invoice or Cost Management export.

Three-step Azure Blob Storage SFTP budgeting process

What Most People Miss About Azure Blob Storage SFTP Cost

  • The hourly fee isn't the whole bill. Keep endpoint, capacity, transaction, retrieval, egress, and replication meters separate.
  • Native SFTP needs no VM. A VM, its OS, disks, patching, and networking become costs only when you run a self-managed SFTP server or supporting automation on one.
  • Block storage sits beside Blob. Teams often run Azure managed disks with Blob workloads; Lucidity optimizes that block storage across AWS, Azure, and Google Cloud by up to 70% and does not replace native Blob SFTP or the endpoint hourly charge.

Conclusion

Azure Blob Storage SFTP pricing is mainly an enabled-hours calculation. A complete budget also reflects:

  • Region and account count
  • Capacity and transactions
  • Data transfer and operational tooling

The right choice balances availability, security exposure, reliability, and engineering effort against long-term cost. Recheck Microsoft's current pricing before you buy or publish a budget.

Frequently Asked Questions

How much does Azure charge for storage?

Blob capacity is billed separately from the SFTP endpoint fee. The rate varies by access tier, redundancy, region, and usage, so check Microsoft's current Blob pricing page for your configuration.

How much does it cost to use SFTP in Azure?

Native Blob SFTP costs $0.30 per hour in US regions for every hour it's enabled. Storage, transactions, transfer, and other charges are billed separately.

How much does it cost per hour to run an Azure VM?

VM pricing depends on SKU, region, operating system, disks, and runtime. Native Blob SFTP doesn't need a VM, but one adds cost if you host a self-managed SFTP server.

Is Azure free for 1 month?

New customers get a $200 credit within 30 days, plus free-tier services. Microsoft doesn't state an SFTP free-hour allowance, so confirm the offer terms before assuming SFTP is covered.

Is Azure Blob Storage SFTP charged when no files are transferred?

Yes. The hourly endpoint charge applies whenever SFTP is enabled, even when idle. Transactions and data transfer are usage-based and billed separately.

How can I reduce Azure Blob Storage SFTP costs?

Enable SFTP only during transfer windows, trim unneeded accounts, and watch related Blob meters. Test your automation so savings don't cause failed transfers or security gaps.