azurerm_powerbi_embedded cost estimation

An azurerm_powerbi_embedded resource provisions dedicated capacity (an A-SKU) for embedding Power BI reports and dashboards into applications. Cost is a flat hourly rate by SKU, and the SKUs double in size and price up the ladder: A1 ~$1.0081/hour (~$736/month), A2 ~$2.02, A3 ~$4.03, A4 ~$8.06, and so on.

The capacity bills continuously while running — but, crucially, Power BI Embedded capacity can be paused, and pausing stops the charge entirely. For workloads that only serve embedded reports during business hours, or for dev/test capacity, pausing off-hours is the single biggest lever, cutting cost by more than half.

The other decision is right-sizing the SKU: each step up doubles capacity (v-cores and memory) and price. Over-provisioning to A3/A4 for a workload that A1 handles is a common, expensive default.

c3x prices the capacity from sku_name, so the standing monthly cost — and the impact of the SKU choice — is visible before deployment.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_powerbi_embedded" "reports" {
  name                = "embedded-reports"
  resource_group_name = azurerm_resource_group.main.name
  location            = azurerm_resource_group.main.location
  sku_name            = "A1"

  administrators = ["admin@example.com"]
}

Pricing dimensions

What you actually pay for when you provision azurerm_powerbi_embedded.

Dimension	Unit	What's being charged
Embedded capacity	per hour	Flat hourly rate by A-SKU, billed while the capacity is running. Pausing stops the charge. $1.0081/hour for A1 → ~$735.91/month; each SKU step roughly doubles it

Sample C3X output

An A1 capacity running 24/7 (the avoidable case — pause off-hours):

azurerm_powerbi_embedded.reports
└─ Embedded capacity (A1)   730 hours   $735.91
                            Monthly     $735.91

Optimization tips

Common ways to reduce azurerm_powerbi_embedded cost without changing the workload.

Pause capacity when not in use

Up to ~70% with off-hours pausing

Power BI Embedded capacity can be paused, which stops billing entirely. For business-hours-only embedding or dev/test, a schedule that pauses nights and weekends cuts cost by more than half — the single biggest lever.

Right-size the A-SKU

Roughly halves cost per SKU stepped down

Each SKU step up doubles capacity and price. Start at A1 and scale up only when you measure the capacity being saturated — over-provisioning to A3/A4 'for headroom' is expensive idle capacity.

Scale up temporarily for peaks, then back down

Difference vs sizing for peak permanently

Rather than running a large SKU 24/7 for occasional peak load, scale the capacity up before a known peak and back down after. Embedded supports changing SKU without redeploying.

Consider Fabric/Premium Per User for some scenarios

Workload-dependent

Depending on the audience and usage, Microsoft Fabric capacities or Premium Per User licensing can be more cost-effective than dedicated A-SKU embedded capacity. Evaluate against your user count.

FAQ

How is Power BI Embedded billed?

Per hour by A-SKU while the capacity is running — A1 is ~$1.0081/hour (~$736/month), and each step up (A2, A3, …) roughly doubles capacity and price. Critically, the capacity can be paused, which stops the charge.

Can I pause Power BI Embedded to save money?

Yes — pausing stops billing entirely. For embedding that's only needed during business hours, or for dev/test capacity, scheduling pauses off-hours is the biggest saving, often cutting cost by well over half.

How does c3x estimate the cost?

From sku_name, pricing the hourly capacity rate (shown at 24/7 as the ceiling). Real cost depends on running hours — pausing brings it well below the ceiling.

Related resources

Azure

azurerm_analysis_services_server

Another pausable analytics capacity with similar economics

`azurerm_powerbi_embedded` cost estimation