You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add FOCUS 1.3 (ratified December 2025) and FOCUS 1.4 (working draft, targeting June 2026) support across the FinOps toolkit. Implementation follows the hub schema versioning procedure, which couples each new FOCUS minor version to a new hub schema version (v1_3, v1_4).
Child issue #2104 captured the original 1.3 request and remains the source of context for the Contract Commitment dataset and ContractApplied column. This issue extends that to also cover 1.4 and tracks the full delivery plan.
Out of scope: regenerating the FOCUS conformance reports, updating Cost Management export schemas, and updating FocusCost_*.json open-data metadata. Those activities run only against official Microsoft Cost Management FOCUS releases, not as part of adding hub support.
Summary
Add FOCUS 1.3 (ratified December 2025) and FOCUS 1.4 (working draft, targeting June 2026) support across the FinOps toolkit. Implementation follows the hub schema versioning procedure, which couples each new FOCUS minor version to a new hub schema version (
v1_3,v1_4).Child issue #2104 captured the original 1.3 request and remains the source of context for the Contract Commitment dataset and
ContractAppliedcolumn. This issue extends that to also cover 1.4 and tracks the full delivery plan.Plugin updates are tracked separately in #2119.
Out of scope: regenerating the FOCUS conformance reports, updating Cost Management export schemas, and updating
FocusCost_*.jsonopen-data metadata. Those activities run only against official Microsoft Cost Management FOCUS releases, not as part of adding hub support.Branch strategy
flanakin/focus14(offorigin/dev).flanakin/focus14, reviewed via PR back intoflanakin/focus14. Final merge offlanakin/focus14intodev.Scope summary
FOCUS 1.2 → 1.3 (compatible)
AllocatedMethodId,AllocatedMethodDetails,AllocatedResourceId,AllocatedResourceName,AllocatedTags,ContractApplied,ServiceProviderName,HostProviderNameProviderNameandPublisherName(still present in 1.3)FOCUS 1.3 → 1.4 (incompatible — working draft)
ProviderNameandPublisherNamePlan / checklist
Scoping (complete)
Implementation phases
IngestionSetup_v1_3.kql+Costs_rawextension for FOCUS 1.3 columns. (FOCUS 1.4 phase 1: add FOCUS 1.3 ingestion (IngestionSetup_v1_3.kql) #2124, PR Add FOCUS 1.3 ingestion (IngestionSetup_v1_3.kql) #2126)HubSetup_v1_3.kqland Latest aliases retargeted to v1_3. (FOCUS 1.4 phase 2: add FOCUS 1.3 hub functions (HubSetup_v1_3.kql) #2127, PR Add FOCUS 1.3 hub functions (HubSetup_v1_3.kql) #2128)ContractCommitmentdataset end-to-end (raw, transform, final, hub function, Latest alias). (FOCUS 1.4 phase 3: add ContractCommitment dataset #2129, PR Add ContractCommitment dataset #2130)IngestionSetup_v1_4.kql(preview): drops ProviderName/PublisherName from Costs, expands ContractCommitment by 14 columns. (FOCUS 1.4 phase 4: add FOCUS 1.4-preview ingestion #2131, PR Add FOCUS 1.4-preview ingestion (IngestionSetup_v1_4.kql) #2132)HubSetup_v1_4.kql(preview); Latest aliases stay pinned to v1_3 GA. (FOCUS 1.4 phase 5: add FOCUS 1.4-preview hub functions #2133, PR Add FOCUS 1.4-preview hub functions (HubSetup_v1_4.kql) #2134)Removed from scope
Phase 1 (originally): multi-version conformance tooling— closed as FOCUS 1.4 phase 1: extend Build-FocusConformance for multi-version + hubs report #2122. Conformance reports are generated only against official Microsoft Cost Management FOCUS releases.Cost Management export schema updates— same reason.Open-data— these files describe Cost Management exports (DataGenerator: Microsoft) and are therefore out of scope.FocusCost_*.jsonmetadataReferences