Case Study · Healthcare · Azure

Healthcare Platform Cuts Azure Spend 29% Without Touching Compliance

Engagement length 90 days · Performance fee, no savings no fee · Independent and vendor neutral
29%
Monthly bill reduction
$177k
Saved per month
90
Days to realized savings
$2.1M
Annualized saving

The situation

A healthcare technology company ran its patient-facing platform and analytics estate entirely on Microsoft Azure. Growth had been fast, the bill had grown faster, and the monthly Azure invoice had reached about 612,000 dollars. The finance team could see the total climbing but could not see which product lines or environments were driving it, and every cost conversation stalled on the same question: what can we safely cut in a regulated environment without putting patient data or uptime at risk.

That constraint shaped everything. Anything we proposed had to respect HIPAA controls, data residency rules, and the audit trail. We sit on the customer's side of the table against the cloud bill, and in healthcare that means cutting waste and rate, never coverage or compliance. We engaged on the performance fee model: no savings, no fee, so the firm carried the risk and was paid from realized savings only.

What we did: See, Cut, Lock, Run

We ran the engagement on our standard four step method. The first two weeks were See: tagging every resource and normalizing the billing data so every dollar had an owner, an environment, and a product line. That alone reset the conversation, because for the first time the team could compare production against the sprawl of non-production environments that had quietly become the larger line item.

Rightsize first, before any commitment

We rightsized over-provisioned virtual machines and AKS node pools against actual utilization rather than peak-day guesses, and consolidated under-used database tiers. Rightsizing and scheduling came first so that later commitments were bought on a clean, lower baseline rather than locking in waste.

Azure Hybrid Benefit on existing licenses

The company held Windows Server and SQL Server licenses with active Software Assurance that were not being applied in Azure. Switching eligible VMs and SQL workloads to Azure Hybrid Benefit removed the second license charge from a large share of the fleet, a pure paperwork win with no architectural change.

Schedule and clear non-production

Development, test, and staging environments were running around the clock. We applied auto-shutdown schedules and Dev/Test pricing where eligible, and removed idle and orphaned resources: unattached managed disks, stale snapshots, and old Log Analytics retention that no one needed.

Commit last, on the clean baseline

Only after the baseline dropped did we layer in a savings plan for compute and reserved capacity for the steady, predictable production workloads. Buying commitments last meant the discount applied to the right-sized fleet, not the bloated one.

Lock and Run so it stays cut

We set budgets and anomaly alerts per product line, added Azure Policy guardrails so untagged or oversized resources could not ship, and handed over a monthly operating rhythm. Savings in a regulated estate erode quietly; the governance layer is what keeps the unit cost falling after the engagement ends.

Before and after

MeasureBeforeAfter
Monthly Azure bill~$612,000~$435,000
Reduction·29%
Annualized saving·~$2.1M
Time to realized savings·90 days
Compliance postureHIPAA, data residencyUnchanged

The largest single contributors were rightsizing and Azure Hybrid Benefit, followed by non-production scheduling. Commitments closed the remaining gap. No production workload was downgraded and no compliance control was relaxed to get there.

"For the first time we could see the bill by product line, and the savings did not cost us a single control. The no savings, no fee model meant the incentives were aligned from day one."

This engagement is part of how we approach Azure cost optimization across regulated industries. For the full playbook behind it, see The Complete Guide to Azure Cost Optimization and download the Azure Cost Optimization Field Guide.

Figures in this case study are representative of a real engagement and have been anonymized and rounded to protect the client. Before and after amounts illustrate the typical shape and scale of an Azure optimization in a regulated environment.

Want this result on your Azure bill

We map the estate, find the rightsizing, licensing, and commitment wins, and lock them in place. No savings, no fee.

Get a cost audit