Azure Advisor Cost Recommendations
Monitoring Cost Consumption
Cost Management Report
The course is part of these learning pathsSee 3 more
This course looks into how to capture log data and metrics from Azure services and feed this information into different locations for processing. We take a look at diagnostic logging, which can help to troubleshoot services and create queries and alerts based on that data. We also look into Azure Adviser, cost consumption reporting, and how we can baseline resources. This is an introduction to these advanced areas of Azure services.
- Understand how to use and configure diagnostic logging for Azure services
- Gain an understanding of Azure Monitor and how to create and manage alerts
- Review cost consumption reporting and how to create scheduled reports
- Investigate different methods for baselining resources
- People who want to become Azure cloud architects
- People preparing for Microsoft’s AZ-100 or AZ-300 exam
- General knowledge of Azure services
For more MS Azure-related training content, visit our Microsoft Azure Training Library.
Azure has some built-in algorithms to help identify cost savings. These can vary depending on how you use the system, but it's worth taking some time to review the suggestions and recommendations. One of the most common recommendations, if you have long-running virtual machine instances, is to purchase reserved instances. If we take a look at the screenshot, the Azure Advisor shows nine VMs it has determined to be around long enough to suggest that if we had reserved instance, and made a commitment to these resources, we could potentially save $2,700 US per year. Advisor recommendations are based on the last 14 days of usage and target low utilization systems.
Recommendations could include:
- Eliminating unprovisioned ExpressRoute circuits. It identifies ExpressRoute circuits that have been in the status of Not Provisioned for more than a month.
- Deleting or reconfiguring idle virtual network gateways (virtual network gateways that have been idle for over 90 days). Since these gateways are built hourly, you should consider reconfiguring them or deleting them if you don't tend to use them anymore.
- Based on usage, recommending a more appropriate VM size. Virtual machines whose CPU utilization is 5% or less, and the network usage is 7 meg or less for four days or more, are considered low utilization virtual machines.
About the Author
Matthew Quickenden is a motivated Infrastructure Consultant with over 20 years of industry experience supporting Microsoft systems and other Microsoft products and solutions. He works as a technical delivery lead managing resources, understanding and translating customer requirements and expectations into architecture, and building technical solutions. In recent years, Matthew has been focused on helping businesses consume and utilize cloud technologies with a focus on leveraging automation to rapidly deploy and manage cloud resources at scale.