Azure HIPAA Cost in 2026
Microsoft's HIPAA BAA is a default term of the Data Protection Addendum rather than something you buy, and no Azure meter carries a HIPAA rate. What you pay is Defender, Sentinel, Key Vault and Log Analytics at their ordinary published rates. This page gives you those rates with the dimension each is actually charged on, which for most of Defender for Cloud is per node per hour and not the per-month figure you have probably seen quoted.
The structural point
There is no HIPAA SKU on Azure. Microsoft states the BAA is available through the Data Protection Addendum by default to any customer who is a covered entity or business associate, so there is nothing to negotiate and no fee attached to it. Your HIPAA-attributable Azure spend is the security services you choose to switch on, metered the way Microsoft meters them, plus the engineering time to configure and evidence them. Microsoft publishes no figure for that engineering time and neither do we.
The Microsoft BAA mechanics
Microsoft's HIPAA and HITECH Act offering page states that the BAA "is available through the Microsoft Online Services Data Protection Addendum by default to all customers who are covered entities or business associates under HIPAA", checked July 2026. Two things follow that are worth internalising. There is no acceptance workflow to complete, unlike AWS Artifact or the Google Cloud console: if you are on the DPA and you are a covered entity or business associate, the BAA already applies. And Microsoft will not sign your paper, stating that it cannot use a customer's Business Associate Agreement.
Microsoft attaches no price to the BAA anywhere on that page. It also never says the BAA is free. Those are different statements and this page keeps them apart: what is verifiable is that the BAA is a default contract term with no fee published against it.
This is an informational cost reference, not legal or compliance advice. Consult a cloud-compliance attorney or a HIPAA-qualified compliance professional before architecting a HIPAA workload on Azure.
The published meters
Each row below is a separate meter on its own dimension. Microsoft publishes no combined security total for Azure and this page does not build one into a headline.
| Meter | Published rate | Charged per |
|---|---|---|
| Defender for Servers Plan 1 | $0.00672 | per node per hour |
| Defender for Servers Plan 2 | $0.02 | per node per hour |
| Defender CSPM | $0.007 | per node per hour |
| Defender for Storage | $0.0134 | per storage account per hour |
| Defender for SQL, servers on machines | $15 | per node per month |
| Microsoft Sentinel, pay-as-you-go | $4.30 | per GB analysed |
| Sentinel Basic Logs | $1.00 | per GB |
| Key Vault, secrets and software keys | $0.03 | per 10,000 transactions |
| Key Vault, HSM-protected RSA 2048 | $1 | per key per month |
| Log Analytics, Analytics Logs | $2.30 | per GB, first 5 GB per month free |
| Log Analytics retention | $0.10 | per GB per month beyond the free period |
East US, checked July 2026, read from Microsoft's own Azure Retail Prices API, which returns the actual billing meters. Commitment tiers and Defender Commit Units reduce these rates and are published separately; Microsoft advertises up to 22 percent off pay-as-you-go on Defender pre-purchase and up to 52 percent on Sentinel commitments.
Why you will not find these numbers on the pricing page
Azure's pricing pages render every dollar figure client-side. Fetch the Defender for Cloud pricing page and the served HTML contains placeholder dashes where the prices go: "$- /Vault/month", "$- /Subscription/month". The unit wording is server-rendered and citable. The numbers are not.
This is why the "$5 per server per month" and "$15 per server per month" Defender for Servers figures circulate so widely and cite nothing. We could not verify either from a Microsoft surface. The Learn documentation on selecting a Defender for Servers plan carries no dollar figures at all. What Microsoft's API does return is $0.00672 and $0.02 per node per hour. Multiply by a 730-hour month and you land near $4.90 and $14.60, which is close to the folklore but is our arithmetic on an hourly meter, not a Microsoft-published monthly price. We report the meter.
Microsoft's Sentinel pricing page is the starker case: it publishes no rates at all, only a percentage saving claim and a link to sales. A per-GB figure exists and is real, but you have to query the API to see it.
What the stack costs at one worked volume
Our arithmetic, not a vendor price
Microsoft publishes the per-unit meters. Microsoft does not publish this total, and does not publish a monthly figure for the hourly meters at all: the 730-hour month is ours, as are the volumes. Substitute your own.
| Assumed monthly volume | Against the published meter | Line |
|---|---|---|
| 10 VMs on Defender for Servers Plan 2 | 10 x 730 h x $0.02 | $146.00 |
| 10 nodes on Defender CSPM | 10 x 730 h x $0.007 | $51.10 |
| 50 GB per month into Sentinel | 50 x $4.30 | $215.00 |
| 5 HSM-protected RSA 2048 keys | 5 x $1 | $5.00 |
| 200,000 Key Vault transactions | 20 x $0.03 | $0.60 |
| Our total for these assumed volumes | $417.70 | |
As on AWS, the total is ours and applies to nobody. The shape is the transferable part: Sentinel ingestion and Defender node-hours are the whole bill, and key management is a rounding error. The two levers are how many nodes you protect and how many GB you send to Sentinel. Before you model anything else, meter your log volume, and check whether your workspace is still inside the 31-day, 10 GB per day free window that Microsoft grants new workspaces, because that window is why Sentinel bills look fine in month one and different in month two.
Common Azure HIPAA budget mistakes
Letting Defender auto-enrol the estate. Microsoft states that "when you enable Microsoft Defender for Cloud, we automatically enroll and start protecting all your resources unless you explicitly decide to opt-out", and that the first 30 days are free. Both facts together produce the classic Azure surprise: a free month across every subscription, then a bill for node-hours nobody scoped.
Reading the hourly meters as monthly. $0.02 per node per hour is not $0.02 per node per month. On a 100-VM estate that mistake is two orders of magnitude.
Assuming the free Sentinel data sources cover you. Azure Activity, Sentinel Health, Office 365 audit logs and Defender alerts are free. Microsoft warns that the raw underlying logs for several Defender data types are paid, so the alert is free and the evidence behind it may not be.
Forgetting retention. Sentinel retains ingested data at no charge for the first 90 days. After that, Log Analytics retention is $0.10 per GB per month. HIPAA sets no single retention period for audit logs, but 45 CFR 164.316(b)(2)(i) requires six-year retention of the documentation the rule requires, and where your own policy commits you to a long log-retention window, that window has a published per-GB price.
Azure HIPAA cost FAQ
Does Microsoft charge for the HIPAA BAA?
What does Microsoft Defender for Cloud cost?
What does Microsoft Sentinel cost?
What does Azure Key Vault cost?
Is there a HIPAA surcharge on Azure?
Why does this page quote an API rather than the pricing page?
Does the BAA make my Azure workload HIPAA compliant?
Related cost guides
AWS HIPAA Cost
KMS, CloudTrail, Config, GuardDuty rates
GCP HIPAA Cost
The one cloud that states its HIPAA pricing policy
Digital Health Startup Cost
Seed to Series A HIPAA pricing
Business Associate Agreements
BAA scope, cost, and red flags
HIPAA Email Cost
Microsoft 365 and Google Workspace
2026 Security Rule Changes
Cloud-architecture impact