Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs-mslearn/toolkit/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: FinOps toolkit changelog
description: Review the latest features and enhancements in the FinOps toolkit, including updates to FinOps hubs, Power BI reports, and more.
author: MSBrett
ms.author: brettwil
ms.date: 08/22/2026
ms.date: 09/01/2026
ms.topic: reference
ms.service: finops
ms.subservice: finops-toolkit
Expand Down Expand Up @@ -33,6 +33,7 @@ The following section lists features and enhancements that are currently in deve
- Clarified that the FinOps toolkit exclusively manages the FinOps hub virtual network and documented customer-managed private endpoints as the preferred private-access topology, with virtual network peering as a secondary option ([#2156](https://github.com/microsoft/finops-toolkit/issues/2156)).
- Replaced redundant `tolower()` comparisons in hub KQL with case-insensitive operators (`has`, `=~`, `!~`) so the engine can use the term index instead of scanning every row ([#2213](https://github.com/microsoft/finops-toolkit/issues/2213)).
- Replaced whole-term `contains` matches with `has` across hub KQL and the query catalog (resource ID paths, licensing phrases, SKU description terms) and added a per-row operator-equivalence regression harness with unit test coverage ([#2220](https://github.com/microsoft/finops-toolkit/pull/2220)).
- Updated the hub cost estimate note to reflect real-world Azure Data Explorer and Microsoft Fabric pricing and called out that Data Explorer cost varies significantly by region; the previous flat estimate understated actual cost for some regions and SKUs ([#2229](https://github.com/microsoft/finops-toolkit/issues/2229)).
- **Fixed**
- Fixed private-network deployments that Azure Policy blocked when `defaultOutboundAccess` was omitted. Private mode subnets now set it to `false`, while an Azure Files private endpoint supports deployment-script storage and the NAT Gateway provides required container egress ([#2258](https://github.com/microsoft/finops-toolkit/issues/2258), [#2259](https://github.com/microsoft/finops-toolkit/pull/2259)).
- Fixed the `ContractedCost` recompute guard to compare with a null-safe tolerance instead of exact float equality, eliminating millions of no-op rewrites that polluted the `x_SourceValues` audit trail while preserving the null-cost backfill and no longer overwriting an existing cost when the unit price is missing ([#2216](https://github.com/microsoft/finops-toolkit/issues/2216)).
Expand Down
6 changes: 3 additions & 3 deletions docs-mslearn/toolkit/hubs/finops-hubs-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: FinOps hubs overview
description: FinOps hubs provide a reliable platform for cost analytics, insights, and optimization, supporting large accounts and organizations.
author: flanakin
ms.author: micflan
ms.date: 08/13/2026
ms.date: 09/01/2026
ms.topic: concept-article
ms.service: finops
ms.subservice: finops-toolkit
Expand All @@ -25,9 +25,9 @@ FinOps hubs extend Cost Management to provide a scalable platform for advanced d

<!-- prettier-ignore-start -->
> [!NOTE]
> Estimated cost: Starts at $120/mo + $10/mo per $1M in cost being monitored.
> Estimated cost: Starts at $160/mo + $10/mo per $1M in cost being monitored.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the per-$1M figure is being revised (see the note on line 30 β€” the body now says $15 without Data Explorer while this line and the next still say $10), this headline needs to move in step. Right now a reader gets $10 here, $10 in the first half of the note, and $15 in the second half.

>
> Estimated monthly cost includes $120 for a single-node Azure Data Explorer cluster or $300 for F2 Fabric capacity, plus $10 in Azure storage and processing cost per $1M being monitored. Exact cost will vary based on discounts, data size (we estimate ~20GB per $1M), and Fabric or Power BI license requirements. Cost without Data Explorer or Fabric is $5 per $1M. For details, refer to the [FinOps hub cost estimate](https://aka.ms/finops/hubs/calculator) in the Azure Pricing Calculator.
> Estimated monthly cost includes $160+ for a single-node Azure Data Explorer cluster or $310 for F2 Fabric capacity, plus $10 in Azure storage and processing cost per $1M being monitored. Exact cost will vary based on discounts, region, data size, and Fabric or Power BI license requirements. Cost without Data Explorer or Fabric is $15 per $1M. For details, refer to the [FinOps hub cost estimate](https://aka.ms/finops/hubs/calculator) in the Azure Pricing Calculator.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two numbers can't both be right:

...plus $10 in Azure storage and processing cost per $1M being monitored. ... Cost without Data Explorer or Fabric is $15 per $1M.

The old pairing ($10 with Data Explorer, $5 without) was coherent β€” drop ADX, drop the ingestion-side cost. The new pairing has the no-ADX deployment costing more per $1M than the ADX deployment's incremental, which inverts that. One of the two has been updated and the other hasn't.

If $15 is the corrected storage + Data Factory figure, then the $10 here and in the headline on line 28 both need to move with it. Worth double-checking the number itself too β€” it's a 3-5x jump from the ~$3-5 per $1M quoted in help-me-choose.md:52.

Nit: dropping "(we estimate ~20GB per $1M)" removes the only handle a reader has for sanity-checking against their own data volume. Could it stay alongside the new "region" caveat rather than being swapped out for it?

<!-- prettier-ignore-end -->

<br>
Expand Down