3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations

Cost controls are not all the same

Azure administrators need to separate cost visibility from cost enforcement. Cost Management helps analyze spending. Budgets notify when actual or forecasted cost crosses thresholds. Azure Advisor recommends cost optimizations. Azure Policy can block or constrain deployments that would violate governance rules. RBAC limits who can create or change resources. A resource lock prevents accidental changes or deletion. These controls complement each other, but the exam expects you to choose the specific one that satisfies the requirement.

A budget is not a spending circuit breaker by itself. When a budget threshold is reached, Azure can send notifications and trigger action groups or automation. Existing resources do not automatically stop just because the budget reached 100 percent unless you build an automation process and accept the operational risk. In production, automatic shutdown can cause outages, so many organizations use budget alerts for notification and approval workflows rather than hard stops.

Cost governance decision tree
Need to know where money went? Cost analysis.
Need notification at 80 percent and 100 percent? Budget.
Need identify idle VMs or reserved instance opportunities? Azure Advisor.
Need block expensive SKUs or disallowed regions? Azure Policy.
Need limit who can create resources? RBAC.
Need classify cost by team? Tags.

Creating and interpreting budgets

Budgets are created in Cost Management at a supported scope such as subscription, resource group, management group, or billing scope depending on account type and permissions. The portal path is generally Cost Management + Billing > Cost Management > Budgets > Add. You choose scope, reset period, expiration, amount, thresholds, recipients, and optionally action groups.

Thresholds can be based on actual cost or forecasted cost. Actual thresholds notify after usage reaches a percentage of the budget. Forecasted thresholds notify when Azure projects that spending will cross the threshold by the end of the budget period. Forecast alerts are useful for early intervention, but they are estimates and can change as usage changes.

For CLI awareness, you may see budget operations through the az consumption or az costmanagement command groups depending on environment and API support. In real administration, the portal and automation templates are common because budget objects include notification structures. For AZ-104, the important point is the result: budget equals alerting and tracking, not automatic cost prevention.

Cost alerts versus monitoring alerts

Cost alerts are part of Cost Management and budgets. Metric alerts are part of Azure Monitor and evaluate resource metrics such as CPU percentage, storage transactions, or network throughput. Activity log alerts evaluate control-plane events such as deleting a resource group or changing a network security group. Advisor alerts can notify on new recommendations depending on configuration.

If a question says, Notify the owner when a VM CPU exceeds 90 percent, use Azure Monitor metric alerts. If it says, Notify finance when subscription spending reaches 75 percent, use a budget alert. If it says, Notify security when a delete lock is removed, use an activity log alert. If it says, Reduce cost by identifying underutilized resources, review Advisor recommendations.

Azure Advisor cost recommendations

Azure Advisor analyzes resource configuration and usage and provides recommendations across categories such as cost, security, reliability, operational excellence, and performance. Cost recommendations commonly include resizing or shutting down underutilized virtual machines, purchasing reservations or savings plans where appropriate, deleting unattached disks, removing idle public IP addresses, and improving database or App Service plan utilization.

Advisor does not make every change automatically. It gives recommendations with estimated savings and impact context. An administrator still evaluates business requirements, performance history, maintenance windows, and owner approval. For example, a VM with low CPU may still be latency-sensitive, licensed per host, or used for end-of-month processing. The right AZ-104 response is to use Advisor to identify opportunities, then apply changes through normal change control.

Scenario workflow

A department has a monthly subscription budget of $15,000. Finance wants a warning at 70 percent, an urgent notification at 90 percent, and a weekly review of savings opportunities. Create a monthly budget at the subscription scope with actual and forecasted thresholds. Add finance and operations recipients, or use an action group if integration with ITSM or automation is required. Then schedule a recurring Advisor cost review and export or document accepted recommendations.

If the same department also wants to prevent new GPU VMs in development, do not rely on the budget. Create an Azure Policy assignment that denies disallowed VM SKUs or requires approved SKUs in the development subscription or management group. If users should not create resources at all, adjust RBAC so they lack write permissions. Budgets tell you about spend; they do not replace governance.

Exam traps

Do not answer budget when the requirement is to block deployment. Do not answer Azure Policy when the requirement is only to notify at spend thresholds. Do not answer Advisor when the question asks for an alert at 80 percent of a defined monthly amount. Advisor is recommendation-driven, not a threshold budget mechanism.

Also watch scope. A resource group budget only covers that resource group. A subscription budget covers subscription spending. If the requirement spans many subscriptions under a management group, choose a scope that can see those subscriptions and confirm permissions. Cost visibility is permission-sensitive, so Reader on a resource group may not be enough to see all billing or management group cost views.