Azure cost optimization for a small business comes down to five habits: right-size or switch off what is idle, commit to reservations or savings plans only for workloads that have proven stable, move old data to cheaper storage tiers, set budgets with alerts, and give every resource a named owner who answers for its cost. The tools for all five are built into Azure, and Microsoft charges nothing to use Cost Management on your subscriptions.
This guide is for an Azure environment that is already running. If you are still deciding whether to move, our Azure migration cost guide separates the one-time project from the monthly bill, and our Azure migration consulting builds that cost model before anything moves. Below are the causes of waste, the settings that fix them and a review checklist. Our cloud services team runs the same review for managed clients.
What does cloud cost optimization mean on Azure?
Cloud cost optimization means paying for the capacity you actually use, at the lowest rate that still meets your performance and recovery needs. On a small business Azure bill, the waste tends to come from a short list:
- Virtual machines sized for a peak that never comes, or left running overnight when nobody uses them.
- Resources nobody owns: unattached disks, old snapshots, public IP addresses and test machines from a finished project.
- Data sitting in the hot storage tier years after anyone last opened it.
- Steady production servers billed at pay-as-you-go rates instead of a one- or three-year commitment.
- Windows Server licenses paid twice: once in the hourly VM rate and again in an agreement you already hold.
- Backup and log retention set to keep everything, forever.
How do you right-size Azure virtual machines?
Start with Azure Advisor's cost recommendations. Advisor recommends shutting a VM down when it was effectively unused over its lookback period, for example when the 95th percentile of its maximum CPU stays under 3 percent and outbound network use under 2 percent. It recommends a smaller or cheaper size when the current load would fit, and burstable B-series sizes for machines with low average CPU and occasional spikes. The default lookback is seven days; change it to 30 days or more in Advisor's configuration so a month-end close or payroll run is included.
Treat the recommendations as leads, not orders. Advisor estimates savings at retail rates and does not account for reservations or savings plans you already hold, so the savings it lists can be higher than what you will see. Check memory and disk use before resizing, and dismiss a recommendation, with a reason, for a machine that exists for disaster recovery or a known seasonal peak.
For machines that only need business hours, such as test servers, use the VM's auto-shutdown setting or a schedule. One billing detail is easy to miss: shutting a VM down from inside Windows leaves it in the Stopped state, which Microsoft still bills as compute. Only a VM in the Stopped (deallocated) state stops compute charges, and its disks and networking keep billing even then.
Reservations or savings plans: which should a small business buy?
Both trade a one- or three-year commitment for a lower rate. Microsoft draws the line like this:
| Reservation | Savings plan | |
|---|---|---|
| What you commit to | A specific VM type or family in a specific region | An hourly spend on eligible compute services, in any region |
| Best for | Workloads that run continuously and will not change size, family or region | Workloads that change shape or move between VM families and regions |
| Savings | The greatest when fully used | Deep, with more flexibility in where the discount applies |
| Main risk | Paying for a size you no longer run | Committing to more hourly spend than you use |
Microsoft's recommended order is to right-size first, because discounts reduce rates, not waste. Then exchange or trade in reservations that no longer fit, buy reservations for stable workloads, and add savings plans sized to the cleaned-up baseline. For a small business that usually means running a new server at pay-as-you-go rates for a billing cycle or two, confirming its size, then reserving only the production machines you expect to run around the clock for the whole term.
How do storage tiers and lifecycle rules cut Azure costs?
Blob storage has four access tiers you can set yourself. Each cooler tier costs less to store data and more to read it:
| Tier | Use it for | Minimum storage period |
|---|---|---|
| Hot | Data in active use | None |
| Cool | Data read occasionally | 30 days |
| Cold | Data rarely read that still needs instant access | 90 days |
| Archive | Data kept for retention, where waiting hours to read it is acceptable | 180 days; the tier is offline, and rehydration can take up to 15 hours |
Moving or deleting a blob before its tier's minimum period triggers a prorated early deletion charge, so tier deliberately. A lifecycle management policy does the work automatically: its rules move blobs to cooler tiers, or delete them, based on creation time, last modified time or last access time. Microsoft charges nothing for the policy itself, only the normal cost of the tier changes it makes, and new rules can take up to 24 hours to start. If you can't predict how often data will be read, Microsoft's smart tier, generally available on zone-redundant storage accounts, moves blobs among hot, cool and cold automatically, with no early deletion or retrieval charges but a monthly monitoring fee for each object over 128 KiB. Review backup retention and old disk snapshots in the same pass.
How do budgets and alerts keep the Azure bill predictable?
Create a budget in Cost Management for each subscription or resource group. A budget resets monthly, quarterly or yearly, and each one supports up to five alert thresholds sent to up to five email addresses, based on actual spend or on Microsoft's forecast. Set at least two: a forecast alert at 90 percent, so you hear about an overrun before the month ends, and an actual-cost alert at 100 percent.
Know the limits. Budgets are evaluated every 24 hours against cost data that can lag by 8 to 24 hours, and an alert does not stop anything: Microsoft states that resources are not affected and consumption is not stopped. If you want an automatic response, attach an action group to the budget. Cost analysis also flags anomalies at subscription scope, and you can subscribe to an anomaly alert for spending that breaks its usual pattern.
Who owns Azure costs?
Every resource needs an owner who can say why it exists. Tags make that visible on the bill: Owner, CostCenter, Environment and Application are enough for most small businesses. Tags appear in Microsoft's usage file and let you group spending by owner or project. Two rules from Microsoft's documentation matter. Resources do not inherit tags from their resource group or subscription, so use Azure Policy to apply and require them; Cost Management's tag inheritance setting can copy those tags into cost data, but not onto the resources. And tags are stored as plain text, so never put sensitive values in one.
Then hold a 30-minute review each month. The cost owner, usually the operations or finance lead, goes through the largest changes with whoever administers Azure. Every line on the bill gets a reason, and anything without one becomes a candidate for deletion.
What goes on an Azure cost review checklist?
Monthly
- Compare actual spend with the budget and with last month, by subscription and by tag.
- Work through Advisor's cost recommendations, acting on each or dismissing it with a reason.
- Find unattached managed disks, unused public IP addresses and snapshots older than your retention rule.
- Confirm test and development VMs are deallocated outside business hours.
- Check reservation and savings plan utilization, and investigate anything well below full use.
- Look at the five largest cost increases and any anomaly alerts, and record the cause.
- Check that new resources carry the required tags.
Quarterly
- Re-run right-sizing with a lookback of 30 days or more.
- Review storage tiers, lifecycle rules, backup retention and log retention against what you actually need.
- Confirm Azure Hybrid Benefit is applied wherever you hold Windows Server core licenses with active Software Assurance or qualifying subscription licenses.
- Decide on new reservations or savings plans for workloads that have stayed steady.
- Adjust budgets for planned changes, such as a new office or application.
How do you validate that the changes saved money?
Record each change with the date, the resource and its cost for the previous full month, then compare a full month afterward. Watch performance as well: after a resize, check that CPU and memory peaks stay comfortably below the new size's limits and that users report no slowdowns. For commitments the test is utilization, because a reservation running well below full use is costing you money. Keep the change log with the monthly review notes, so each review starts from facts.
How does NetSys help with Azure costs?
Cost control is part of how we run cloud infrastructure for managed clients: resource optimization and scaling, cost control and budget planning, performance monitoring and backup design sit with the same team that administers the environment. Every Azure migration we run ends with a first cost review against the estimate. Management is priced per user per month, agreements run month to month, and Azure usage itself is billed by Microsoft.
Book a call with an engineer to walk through your last three Azure invoices and the Advisor recommendations behind them.
Frequently asked questions
What does the Azure cost review checklist cover?
Idle and oversized VMs, orphaned resources, VM schedules, reservation and savings plan use, storage tiers and retention, budgets and anomaly alerts, tags and ownership, and Azure Hybrid Benefit. The monthly items catch drift, and the quarterly items revisit commitments and retention.
Who maintains Azure cost optimization in a small business?
Two people: a cost owner on the business side, often the operations or finance lead, who approves budgets and asks why spending changed, and a technical administrator, in house or at your IT provider, who makes the changes. Each resource also carries a tagged owner who answers for it.
How do we validate the result?
Compare each changed resource's cost for a full month before and after, confirm performance held after any resize, and track reservation and savings plan utilization. Keep a change log so the savings are documented, not assumed.
Does stopping an Azure VM stop the charges?
Only if it is deallocated. A VM shut down from inside the operating system shows as Stopped and is still billed for compute. Check its status: Stopped (deallocated) ends compute charges, while its disks and some networking resources keep billing until you delete them.
Should a small business buy Azure reservations right away?
No. Run new or migrated servers at pay-as-you-go rates for one or two billing cycles, right-size them from real usage, and then commit for the production servers you are sure will run around the clock for the term. Reserving first locks in whatever size you guessed.
Is Azure Cost Management free?
Yes, for Azure subscriptions. Microsoft states there is no charge to use Cost Management and Billing features on your Azure subscriptions, which covers cost analysis, budgets and anomaly detection.
Sources and further reading
- Microsoft Learn: Advisor recommendations for VMs: shutdown, resize and burstable criteria, lookback periods and limitations, checked October 2026.
- Microsoft Learn: VM states and billing: which states are billed for compute.
- Microsoft Learn: decide between a savings plan and a reservation: the comparison and the recommended order.
- Microsoft Learn: blob access tiers: minimum storage periods, early deletion, rehydration and smart tier.
- Microsoft Learn: create and manage budgets: thresholds, evaluation timing and action groups.
- Microsoft Learn: use tags to organize Azure resources: inheritance, billing data and plain-text storage.
Discuss cloud services for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.