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?
- AThe budget was configured at the subscription scope, which excludes resources within child resource groups from the cost calculation.
- BA CanNotDelete resource lock applied to the subscription prevents Cost Management from generating notifications.
- The budget threshold was created without associating any email addresses or Action Groups to the alert.Cevap
- DThe budget requires a separate Azure Monitor metric alert rule to route cost thresholds to the administration team.
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
Azure Cost Management Budgets and Alert Thresholds