AzureAzure Managed GrafanaManagement

`azurerm_dashboard_grafana` cost estimation

A managed Grafana instance for dashboards and observability. Priced on a per-instance hourly node fee plus a per-active-user charge.

An azurerm_dashboard_grafana provisions a managed Grafana workspace so you don't run and patch Grafana yourself. The Standard plan has two cost parts: an always-on instance (node) fee billed per hour, and a per-active-user monthly charge.

The instance fee runs around $0.0342/hour (about $25/month) for the base node, covering the running Grafana service. On top of that, each active editor or admin user is roughly $6/month; viewers are typically included. Optional availability-zone redundancy adds a node surcharge. So a small team's Grafana is the ~$25 base plus a few dollars per editor.

c3x prices the instance hours at 730 hours/month and the active-user dimension from the user count you supply in c3x-usage.yml. Compared to self-hosting Grafana on a VM, the managed service trades the VM and ops cost for this per-instance-plus-user model, which is usually cheaper once you count patching and availability work.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_dashboard_grafana" "obs" {
  name                  = "team-grafana"
  resource_group_name   = azurerm_resource_group.mon.name
  location              = "eastus"
  grafana_major_version = "11"

  sku = "Standard"

  identity {
    type = "SystemAssigned"
  }
}

Pricing dimensions

What you actually pay for when you provision azurerm_dashboard_grafana.

Dimension	Unit	What's being charged
Instance (node) hours	per hour	Always-on base node fee for the managed Grafana service. c3x assumes 730 hours/month. $0.0342/hour (~$25/month)
Active users	per user-month	Per active editor/admin. Viewers are typically included. Usage-based; define active_user_count in c3x-usage.yml. $6/active editor/month
Zone redundancy	per node-hour	Optional AZ redundancy adds a node surcharge. Only when enabled.

Sample C3X output

Example output from c3x estimate (Standard, 1 active editor):

azurerm_dashboard_grafana.obs
├─ Instance (Standard)        730  hours        $24.97
└─ Active users                 1  user-month    $6.00

OVERALL TOTAL                                   $30.97

Optimization tips

Common ways to reduce azurerm_dashboard_grafana cost without changing the workload.

Count only active editors, not viewers

Per unnecessary editor seat

The per-user charge applies to editors and admins. Granting viewer access where edit rights aren't needed keeps users off the billed seat count.

Skip zone redundancy for non-critical dashboards

Redundancy node surcharge

AZ redundancy adds a node surcharge. Internal observability dashboards rarely need it; reserve it for dashboards that page on-call during an AZ outage.

Consolidate to one workspace

Per avoided instance

Each managed Grafana instance carries the always-on base fee. A single workspace with folders and team permissions usually serves the whole org more cheaply than per-team instances.

FAQ

How does c3x estimate Azure Managed Grafana cost?

It prices the always-on instance (node) hours at 730 hours/month and the active-user dimension from the count you supply in c3x-usage.yml. Zone redundancy, if enabled, adds a node surcharge.

Are viewers charged?

Typically no. The per-user charge applies to active editors and admins. Viewer access is generally included, so granting view-only rights doesn't grow the billed seat count.

Why is there an always-on cost even with no users?

The managed Grafana node runs continuously and bills per hour (~$25/month) independent of user activity. User charges are on top of that base.

Is managed Grafana cheaper than self-hosting?

Usually, once you account for the VM, patching, and availability work of self-hosting. The managed base fee plus per-editor charge is often less than a comparably-available self-managed Grafana VM.