Client Context
The organization was using Microsoft Azure to support cloud workloads across different environments. As usage expanded, the customer wanted better visibility into whether deployed resources were still needed, properly sized, and aligned with current demand.
Cloud usage can grow quickly. Teams may deploy resources for projects, testing, development, temporary workloads, or production needs. Over time, resources can become idle, oversized, misaligned, or forgotten. Even when each individual resource appears small, accumulated waste can affect cloud spend and operational complexity.
The source material defines usage optimization as an approach for maximizing cloud investment and avoiding underutilized resources and resource features. It also emphasizes matching deployed cloud resources to actual workload needs and using governance, automation, and monitoring to continuously improve.
BI Cloud Tech helped the customer review these concepts and translate them into practical Azure operating practices.
Customer Challenge
The customer needed a repeatable way to identify resources that were not being used effectively. Idle or underutilized resources can continue to generate charges even when they are no longer supporting an active workload.
The customer also needed a better process for non-production environments. Development and test resources often have different usage patterns than production. They may not need to run continuously, and they may be eligible for Dev/Test pricing or automated shutdown practices.
Storage was another area that needed review. Data can accumulate over time, and not all data needs to remain in the same access tier forever. Without lifecycle management, storage may remain in a higher-cost tier even when usage patterns have changed.
The organization also needed better use of recommendations and alerts. Azure Advisor and related tooling can surface opportunities, but teams need a process to review, validate, and act on recommendations.
How We Helped
BI Cloud Tech helped the customer review Azure usage optimization as an operating discipline. The review connected technical resource analysis with FinOps ownership, governance, and automation.
The engagement focused on six practical areas: identifying idle resources, using cost optimization workbooks, creating proactive FinOps alerts, reviewing Dev/Test subscription usage, automating non-production VM shutdown, optimizing blob storage lifecycle management, and using Azure Advisor alerts and recommendation digests.
BI Cloud Tech helped frame each area as a review and decision process. Not every resource should be deleted, resized, shut down, or moved to another tier without validation. Workload owners need to confirm purpose, performance, availability, retention, and business requirements.
This helped the customer approach usage optimization responsibly rather than treating all recommendations as automatic changes.
Idle Resource Review
The review included idle resource identification. The source material notes that idle Azure resources may continue to incur charges even when they are not being used. It also identifies examples such as unattached managed disks, unattached public IPs, idle load balancers, idle application gateways, and idle app services.
BI Cloud Tech helped the customer understand how idle resource review can reduce waste and simplify the environment. Idle resources can create both cost and management overhead. They may also make the Azure estate harder to understand because unused components remain visible in reports, inventories, and operational reviews.
The review emphasized approval and ownership. A resource should not be removed simply because it appears idle. Teams should confirm whether it is needed, whether it supports recovery or testing, and whether there are dependencies.
This helped position waste removal as a controlled operational process.
Cost Optimization Workbooks and Review Cadence
The Azure Cost Optimization Workbook was reviewed as a useful tool for surfacing cost-relevant insights. The source material states that the workbook provides recommendations aligned with the Well-Architected Framework cost optimization pillar, including Azure Advisor cost recommendations, idle resource identification, improperly deallocated virtual machines, and Azure Hybrid Benefit insights.
BI Cloud Tech helped the customer see the workbook as part of a recurring review cadence. A workbook is useful only when teams review it regularly, assign ownership, and track decisions.
The customer needed a process for reviewing recommendations monthly or quarterly, depending on operational needs. Recommendations could be grouped by workload, subscription, resource type, risk level, or potential action.
This approach helped the customer avoid one-time cleanup behavior and move toward continuous optimization.
FinOps Alerts with Azure Logic Apps
The review also included proactive FinOps alerting. The source material describes a FinOps alerts Logic App that scans the Azure environment for idle resources and sends notifications to designated administrators. It can run on a configurable schedule and can be tailored for recurrence, recipients, and subscriptions.
BI Cloud Tech helped the customer evaluate how automated alerts could support timely action. Instead of waiting for manual reviews, automated monitoring can notify the right stakeholders when potential waste is detected.
The review also considered alert quality. Alerts are only useful when they are actionable. Too many alerts can create noise, while too few alerts may miss important opportunities. The customer needed to define alert recipients, escalation paths, review expectations, and closure criteria.
This helped connect automation to a broader FinOps process rather than treating it as a standalone script.
Dev/Test Subscription Optimization
Non-production environments were a key topic. The source material describes Azure Dev/Test pricing for non-production workloads under the Microsoft Customer Agreement and notes that it can apply to services such as virtual machines, Azure SQL Database, Logic Apps, App Service, Cloud Services instances, and HDInsight instances.
BI Cloud Tech helped the customer review how development and test workloads were organized. Non-production resources often have different cost and uptime requirements from production resources. This creates opportunities to review subscription placement, pricing eligibility, resource schedules, and workload ownership.
The review also helped the customer consider billing simplicity and governance. Dev/Test usage should be visible and controlled, not hidden. Teams still need tagging, ownership, cost reporting, and policies even when non-production pricing applies.
This helped the customer think about Dev/Test as a managed operating model, not just a pricing option.
Non-Production VM Shutdown Automation
The review included automation options for non-production virtual machines. The source material describes using Azure Functions and Azure Logic Apps to configure and manage start and stop schedules for VMs, including scheduled start and stop actions, sequenced actions, and AutoStop patterns.
BI Cloud Tech helped the customer consider where shutdown automation could be appropriate. Some development or test VMs may not need to run outside business hours. Automating shutdown can help align usage to actual need.
The review also emphasized that automation requires careful design. Teams need to define exclusions, ownership, schedules, restart requirements, time zones, and support expectations. Some workloads may need to remain available for testing windows, batch jobs, or shared team use.
A responsible VM shutdown model balances cost efficiency with team productivity and operational reliability.
Blob Storage Lifecycle Management
Storage optimization was another important area. The source material explains that Azure Blob Storage lifecycle management can use rule-based policies to transition data to cooler tiers or expire data when it is no longer needed. It also describes using a PowerShell script to identify blobs that have not been modified in the last 30 or 365 days as potential candidates for Cool or Archive tiers.
BI Cloud Tech helped the customer review how storage usage patterns could inform lifecycle policies. Not all data has the same access requirements. Some data is active, some is infrequently accessed, and some may be retained only for compliance or historical reasons.
The review also emphasized validation. Before moving or expiring data, teams need to confirm retention requirements, recovery needs, application dependencies, and access patterns.
This helped the customer approach storage optimization as a lifecycle management practice rather than a simple cost-cutting exercise.
Azure Advisor Recommendations, Alerts, and Digests
Azure Advisor was reviewed as a key source of recommendations. The source material describes Azure Advisor as a personalized cloud consultant that analyzes resource configuration and usage telemetry and recommends solutions that can improve cost effectiveness. It also describes Advisor alerts and recommendation digests for proactive notification.
BI Cloud Tech helped the customer understand how Advisor could fit into its FinOps operating rhythm. Recommendations should be reviewed, assigned, accepted, deferred, or rejected with a clear reason.
Advisor alerts can notify teams when new recommendations appear. Recommendation digests can provide periodic summaries across categories. These capabilities can help the customer stay aware of optimization opportunities without relying only on manual portal checks.
The review helped position Azure Advisor as a decision-support tool. It can identify opportunities, but workload owners still need to validate whether each recommendation makes sense.
Microsoft Cloud Capabilities Used
The review included several Microsoft cloud capabilities and practices:
- Azure Cost Optimization Workbook for identifying idle resources, cost recommendations, and cost optimization opportunities.
- Azure Advisor for recommendation review, alerts, and periodic recommendation digests.
- Azure Logic Apps for proactive FinOps alerting and orchestration of cost-related notifications.
- Azure Functions for supporting automation scenarios such as VM start and stop actions.
- Azure Dev/Test subscriptions and pricing concepts for reviewing non-production cost models.
- Azure Blob Storage lifecycle management for tiering or expiring data based on usage and retention needs.
- Azure Activity Log and action groups for recommendation alerting and notification workflows.
- Well-Architected Framework cost optimization practices for reviewing resources against workload requirements.
These capabilities were reviewed together because usage optimization works best when monitoring, governance, automation, and workload ownership are connected.
What Improved
The customer gained a clearer view of how usage optimization could become a repeatable Azure operating practice. The review connected idle resource detection, alerts, Dev/Test optimization, VM scheduling, storage lifecycle management, and Advisor recommendations into a practical improvement path.
The customer also gained a better understanding of where automation could help. Logic Apps, Azure Functions, Advisor alerts, and recommendation digests can reduce manual effort, but they need ownership and review processes.
The review helped clarify that optimization should be validated before action. Removing resources, changing tiers, resizing workloads, or applying shutdown schedules can provide value only when aligned with workload requirements.
Most importantly, the customer had a clearer path for reducing avoidable waste while maintaining operational control.
Business Value
The main business value was improved control over Azure usage. By identifying idle resources and reviewing underutilized components, the customer could reduce avoidable complexity and improve cloud hygiene.
Proactive alerts can help teams respond earlier. Instead of waiting for a monthly cost surprise, stakeholders can be notified when idle resources or recommendations require review.
Dev/Test optimization can help ensure non-production environments are managed according to their actual purpose. This supports better cost alignment without treating development and production workloads the same way.
Storage lifecycle management can help match data placement to access patterns. This helps the organization manage growing storage environments more intentionally.
Why This Matters
Usage optimization is a core part of FinOps. Cost transparency explains where money is going, but usage optimization helps teams act on that information.
Organizations that review usage regularly are better prepared to remove waste, right-size resources, schedule non-production workloads, manage storage lifecycle, and act on Advisor recommendations.
BI Cloud Tech’s Azure Infrastructure expertise helps organizations review Azure resource design and operational practices. A Cost Optimization and FinOps Assessment can help identify maturity gaps and prioritize next steps.
For ongoing support, FinOps as a Service can help maintain reporting, review, and optimization cadence. BI Cloud Tech’s Azure Operations services can help keep optimization connected to day-to-day cloud management.
Recommended Next Step
Organizations using Azure should review usage optimization practices regularly. A practical review should include idle resources, cost optimization workbooks, Advisor recommendations, Dev/Test usage, non-production schedules, storage lifecycle policies, and proactive alerts.
The next step is to define which optimization activities should happen monthly, who owns each review, and how recommendations are validated before action.
Request an Assessment to review Azure usage optimization opportunities and build a practical FinOps automation roadmap.