Updates, improvements, and new features rolling out to the Cirrova platform. Most recent first.
Feature
Test alert rules, and see what needs attention from anywhere
Alert rules now have their own Send test action. Where the existing channel test proves a single destination is reachable, a rule test exercises the whole path — it builds a sample event of the rule's type and fans it out to every channel attached to the rule, then reports back per channel. If a rule fires but only some of its destinations light up, this is where you'll see it.
The sidebar has also grown count badges on Insights and Anomalies, so there's a visible cue that something is waiting without having to open each page to check.
What changed
New Send test action in the row menu on Organisation Settings → Alerting → Rules, alongside Edit and Delivery history.
The test sends a realistic sample of the rule's event type through each attached channel, so every notification renders with proper values rather than placeholders. Sample data is prefixed [TEST] in the most prominent field, so nobody receiving one mistakes it for a live alert.
Results are listed per channel — delivered or failed, with the failure reason inline, plus a 2 of 2 channels delivered summary. A disabled channel is reported as such rather than silently skipped.
A rule test never writes to delivery history and never marks an event as already-notified, so testing a rule cannot suppress a real alert that follows.
Scope filters are not applied to a test send — the sample event has no real tenant or resource behind it. The dialog says so, so a green result isn't read as confirmation that your scope filters are correct.
Count badges on the Insights and Anomalies sidebar items. Anomalies counts only those still Active — acknowledging one clears it from the badge. Insights counts findings that are neither dismissed nor snoozed. Both respect the tenants you have access to, and update immediately when you acknowledge or dismiss.
Multi-channel alert rules, and missing detail in anomaly emails
Two fixes to alerting. If you configured a rule to notify more than one channel, only the first channel in the rule ever received the notification — the others were skipped, with nothing recorded in delivery history to show it had happened. Rules with a single channel were unaffected, and channel tests always worked, which made the gap easy to miss.
Separately, anomaly emails sent through alert rules were arriving with some of their detail missing — resource type and tenant showing as Unknown, the baseline, last 24 hours and change figures as N/A, a raw timestamp, and a View in Cirrova button that wasn't a working link.
What changed
Alert rules now deliver to every channel attached to them. Duplicate suppression is applied per channel rather than per rule, so one destination receiving an event no longer prevents the rest from getting it.
Anomaly notifications sent via alert rules now carry their full detail — resource type, tenant, baseline daily average, last 24 hours, and the percentage change — in email, Microsoft Teams, and Slack alike.
View in Cirrova links directly to the affected resource, falling back to the Anomalies page where the resource can't be resolved. It is always a real link, never an inert button.
Timestamps in rule-driven notifications are formatted for reading rather than shown raw.
Configurable spend charts & new App Service Plan insight
The spend charts on the Dashboard and Cost Explorer have grown a set of in-place controls. Pick the period, group the bars by tenant / subscription / resource group / resource type / cost centre, switch between line / area / stacked column / grouped column, and toggle between daily and accumulated views — without leaving the page.
A new Orphaned Resource rule also catches App Service Plans with no hosted apps or function apps — the SKU keeps billing whether the plan is doing anything or not, so it's worth surfacing alongside orphaned disks and unattached public IPs.
What changed
Period selector on the Dashboard daily-spend chart and as a page-level filter on Cost Explorer. Calendar ranges (this month / quarter / year, last quarter, last 3 / 6 / 12 months), relative ranges (last 7 / 30 / 90 days), and a custom date range.
Group dimension on both charts — None, Tenant, Subscription, Resource Group, Resource Type. Cost Explorer adds Cost Centre as an extra option, turning the spend chart into an instant chargeback view.
Chart type selector — Line, Area, Stacked Column (default), or Grouped Column.
Daily / Accumulated toggle. The chart title updates to match the configuration: Daily spend & rolling average, Daily spend (when grouped), or Cumulative spend.
The seven-day moving average and the forecast tail are now shown only in the unggrouped daily mode, where they actually apply.
New Insights rule: App Service Plan with no hosted apps or function apps is flagged as an Orphaned Resource. The existing Unused Resource rule for App Service Plans now scopes specifically to plans whose hosted apps have recorded zero network data transfer.
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-tenant alert recipients and the Alerts & notifications card on each tenant'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 tenant, 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-tenant setting and is still managed on the tenant's Cost tracking tab.
Budgets can now be scoped to a tag key/value pair, aggregating spend across every resource carrying that tag — regardless of which tenant or subscription it lives in. The new scope is called Tag Collection.
The motivating use case is cross-tenant departmental budgeting. A team running workloads across multiple subscriptions, and possibly multiple Azure tenants, 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-tenant reach explicit.
Stricter permission rule: managing a Tag Collection budget requires either organisation owner or tenant admin on every tenant attached to the organisation. Subscription, Resource Group, and Tenant budgets continue to be manageable by an organisation owner or by a tenant admin on the relevant tenant 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 tenant, then tick multiple subscriptions, or add multiple resource groups across different subscriptions, into one cap.