Budgets and Cost Alerts After Moving to CSP — What Still Works

What still works at subscription scope?

Per Microsoft's Cost Management for partners documentation, CSP customers get Cost Analysis, budgets, and alerts at subscription and resource group scope, evaluated against pay-as-you-go-rate costs. Two prerequisites and one caveat:

• The cost visibility policy must be enabled by your partner. It's disabled by default for subscription users in the customer tenant. If cost views are empty, this is the first thing to check.
• New subscriptions warm up. Microsoft's budgets tutorial notes it can take up to 48 hours before all Cost Management features work on a new subscription.
• Retail rates, not partner pricing. "Costs shown don't include any discounts or credits that the partner may have" — budgets fire on consumption at list rates, which is fine for trend control, imperfect for invoice reconciliation.

Anomaly alerts also work: Microsoft documents anomaly detection for subscriptions monitored in Cost Analysis, with alert rules created at subscription scope only, up to five rules per subscription, requiring the Cost Management Contributor role. No CSP-specific exclusion is documented.

What doesn't work — and why?

Anything that needs a scope above subscription. Management group budgets fail because Cost Management doesn't support management groups in CSP scopes; billing-account budgets and alerts live in the partner's tenant. In practice that means:

• No single budget covering the whole tenant — only one budget per subscription, maintained per subscription.
• No cross-subscription anomaly detection — each subscription's rules see only that subscription's spend. A pattern spread across many subscriptions never trips any single rule.
• Per-subscription administration scales linearly: five rules × N subscriptions, plus budget upkeep as subscriptions come and go.

How do you get tenant-wide alerting back?

1. Maintain per-subscription budgets systematically (free)

Budgets can be created programmatically, so a script can enforce a standard budget and alert set on every subscription. This keeps per-subscription guardrails consistent, though thresholds are still per subscription, and someone owns the script.

2. Alert on consolidated data you collect (DIY)

If you build per-subscription collection — API loop or FinOps hubs — you can implement budgets and anomaly detection on the merged dataset with your own queries and alerting.

3. Use the built-in anomaly detection on consolidated data

CSP Continuity's consolidated database gives anomaly detection the tenant-wide view the portal can't: it compares daily costs against trailing 30-day averages across all subscriptions and exposes results via its REST API, so you can wire alerts into whatever already pages your team. It complements — rather than replaces — the per-subscription portal budgets above: keep those for hard guardrails, use consolidated detection for the patterns no single subscription reveals.