Azure Resource Group
Does ZopNight manage Azure Resource Group?
Azure resource groups carry a charge of 0 (the container is free), but they are the unit ZopNight uses to roll up cost, tags, and schedule coverage. Connections can be scoped to named groups via azureResourceGroups, and Databricks-managed groups are recognized so managed worker VMs are handled correctly.
Rules that fire on Azure Resource Group
No active rule family targets Azure Resource Group today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | grouping and roll-up only; member resources are scheduled individually or via resource groups in the scheduling UI. |
Resource groups are the deployment and lifecycle containers for Azure resources. They are free, but they are the natural unit for environment identification, tagging, and bulk scheduling decisions.
A free container that shapes the whole bill
A resource group itself never appears as a charge; the meter reads zero. Its financial weight is indirect: because every Azure resource lives in exactly one group, the group boundary is where environments become legible. A well-named group tells you at a glance that its contents are a staging environment safe to schedule off at night; a grab-bag group named after a person who left makes every cost decision inside it slower. The container is free, but ambiguity in it is expensive.
Roll-ups ZopNight computes at the group level
Derived during discovery as the organizing parent for every discovered resource. ZopNight rolls up cost, tags, and schedule coverage per resource group, and connections can be scoped to specific resource groups via azureResourceGroups, useful when a platform team wants ZopNight to see only the non-production groups. Scheduling itself stays at the member level: the group is not stopped as an object, but the scheduling UI can act on a group’s members as a set, so the roll-up is how a team finds the group where 12 VMs run all weekend for nobody.
Group patterns that hide waste
Mixed-environment groups defeat every bulk action, because production and staging share one blast radius. Leftover groups from deleted projects keep billing through the resources still inside them, invisible precisely because nobody opens the group anymore. And empty groups cost nothing but pollute inventory, drowning the groups that matter.
The managed groups that get special handling
Databricks-managed groups (databricks-rg-*) are recognized so managed worker VMs are handled correctly. Their contents belong to the workspace’s lifecycle, not to individual VM schedules.
Browsing groups and their contents
Azure portal → Resource groups lists every group in the subscription; opening one shows its resources, tags, and a per-group cost analysis view, the same slice ZopNight’s roll-up automates across all of them.