{"id":15263,"date":"2021-07-08T07:07:52","date_gmt":"2021-07-08T11:07:52","guid":{"rendered":"https:\/\/www.eginnovations.com\/blog\/?p=15263"},"modified":"2026-08-04T06:47:45","modified_gmt":"2026-08-04T10:47:45","slug":"estimate-azure-monitor-costs-for-avd","status":"publish","type":"post","link":"https:\/\/www.eginnovations.com\/blog\/estimate-azure-monitor-costs-for-avd\/","title":{"rendered":"Estimating Azure Monitor Costs for AVD"},"content":{"rendered":"
\n

<\/span>Using Azure Monitor for Monitoring Azure Virtual Desktop (AVD) and Estimating Your Costs<\/span><\/h2>\n

In my last blog, I wrote about how to set up Azure Monitor for WVD leveraging a Log Analytics Workspace<\/a>. In this next installment I\u2019ll cover how you can proceed from this point and add in thresholds on metrics and signals that when crossed will generate alerts which can trigger actions. As with most things in Azure, alerting is essentially PAYG so I will also cover some guidance on how you can start to estimate the costs of monitoring and alerting. Since my last blog Microsoft have changed the name of WVD (Windows Virtual Desktop)<\/a> to AVD (Azure Virtual Desktop). An excellent overview of the reasons behind, and implications of, the change is available from Vadim Vladimirskiy at Nerdio<\/a>.<\/p>\n

Once you have set up a Log Analytics Workspace you will be able to setup and view various Dashboards or Workbooks in Azure Monitor or use other methods of visualizing and collating the data – for example, Power BI and Graphana are some of the integrations available. Azure dashboards are free to use so I am not going to cover them in this blog, they are well-documented in the Microsoft documentation, here<\/a>. My ultimate goal is to try and work out how to calculate and estimate my end costs and Azure bill will be for monitoring and billing hence the emphasis on PAYG features.<\/p>\n

In the previous blog<\/a>, \u00a0I started with an existing host pool named \u201cUKGROUP\u201d containing two WVD (now AVD – Azure Virtual Desktop) session hosts within a resource group \u201cegwvd\u201d located in the Azure region \u201cEast US 2\u201d, I connected them all into a Log Analytics Workspace named \u201cRachels-LogAnalyticsWorkspace\u201d and then added a 3rd<\/sup> session host. This is the configuration I will cover adding monitoring and alert thresholds to, today.<\/p>\n

<\/span>What you can monitor and raise alerts on with Azure Monitor?<\/span><\/h2>\n

\"ManAt this point, it is worth familiarizing yourself with the Azure Monitor Documentation<\/a>. From the home page, you can navigate through the documentation tree on the left-hand side to \u201cHow-to-Guides” and then \u201cAlerts\u201d, however you should be aware that in addition to \u201cHow-to guides -> Alerts\u201d you will probably want to familiarize yourself \u00a0 sections like \u201cHow-to guides -> VM Insights -> Alerts\u201d and possibly even \u201cHow-to-guides -> Application Insights -> Alerts” (Azure\u2019s APM monitoring).<\/p>\n

For the Azure Virtual Desktop host pool, in my last blog we configured collection of the default Performance counters<\/strong> and Windows event logs<\/strong>. Log alerts can be associated with any of these metrics and log events.<\/p>\n

There are also two types of log alerts in Azure Monitor associated with VM Insights (VM Insights being an optional agent you can install within the VMs in your Azure Virtual Desktop host pool, covered in my last blog:<\/p>\n