feat(ptn): Update FinOps Hub v12 pattern module#6549
Open
FallenHoot wants to merge 1 commit intoAzure:mainfrom
Open
feat(ptn): Update FinOps Hub v12 pattern module#6549FallenHoot wants to merge 1 commit intoAzure:mainfrom
FallenHoot wants to merge 1 commit intoAzure:mainfrom
Conversation
avm-organizer
bot
added
the
Needs: Module Owner 📣
microsoft-github-policy-service
bot
added
Needs: Triage 🔍
FallenHoot
force-pushed
the
feature/finops-hub-avm-module
branch
from
f68750c to
5720da9
Compare
…ps-hub) This module deploys a FinOps Hub — a data platform for FinOps that normalizes multi-cloud cost data into the FOCUS specification using Azure Data Explorer, Data Factory, and optional Microsoft Fabric integration. Key capabilities: - Three deployment modes: Storage-only, ADX (recommended), and Fabric - Multi-cloud support: Azure, AWS, GCP, and on-premises/datacenter costs - FOCUS 1.0-1.3 normalization with open data enrichment - Interactive ADX dashboard with 22 pages (19 standard + 3 experimental) - WAF-aligned options: managed VNET, private endpoints, CMK encryption - Managed exports pipeline for automated Cost Management data ingestion Architecture decisions documented in ADR.md (ADR-001 through ADR-015) covering: - AVM compliance, resource naming, region selection, identity management - ADF pipeline approach for ADX managed identity policy (ADR-015) - ADX principal assignment identity format fix (ADR-014) Test scenarios: adx-minimal, adx-waf-aligned, adx-managed-network, fabric-minimal, fabric-waf-aligned, storage-minimal, managed-network Includes operational scripts for deployment, test data generation, ADX SKU selection, and hub state management.
FallenHoot
force-pushed
the
feature/finops-hub-avm-module
branch
3 times, most recently
from
3bf4817 to
f7896a9
Compare
FallenHoot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds the FinOps Hub pattern module to Azure Verified Modules (AVM). FinOps Hub is a comprehensive cost management and optimization solution that ingests, normalizes, and analyzes cloud cost data from multiple providers.
CI Status (Fork)
Features
Module Details
avm/ptn/finops-toolkit/finops-hub46d3xbcp.ptn.finopstoolkit-finopshubAVM Compliance
lockanddiagnosticSettingsstandard interfacesavm/utl/types/avm-common-types:0.6.1enableTelemetryparameterTest Scenarios
All 7 e2e test scenarios are enabled and passing:
ADX Managed Identity Policy — Implementation Note
The ADX cluster requires a
managed_identitypolicy for native ingestion via Azure Data Factory. We explored several approaches to automate this:scriptLevel: 'Cluster'— Works in CI but the database script resource has limitations with cluster-level KQL commands in some edge cases.Current approach: The ADX managed identity policy is set via an ADF pipeline activity (
Set Ingestion Policy) that runs as part of theingestion_ETL_dataExplorerpipeline. This mirrors the upstream FinOps Toolkit pattern where ADF manages ADX configuration as part of the data pipeline, rather than during ARM deployment.We've engaged the ADX Product Group for guidance on a cleaner Bicep-native approach (e.g., a dedicated ARM resource type for MI policy). In the meantime, the ADF-based approach is reliable and production-tested.
Related
Checklist