The course is part of these learning paths
Azure Advisor Cost Recommendations
Monitoring Cost Consumption
Cost Management Report
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 aims to be 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 dedicated MS Azure Training Library.
Understanding cost is very important when operating in the Cloud at any scale. Over time it can become a difficult task to understand where exactly which groups or systems are costing you a lot of money. We will cover some tools and methods that will hopefully help keep your costs under control. One of the first steps is to utilize Resource Tagging. Tagging exists on every resource in Azure, whether the resource is free or charged by usage. This tagging structure is completely up to you and your organization. It is department based, cost center based, or you could just put the person's name on the resource. Here we can see we have added three tags to a resource group.
Solution, Owner, and Environment. You can also include resource tags within your adjacent ARM templates, or through PowerShell. Viewing Costs by Resource Tag. In the Azure portal, go to 'Cost Management and Billing' section. Under the Cost Management section you can go to Cost Analysis, then select 'Group by' and select 'Tag' from the bottom of the drop-down menu. In this screenshot we can clearly see the tagging has only been partially successful, with the largest cost under 'Subscription' coming from untagged resources.
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.