Azure FinOps: How Philippine Businesses Stop Overpaying for Cloud in 2026
The three most common Azure cost problems for Philippine businesses are not pricing model complexity — they are predictable and fixable: over-provisioned virtual machines running at 5–15% CPU utilisation, development environments left running on weekends, and storage that accumulates indefinitely because no one set a lifecycle policy.
FinOps is the organisational discipline of applying financial accountability to cloud spending. For Philippine SMEs and mid-market organisations, the practical starting point is Azure Cost Management — Microsoft's built-in tool that requires no additional spend to use.
Azure Cost Management: The Starting Point
Admin portal path: portal.azure.com → Cost Management + Billing → Cost Management
Cost Analysis
The Cost Analysis view shows accumulated spend over time, broken down by service, resource group, location, or tag. For Philippine Azure tenants, the first action is always:
- Set the date range to the current month
- Group by Service name — identifies which services are driving cost
- Group by Resource — identifies which specific resources are most expensive
- Group by Resource group — shows which application or team is spending most
What to look for immediately:
- Virtual Machines in the top 3 services (always) — check utilisation
- Storage Accounts with unexpectedly high cost — check blob lifecycle policies
- Bandwidth/data transfer charges — often indicates misconfigured egress
- Any service you did not intentionally provision — investigate immediately
Budget Alerts
Every Azure subscription used by a Philippine business should have a budget alert configured before the next billing cycle.
Admin portal path: Cost Management → Budgets → Add
Set monthly budget at 110% of expected spend. Configure alerts at 80%, 90%, and 100% — emailed to the subscription owner and billing contact. A Philippine IT team that learns about overspend from the monthly invoice is always one month behind.
Cost Alerts for Anomalies
Admin portal path: Cost Management → Cost alerts → Add
Anomaly alerts use ML to detect spend patterns that deviate from historical baseline. A VM left running by mistake or a runaway storage write job triggers an anomaly alert within 24 hours — far faster than the end-of-month invoice discovery.
The Biggest Savings: Right-Sizing Virtual Machines
Philippine Azure deployments typically provision VMs at the size requested by the application team ("we need 8 cores and 32GB RAM") without validating actual utilisation. The result: most VMs run at 5–20% CPU and 30–50% memory utilisation.
Using Azure Advisor for Right-Sizing
Admin portal path: portal.azure.com → Advisor → Cost
Azure Advisor analyses VM utilisation over 7–14 days and recommends specific right-sizing changes. Each recommendation shows:
- Current VM size and monthly cost
- Recommended VM size and monthly cost
- CPU/memory utilisation percentages
- Estimated monthly savings
Example: A D4s_v5 (4 vCPU, 16GB RAM) running a Philippine SME ERP at 8% average CPU can be downsized to B2ms (2 vCPU, 8GB RAM) — saving approximately USD $60–80/month per VM.
Action: Review Advisor cost recommendations monthly. Implement all recommendations with >20% savings that Advisor rates as high confidence (90%+ utilisation data). For each recommendation, test the downsized VM in staging before applying to production.
Development and Test VM Scheduling
Philippine office hours are 8AM–6PM, Monday–Friday. Development VMs running 24/7 waste 70 hours/week of compute cost during nights, weekends, and Philippine holidays.
Implementation: Azure Automation → Schedules → create Start (7:45AM weekdays) and Stop (6:30PM weekdays) runbooks for all dev/test VMs tagged Environment: Development.
Savings: A D4s_v5 running 24/7 costs ~USD $140/month. Running 55 hours/week (8AM–6PM weekdays) costs ~USD $43/month — a 69% reduction.
Reserved Instances: The Single Largest Discount
For any VM running production workloads that will exist for 1–3 years, Reserved Instances (RIs) are the most impactful cost reduction available.
How it works: Commit to using a specific VM size in a specific region for 1 or 3 years, paid upfront or monthly. In exchange, Microsoft reduces the compute rate by:
- 1-year RI: approximately 36–40% discount vs pay-as-you-go
- 3-year RI: approximately 60–63% discount vs pay-as-you-go
Philippine example: D4s_v5 in Southeast Asia (Singapore region):
- Pay-as-you-go: ~USD $140/month
- 1-year RI (monthly payments): ~USD $85/month — saving USD $55/month = USD $660/year
- 3-year RI (monthly payments): ~USD $56/month — saving USD $84/month = USD $3,024 over 3 years
When to buy RIs: After 3–6 months of running a workload and confirming the VM size is stable. Do not buy RIs for VM sizes that are likely to change or workloads that may be decommissioned.
RI flexibility: Azure RIs for most VM sizes include instance size flexibility — a D4s_v5 RI applies to any D-series VM in the same size group, not just the specific D4s_v5 model.
Storage Cost Governance
Azure Storage is the most common source of unexpected cost growth for Philippine organisations. Data accumulates without a deletion or tiering policy.
Blob Lifecycle Management
Admin portal path: Storage Account → Data management → Lifecycle management
Configure a policy that automatically:
- Moves blobs not accessed for 30 days from Hot to Cool tier (approximately 50% storage cost reduction)
- Moves blobs not accessed for 90 days from Cool to Cold tier
- Moves blobs not accessed for 180 days to Archive tier
- Deletes blobs not accessed for 365 days (configure per container as appropriate)
Example savings: 10TB of application logs stored in Hot tier costs approximately USD $200/month. The same data in Archive tier costs approximately USD $10/month.
Unattached Disk Cleanup
When a VM is deleted, its OS disk and data disks frequently remain — still billing at the managed disk rate. Azure Advisor identifies unattached managed disks.
Admin portal path: Advisor → Cost → unattached disks recommendation
Review and delete unattached disks that are not intentionally retained as backups. For Philippine organisations with high VM turnover (dev/test environments), this is often USD $20–50/month of hidden cost per resource group.
Tagging for Cost Allocation
Without resource tags, Azure cost reports show spend by service and resource — but not which team, project, or cost centre is responsible. For Philippine organisations with multiple departments on a shared Azure subscription, tagging is the prerequisite for internal cost chargeback or showback.
Minimum tag schema:
Environment: Production | Development | Staging | Test
Department: IT | Finance | Operations | HR
Project: [project name]
CostCentre: [internal cost centre code]
Owner: [email of accountable person]
Enforcement: Apply an Azure Policy that requires the Environment, Department, and Owner tags on all resource groups. Resources created without these tags are flagged in Advisor.
Philippine FinOps Maturity Path
| Stage | What to do | Expected savings |
|---|---|---|
| Month 1 | Set budgets, configure anomaly alerts, review Cost Analysis | Prevents runaway spend |
| Month 2–3 | Implement right-sizing recommendations from Advisor | 15–25% compute reduction |
| Month 3–6 | Schedule dev/test VMs, lifecycle policies for storage | 20–30% additional reduction |
| Month 6+ | Purchase RIs for stable production workloads | 36–63% compute discount |
For Philippine organisations on Azure managed services, see our Azure Managed Services guide and cloud migration guide.
Related reading: Azure managed services Philippines · Cloud migration guide · Azure virtual network Philippines · Disaster recovery Azure
For Philippine organisations optimising Azure cloud spend — FinOps assessment and implementation — available through Technica Solutions Inc., get in touch.
Talk to our Cloud & I.T. team →
