Enhancements for Integration of FinOps Toolkit with Existing Tools (Alescent FinOps ADX Solution)

⚠️ Problem

We are exploring the integration of Microsoft FinOps Toolkit into our existing tools as an ingestion and data layer. However, several features and enhancements are needed to make this integration feasible and effective. These changes are required to align the toolkit’s capabilities with our operational practices and infrastructure requirements.

🛠️ Solution

To achieve seamless integration, we propose the following enhancements and modifications:

1.1. ✅ Avoid Deploying Network Resources

• Provide an option to configure the toolkit without deploying any network resources.

1.2. ✅ Improved Cost Export Functionality

• The New-FinOpsCostExport cmdlets must function as intended.
• Ideally, provide the capability to create these exports using Bicep templates for better automation.
• Reference: [Issue #1193](https://github.com/microsoft/finops-toolkit/issues/1193).

1.3. ✅ Support for Reals Instead of Decimals

• Data operations and calculations should use real numbers instead of decimals for query efficiency and storage reasons, see https://learn.microsoft.com/en-us/kusto/query/scalar-data-types/decimal?view=azure-data-explorer.

2.1. Pre-Aggregated Monthly View

• Introduce a pre-aggregated view with monthly granularity, such as a Materialized View, in addition to the existing Costs() function.

2.2. Extended Time Horizon

• The toolkit should support a larger default time horizon that encompasses at least an entire MACC (Microsoft Azure Consumption Commitment) period.

3.1. ✅ Fabric Integration

• Enable integration with Microsoft Fabric to streamline data processes (nice to have).

Start with the existing Costs() function and New-FinOpsCostExport cmdlets, then review related Issue #1193. Break the request into the listed network, export, numeric type, monthly aggregation, time horizon, and Fabric integration areas; done requires an agreed scope and validation for each enhancement.