Costs, monitoring, and deployment | AZ-900: Azure fundamentals through practical decisions

Understand the concept

Azure Monitor provides observation capabilities including metrics, logs, and alerts; Application Insights helps understand applications. Service Health provides information about relevant Azure service issues and notices. Advisor offers recommendations, but recommendations require assessment before production changes. A dashboard does not replace a functional operation demonstrating recovery.

Apply and decide

Cost Management helps analyze spending; a budget can issue alerts without stopping resources. Tags help allocate costs when consistently defined and used. IaC and templates make deployment repeatable but need review, appropriate identity, and state validation. Azure Arc extends management capabilities to supported resources outside Azure; it does not automatically turn all infrastructure into an Azure region.

Workplace application

During an incident, correlate Service Health with application signals; a cost recommendation does not prove operational health. For low-use resources, confirm recovery or peak roles before reducing capacity. Associate budget alerts with owners and defined responses. When applying IaC, review changes and observe results within controlled scope: repeatability increases efficiency but may also propagate the same error.

IN PRACTICE

A recommendation suggests downsizing an idle recovery VM. Confirm its recovery role before acting: low utilization may be intentional.

Common pitfalls

Applying recommendations without context or treating alerts as absolute usage limits.

Related topics: Cloud models and responsibilities · Resource organization and resilience

Take this idea with you

Recommendations and alerts inform decisions; they do not remove operational accountability.

Create account

Reference: Azure Service Health overview · AZ-900 skills measured July 20, 2026