LEARN. PRACTICE. GROW.Concept and mechanism
Management groups organize subscriptions and apply governance through inheritance. Resource groups should reflect responsibilities and lifecycles; resources surviving a pilot should not be deleted by an unintended joint operation. Tags help allocate costs but are not automatically inherited by every resource. Define application through IaC or suitable Policy and handling of existing state. A budget produces financial signals, not an automatic billing cap or permission to stop a critical service.
Guided application
For monitoring, start with decisions RUN needs to make. Identify log sources, categories, destination, retention, and access. An empty workspace does not prove collection. If documented residency boundaries exist, design compatible destinations and make distributed query and operating costs explicit. Validate a realistic event’s path from source to alert and accountable owner.
Two units require storage in distinct regions. Separate dashboards in one workspace do not change data location.
Common pitfalls
Treating tags as a security boundary; ownerless alerts; accepting dashboards without demonstrating collection and diagnosis.
Related topics: Relational data decisions · Storage and data integration
Each control needs a requirement, an owner, and evidence of its effect.
Reference: Resource organization · AZ-305 objectives 2026-04-17