Changelog

What's new in Cirrova

Updates, improvements, and new features rolling out to the Cirrova platform. Most recent first.

Feature

Centralised alerting & custom webhooks

All of Cirrova's alerting now lives in one place: a new Alerting page under Organisation Settings, with two tabs — Channels (where notifications go) and Rules (which events route to which channels). Channels and rules are independent, so one delivery destination can be reused across many rules and one rule can fan out to many destinations.

The launch also adds a custom webhook channel type. Cirrova will POST JSON-encoded events to any HTTPS endpoint you control — signed with HMAC-SHA256, retried on failure, with optional custom headers — so anomalies, budget breaches, and snapshot failures can flow into your own systems alongside the existing email / Microsoft Teams / Slack channels.

What changed

  • New Organisation Settings → Alerting page replaces per-tenancy alert recipients and the Alerts & notifications card on each tenancy's settings.
  • Channels are named, reusable delivery endpoints — Email, Microsoft Teams, Slack, or Custom webhook. Each has an enabled flag and a Send test action for verifying reachability before wiring it into rules.
  • Rules match platform events (Anomaly detected, Anomaly resolved, Budget threshold crossed, Snapshot failed) to one or more channels, with optional scope filters per event type — by tenancy, subscription, resource group, tag, or specific budget.
  • New Custom webhook channel type with HMAC-SHA256 signing, retry schedule, and a documented payload schema for every event type. A test event is sent when you click Send test, with the same headers and signing as production deliveries.
  • New Delivery history view per rule: every attempt, the channel that received it, the resulting status, and a detail line for failures — the first place to look when an alert didn't arrive.
  • The New Budget dialog no longer takes alert recipients — thresholds still live on the budget, but routing is decided centrally on the Alerting page.
  • Anomaly sensitivity remains a per-tenancy setting and is still managed on the tenancy's Cost tracking tab.
Read the docs
Feature

Tag-scoped budgets

Budgets can now be scoped to a tag key/value pair, aggregating spend across every resource carrying that tag — regardless of which tenancy or subscription it lives in. The new scope is called Tag Collection.

The motivating use case is cross-tenancy departmental budgeting. A team running workloads across multiple subscriptions, and possibly multiple Azure tenancies, can now see total spend rolled up in one place — tag every resource Department=Marketing (or whatever fits), create a single Tag Collection budget on that key/value pair, and the right number falls out without any manual aggregation.

What changed

  • New Tag Collection option in the New Budget dialog. The tag key dropdown is populated from tag keys actually present on resources in your organisation, with an optional tag value — leave it blank to match any value for the chosen key.
  • The Scope filter on the Budgets page gains a Tag Collection option. Tag-scoped budgets render with a yellow Tag Collection badge and show the matched key = value pair plus an Organisation-wide subtitle to make their cross-tenancy reach explicit.
  • Stricter permission rule: managing a Tag Collection budget requires either organisation owner or tenancy admin on every tenancy attached to the organisation. Subscription, Resource Group, and Tenancy budgets continue to be manageable by an organisation owner or by a tenancy admin on the relevant tenancy alone.
  • The Tag Collection scope option is hidden in the New Budget dialog for users who don't qualify for the stricter permission, so the option doesn't appear available to people who can't actually use it.
  • Subscription and Resource Group scopes also gained multi-target selection in the same release — pick a tenancy, then tick multiple subscriptions, or add multiple resource groups across different subscriptions, into one cap.
Read the docs