azure-cost-governance

Azure cost analysis across multiple subscriptions is handled by querying the Microsoft.CostManagement and Consumption REST APIs to retrieve spend data and identify underutilized resources. This approach enables cost queries, budgeting, and policy-driven savings recommendations across your tenant.

Yes, you can forecast future Azure spend and set budgets using the Azure Cost Management and Consumption REST APIs. The skill projects future costs and monitors spend against predefined plans to ensure budget adherence across multi-subscription environments.

You need canonical context such as your tenantId and subscriptionId to query Azure cost data for FinOps. Providing these identifiers allows the deterministic routing via shared workflow specs to access the Microsoft.CostManagement REST endpoints successfully.

The best way to generate cost optimization recommendations is by applying policy-driven analysis to your Azure Cost Management data. This method surfaces risk-ranked actions and rollback notes, identifying top spenders and idle resources for potential savings.

Azure cost governance requires canonical context like tenantId and subscriptionId for deterministic routing, meaning you must explicitly provide these identifiers. Without proper configuration of the Microsoft.CostManagement and Consumption REST endpoints, multi-subscription budgeting and forecasting will not execute.