Advanced forecasting by application

Organizations with mature FinOps practices want to push the forecasting even further to forecast by application. The idea is that each Engineering team or business unit has a dashboard where they can track the charges incurred by their application. This provides granular visibility to the IT teams and provides an opportunity to track their own spending.

Identifying usage charges by application

One way of mapping service charges back to the application is using tags. If your organization is following tagging policy and each resource is tagged, then you can use the Tags field in the Usage Data table. In our case, the organization does not have sufficient tags in place for historic data and wanted an alternative solution. In that case, the solution is to create a table in Power BI or SQL Database that maps Subscription ID to Application Name. This can also be easily changed to map resource groups or individual service names to the application...