Your finance team wants tighter control over monthly Azure spend and better purchase planning. Requirements: 1) Trigger email to on-call and a webhook to an automation endpoint when 80% of the monthly budget is reached. 2) Provide the CFO a daily breakdown of costs grouped by resource group and by the 'CostCenter' tag. 3) After observing 30 days of usage, obtain recommendations for VM reservations. What should you do?

The correct option directly addresses all three requirements using appropriate Azure services. Azure Cost Management budgets with action groups fulfill the 80% spend alert with email and webhook. Cost Analysis views and scheduled exports to storage, combined with a Logic App, provide the daily, grouped cost breakdown for the CFO. Cost Management's built-in reservation recommendations are the standard way to identify VM reservation opportunities after observing usage. Incorrect options: Spending caps are not suitable for alerts or planning. Azure Policy is for governance, not daily cost summaries by tag. Anomaly alerts are not a daily breakdown. Purchasing reservations without review is risky. Polling the Consumption API hourly for forecasted cost is inefficient and doesn't meet the actual cost requirement. Power BI is a reporting tool, but the solution requires a scheduled export. Azure Migrate is for migration assessment, not reservation planning.