Question 200
A company must open a ticket whenever an Azure subscription budget crosses an actual-cost threshold. A manual email is insufficient. What integration should be evaluated?
Explanation
Correct Answer
Cost Management budgets can integrate with Azure Monitor action groups for supported automated notifications and actions. Configure the actual-spend threshold, select the action group, and connect its supported mechanism, such as a webhook or Logic App, to the ticketing system. Verify permissions and payload handling in the workflow. The budget still detects cost thresholds rather than performing ticket creation itself; the action group and integration supply the missing automated response.
Incorrect Answers
Autoscale rules react to supported performance or schedule signals for a particular scalable resource, not the aggregated subscription budget event described here. Increasing or reducing VM instances is a different operational response from filing a ticket. Configure budget notification with an action group that invokes the ticket workflow.
A policy deny effect evaluates resource requests against policy rules, not the Cost Management budget threshold event. It cannot replace the budget's spend comparison and ticket integration. Such a policy could also block unrelated deployments without generating the desired incident record. Use the budget notification workflow to create tickets.
An annual CSV export is too infrequent to act when a monthly cost threshold is crossed. A report also requires another process to detect and dispatch the event, defeating the requested automated notification. Budget thresholds and a supported action group provide the event-driven mechanism.