Question

Difficulty: MediumAzure Subscription Management and Cost Control

An administrator manages an Azure subscription named sub-engineering-prod. The subscription contains a resource group named rg-core-databases. To control costs, the administrator configures a monthly budget at the subscription scope. The budget includes a threshold alert set to trigger when actual spending reaches 90% of the budgeted amount. During the billing cycle, the spending exceeds the threshold, but no email notifications are sent to the administration team. You need to identify the reason why the notifications were not sent. Which of the following is the most likely cause of this issue?

  1. A
    The budget was configured at the subscription scope, which excludes resources within child resource groups from the cost calculation.
  2. B
    A CanNotDelete resource lock applied to the subscription prevents Cost Management from generating notifications.
  3. The budget threshold was created without associating any email addresses or Action Groups to the alert.Answer
  4. D
    The budget requires a separate Azure Monitor metric alert rule to route cost thresholds to the administration team.

Answer

The budget threshold was created without associating any email addresses or Action Groups to the alert.
The correct answer is correct because Azure Cost Management budgets require explicit configuration of email recipients or Action Groups for each threshold alert. If these are not specified, the alert triggers internally when the threshold is met but cannot deliver any notifications to administrators.

Step-by-Step Solution

1
Analyze the configuration of Azure Cost Management budgets and alert thresholds.
Identify that a budget threshold was set to 90% but notifications were not received.
To determine why the alert was silent despite the costs exceeding the threshold.
2
Evaluate the role of resource locks and scopes on Cost Management alerts.
Determine that the subscription scope includes child resource groups and that a CanNotDelete lock does not block notifications.
To rule out scope configuration and resource locks as the cause of the missing alerts.
3
Verify the notification settings configured on the budget threshold.
Establish that email recipients or Action Groups must be explicitly defined under the budget's alert threshold conditions.
To identify the root cause of the silent budget alert.

Key Concept

Azure Cost Management Budgets and Alert Thresholds
Rate this question