Fix: "Management group does not have any valid subscriptions" in Azure Cost Management

Why does this error happen?

Under an Enterprise Agreement or a direct Microsoft Customer Agreement, your billing account lives in your own tenant, so Cost Management can aggregate costs at billing account, department, or management group scope. Under CSP, the billing account lives in your partner's tenant. Your tenant keeps the management group hierarchy, but Cost Management has no billing scope to aggregate against.

Microsoft's Understand and work with Cost Management scopes documentation states it directly: "Cost Management doesn't support Management groups in CSP scopes," and shows this exact error as the result of trying: Management group <ManagementGroupName> does not have any valid subscriptions. The same page notes that the Cost Details API doesn't support management group scope for EA or MCA customers either — so there is no API-side escape hatch at that scope.

There is no announced timeline for management group support under CSP. If your organization needs a tenant-wide cost view, plan around the limitation rather than waiting for it to change.

What can you do about it?

1. View costs one subscription at a time (free)

Cost Analysis still works at subscription and resource group scope. For a handful of subscriptions this is workable — switch scope, read the number, repeat. For 10, 20, or 50+ subscriptions it becomes a manual aggregation exercise in a spreadsheet, with no shared trend view, no cross-subscription grouping, and costs shown at pay-as-you-go rates rather than your partner's pricing.

2. Script the Cost Details API per subscription (free, but you build the plumbing)

Every Cost Management API that works under CSP works at single-subscription scope. You can loop your subscriptions and merge the results:

# Query cost per subscription and merge — the DIY consolidation loop
$subs = Get-AzSubscription
$results = foreach ($sub in $subs) {
  Invoke-AzRestMethod -Method POST `
    -Path "/subscriptions/$($sub.Id)/providers/Microsoft.CostManagement/query?api-version=2023-11-01" `
    -Payload (@{
      type      = "ActualCost"
      timeframe = "MonthToDate"
      dataset   = @{ granularity = "Daily"; aggregation = @{ totalCost = @{ name = "Cost"; function = "Sum" } } }
    } | ConvertTo-Json -Depth 10)
}
# ...then normalize schemas, handle paging and 429s, and store the merged output yourself

This genuinely works, and for a one-off answer it may be all you need. As a standing reporting pipeline, you own the storage, the scheduling, the schema normalization, retry/paging behavior, and rate-limit handling — and reservation amortization still shows zero at CSP subscription scope, so amortized reporting needs to be rebuilt separately.

3. Per-subscription exports + FinOps toolkit (free tooling, real setup cost)

Microsoft's FinOps hubs support CSP, but the FinOps hubs documentation notes that CSP customers need to configure exports for each subscription individually, because Cost Management doesn't support management group exports for MCA or CSP subscriptions. You then run the hub infrastructure (storage, ingestion, optionally Data Explorer or Fabric) and keep up with monthly toolkit releases. It's a solid path if you have a FinOps engineering function; it is not a quick fix.

4. Deploy a maintained consolidation layer

CSP Continuity automates option 2 as a managed application inside your tenant: it collects from every subscription via the Cost Details API on a daily schedule, consolidates the results into a SQL database, and exposes the consolidated data three ways — an in-portal Azure Monitor Workbook dashboard, Parquet files for Power BI, and a query API at /api/costmanagement/query that accepts Microsoft's request format and returns Microsoft's {id, name, type, properties: {columns, rows}} response format. Existing scripts pointed at the Microsoft endpoint work with a URL swap, and grouping isn't limited to two dimensions.

Deployment is about 5 minutes from the Azure Marketplace, plus one 2-minute PowerShell script to grant read-only permissions. Up to 13 months of history is typically available within hours. All data stays in your tenant.