Operations Reports
Three reports on what changed across the estate, who changed it, and where waste is hiding. All three use every filter dimension; Filters, Subscribe, CSV, PDF and default views work as described in Using Reports.
Prerequisites
- The View Resources permission and at least one completed scan.
- Log Analytics Usage needs a scan that collected workspace usage. Its savings figure needs the Log Analytics sizing recommendations.
Infrastructure Change
Every create, modify and delete across your subscriptions, attributed to a named actor, with change velocity and security-relevant activity surfaced.
Controls: Window (7d, 30d by default, 60d, 90d), Filters.
- Deletions
- Destructive changes. Red when a security resource was removed.
- Security-relevant
- Changes to security resource types, with a link to Security Change Log.
- Change velocity
- Changes per day for 7d and 30d windows, per week for 60d and 90d.
- Where changes landed
- Top 12 subscriptions and busiest resource groups.
- By resource type
- Top 25 types. Security types carry a shield icon.
- Who's changing things
- The Person / Automation / System split, and the top 15 actors.
- The window covers N UTC calendar days including today.
- Actor kind: Person is a user; Automation is an application or managed identity; System is Azure itself or an unrecognized client. The split is a rough indicator of how much change goes through pipelines vs by hand.
- A change is attributed when the change record or a matching activity-log operation names an actor. Placeholder names don't count; unattributed rows show as "Unknown" or "Azure system", and actors known only by ID show as "Unresolved identity" with the last 6 characters.
- Changes to a subscription or resource group itself are included under a scope filter, and excluded once a tag, type or location filter is active.
- Change history comes from Azure Resource Graph, which keeps about 14 days at the source; StratoLens keeps it from then on. Entra ID directory changes aren't collected.
CSV columns: One row per actor (top 15): Actor, Actor kind, Created, Modified, Deleted, Total changes, Security-relevant changes.
Orphans & Waste
Orphaned and idle resources from your latest scan, rolled up by type, subscription and age so you know what to clean up first. It uses the same recommendations as the Orphaned Resources workbench, minus any you hid there. StratoLens flags resources for review and never deletes anything; use Open the Orphaned Resources workbench to hide, restore or work a resource.
Controls: Filters, and the Orphan population toggle: Wastage (costing money, the default) or Orphaned (no direct cost). If nothing costs money, it opens on Orphaned. With more than one subscription, a dropdown on the table narrows it.
- Monthly wastage
- Monthly cost of orphaned resources that cost money. Annualized wastage is monthly × 12.
- Idle 90+ days
- Resources orphaned 90 days or more.
- How long it has stood
- Age bands: under 30 days, 30 to 89, 90 to 179, and 180+ days.
- What to clean up first
- Up to 100 rows. Wastage is sorted by monthly cost, Orphaned by age.
- Projected cost is the resource's rolling 30-day average spend.
- Some orphans, such as empty resource groups, unattached NSGs and idle DNS zones, cost nothing directly. They count under Orphaned and add $0.
- Resources detected by metrics (idle gateways, Bastion, NAT and similar) appear only after 30 days with no activity. Resources detected from inventory, such as an unattached disk or public IP, always appear.
- An age shown as "At least" means the true start is earlier than StratoLens can see.
- The printout includes both populations in full.
CSV columns: Both populations: Population, Resource, Type, Status, Reason, Age (days), Orphaned since, Age is minimum, Monthly cost, Annual cost, Currency, Subscription, Resource group.
Log Analytics Usage
Billable ingestion by workspace and table over the last 31 days, with pricing tier, retention and savings.
Controls: Filters. The window is fixed at 31 days.
- Observed monthly cost
- Log Analytics and Azure Monitor meters, in your billing currency. Excludes Sentinel and Defender charges.
- Savings available
- From Log Analytics sizing, at USD list price. Never added to observed cost. Click to open Sizing.
- Idle workspaces
- No ingestion in 31 days and older than 31 days. Click to open Orphaned Resources. This rule is stricter, so the count can be lower than the Orphaned Resources list.
- Legacy tiers
- Workspaces on Free, Standalone, Per Node, Standard or Premium.
- Workspaces table
- Tier, retention, daily and 31-day GB, observed cost, savings and flags, up to 200 workspaces. Click a name for workspace details.
- Top tables across the estate
- Top 25 tables with GB, estimated monthly cost and plan.
- Leftover restored / search tables
- Restored and search-result tables that keep billing until deleted. Only shown when present.
Flags and badges
- Query failed
- StratoLens couldn't query the workspace's usage in the last scan. The row shows its last good data, or "Never queried".
- Above {n} included
- Retention is longer than the included days.
- Basic-eligible
- The table can move to the cheaper Basic plan.
- Usage is billable GB from each workspace's Usage table over the last 31 full days, as stored by the latest scan. The report doesn't query Log Analytics itself.
- Estimated table cost splits each plan's observed ingestion cost by table GB. Tables on Sentinel workspaces show as billed with Sentinel; Analytics tables on a dedicated cluster show as billed on cluster.
- A workspace created inside the window is averaged over the days it existed.
- Per-resource attribution isn't collected.
Find the expensive tables
Expand a workspace row to see the 5 tables that drive its cost.
CSV columns: Two blocks. Workspaces: Workspace, Subscription, Resource group, Location, Pricing tier, Retention (days), Sentinel, Avg GB/day, Avg over (days), Billable GB (31d), Observed monthly cost, Savings available (USD/month), Idle, Query status, Top table. Then Top tables: Workspace, Table, Billable GB (31d), Est. monthly cost, Cost note, Plan, Basic-eligible.
Troubleshooting
Infrastructure Change shows No changes recorded
Answer
Nothing changed in the window, or history is short. Try a wider window. Azure Resource Graph keeps about two weeks of change history at the source.
Orphans & Waste count differs from the Orphaned Resources page
Answer
This report always uses a 30-day idle rule for metrics-detected resources, the workbench's default Metrics Timeframe. If you picked a different timeframe in the workbench, the counts differ.
Orphans & Waste is empty
Answer
Your latest scan found no orphaned or idle resources, or every recommendation has been hidden in the workbench.
Log Analytics Usage says no workspaces found
Answer
There are no workspaces in scope, or the latest scan hasn't collected workspace usage yet. Run a scan and check again.