Skip to content

CHANGELOG.md

Latest commit

 

History

History
834 lines (682 loc) · 49.1 KB

CHANGELOG.md

File metadata and controls

834 lines (682 loc) · 49.1 KB
Raw

FinOps Open Cost and Usage Specification Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog.

v1.4

Announced June 2026

v1.4 adds 2 datasets (BillingPeriod, InvoiceDetail), 47 new columns, 6 new attributes, 2 new supported features, and 17 new glossary entries.

Changes to Supported Features by Change Impact Classification

Compatible Changes

Migration Compatible Changes

  • Revised ContractApplied format to use the JSON Object Schema format. Queries that parse the ContractApplied JSON structure will need to be updated to the new schema. Affecting:
  • Removal of the ColumnHandling attribute, with requirements shifted to FocusColumnHandling and CustomColumnHandling.
  • Removal of the DiscountHandling attribute, with content moved to the Discount Handling appendix entry.
  • Removal of the InvoiceHandling attribute, with requirements shifted to DeliveryHandling and DatasetCompleteness.
  • Removal of deprecated ProviderName and PublisherName columns. Use cases were migrated to ServiceProviderName, HostProviderName, InvoiceIssuerName, and DataGenerator metadata during the v1.3 cycle. See Participating Entity Identification for guidance on selecting the correct successor column.

Incompatible Changes

  • None

Added

New supported features

New datasets

New columns

New attributes

New appendix entries

New guidelines

New glossary entries

  • Glossary
    • Accrual-Based Accounting
    • Cash-Based Accounting
    • Closed Billing Period
    • Commitment Program
    • Covered Charge
    • Covering Charge
    • Custom Column
    • Delivery Scope
    • FOCUS Column
    • FOCUS Dataset Column
    • Invoice
    • Invoice Issuer
    • Invoice Reconciliation
    • Issued Invoice
    • Native Dataset
    • Open Billing Period
    • Tag Scheme

New requirements model features

  • Added applicability_criteria.json and check_functions.json to define baseline validation functions.
  • Added Schema entity type (RMId format -S-) to allow reusable JSON Schema definitions across the requirements model. See Writing Requirements Model Guidelines for authoring details.

Changed

Changed datasets

  • CostAndUsage and ContractCommitment: Column presence requirements relocated from individual column files to dataset-level requirements, now expressed in dataset-subject form (e.g., CostAndUsage MUST include ColumnId when Condition). Promotes the "Column Presence in Dataset" pattern from future-use to active, centralizing presence rules previously scattered across column files. The Normative Requirements Guidelines were updated to document the new pattern.

Changed columns

  • CostAndUsage
    • BilledCost: Expanded requirements to clarify handling of pricing adjustments, covered charges, non-invoicing entities, and introduced a Rounding Variance Tolerance for invoice matching.
    • ContractApplied: Revised format to follow new JSON Object Schema format.
    • EffectiveCost: Heavily revised requirements to detail its exact relationship with BilledCost across various charge categories, including strict rules for amortizing covering charges and cross-record sum validations.
    • InvoiceId: Changed Feature level from Recommended to Conditional.
    • PricingCurrencyEffectiveCost: Description expanded to position it as the PricingCurrency-denominated equivalent of EffectiveCost. Added a requirement that values MUST equal the PricingCurrency-denominated equivalent of EffectiveCost.

Changed attributes

  • CurrencyFormat: Requirements simplified to mandate ISO 4217:2015 three-letter codes for all currency values. Removed the prior allowance for virtual currency values to use StringHandling rules.
  • JsonObjectFormat: Removed the requirement for data generators to document JSON object schemas for custom columns. Retained other requirements.
  • NullHandling: Clarified that empty-string and placeholder-value prohibitions apply to absent-value scenarios, and split into separate rules for string and numeric columns.
  • NumericFormat: Added normative tables specifying allowed Data Types and Allowed Precisions, replacing the v1.3 pattern that delegated precision to data generator documentation.
  • StringHandling: Restructured rules for mutable versus immutable string values into an explicit set, and added new guidance on handling corrections to previously closed billing periods.
  • UnitFormat: Significantly expanded with normative rules for base units (data size, time-based, count-based), compound units, ratio units, and unit quantities. New definitions section clarifies terminology.
  • All attributes additionally refactored to a consistent structural format shared with datasets, columns, and other entities.

Changed guidelines

  • Deprecated the normative keyword "RECOMMENDED" in favor of "SHOULD" to align with BCP-14, which treats the two as synonyms. Improves terminology consistency without changing the conformance strength of existing requirements.

Changed glossary entries

  • Glossary
    • Allocated Charge: Revised definition.
    • Allocated Method: Revised definition.
    • Commitment Discount: Revised definition.
    • Contracted Unit Price: Revised definition.
    • Correction: Revised definition.
    • Dataset Instance: Revised definition.
    • Dataset Instance Artifact: Revised definition.
    • List Unit Price: Revised definition.
    • Negotiated Discount: Revised definition.
    • Origin Charge: Revised definition.
    • Service: Revised definition.
    • Term: Updated definition to apply to agreements specified on a contract or invoice.

Removed

  • ProviderName column (deprecated in v1.3, removed in v1.4)
  • PublisherName column (deprecated in v1.3, removed in v1.4)
  • ColumnHandling attribute (requirements shifted to FocusColumnHandling and CustomColumnHandling)
  • DiscountHandling attribute (content moved to the Discount Handling appendix entry)
  • InvoiceHandling attribute (requirements shifted to DeliveryHandling and DatasetCompleteness)
  • Billed Cost glossary entry
  • Effective Cost glossary entry

v1.3

Announced December 2025

⚠️ Note: Errata Available A list of non-material editorial corrections and clarifications for this release can be found in the FOCUS 1.3 Errata. Please review this document alongside the 1.3 specification.

Changes to Supported Features by Change Impact Classification

Compatible Changes

Migration Compatible Changes

Incompatible Changes

  • None

Added

New supported features

New datasets

New columns

New attributes

New appendix entries

New metadata column definition properties

New glossary entries

  • Glossary
    • Allocated Charge
    • Allocated Method
    • Contract
    • Contract Commitment
    • Dataset Artifact
    • Dataset Instance
    • Dataset Instance Artifact
    • JSON
    • Origin Charge
    • Period

New requirements model

The specification's normative requirements are now maintained in a structured, graph-based collection of rules. Version 1.2 of the requirements model is available as of this writing; 1.3 will be released during the 1.4 development cycle. This requirements model is designed to be leveraged by a conformance validator, maintained here. For more information on the requirements model, see here.

Changed

Changed datasets

  • CostAndUsage
    • FOCUS had only one dataset prior to 1.3, and thus it did not have a name. See below for a list of changed columns.
  • Datasets are now explicitly associated with attributes via normative requirements; this was previously implied.
  • Datasets now have their column set laid out in tabular format within their respective entries.

Changed columns

  • CostAndUsage
    • CommitmentDiscountQuantity
      • CommitmentDiscountQuantity MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
    • ConsumedQuantity
      • ConsumedQuantity MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
    • ContractedCost
      • ContractedCost MUST equal the product of ContractedUnitPrice and PricingQuantity when ContractedUnitPrice is not null and PricingQuantity is not null. This requirement was previously implied, but not directly stated.
    • ContractedUnitPrice
      • ContractedUnitPrice MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
      • ContractedUnitPrice MUST NOT be null when SkuPriceId is not null. This requirement was previously implied, but not directly stated.
    • InvoiceId
      • The sum of BilledCost for a given InvoiceId MUST match the sum of the payable amount provided in the corresponding invoice with the same id generated by the InvoiceIssuerName. This requirement was previously implied, but not directly stated.
    • InvoiceIssuerName
      • The display name has changed from Invoice Issuer to Invoice Issuer Name. The column ID and definition remains the same.
    • ListCost
      • Discrepancies are no longer allowed for corrections. Now, in all cases, ListCost MUST equal the product of ListUnitPrice and PricingQuantity when ListUnitPrice is not null and PricingQuantity is not null.
    • ListUnitPrice
      • ListUnitPrice MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
      • ListUnitPrice MUST NOT be null when SkuPriceId is not null. This requirement was previously implied, but not directly stated.
    • PricingCategory
      • PricingCategory MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
    • PricingCurrencyContractedUnitPrice
      • PricingCurrencyContractedUnitPrice MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
      • PricingCurrencyContractedUnitPrice MUST NOT be null when SkuPriceId is not null. This requirement was previously implied, but not directly stated.
    • PricingCurrencyListUnitPrice
      • PricingCurrencyListUnitPrice MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
      • PricingCurrencyListUnitPrice MUST NOT be null when SkuPriceId is not null. This requirement was previously implied, but not directly stated.
    • PricingQuantity
      • PricingQuantity MUST be null when SkuPriceId is null. This requirement was previously implied, but not directly stated.
      • PricingQuantity MUST be a valid decimal value when not null. This requirement was previously implied, but not directly stated.

Changed attributes

  • None

Changed appendix entries

  • Metadata examples now include use of DatasetInstanceId.
  • Participating Entity Identification replaces Origination of Cost Data.
    • The layout and functionality is the same, but the entities have been renamed, and new entries have been included.

Changed metadata

Changed metadata properties
  • None

Changed glossary entries

  • Glossary
    • Commitment has been changed to include both spend and usage, not just usage.
    • FOCUS Dataset is now more narrowly defined alongside Dataset Artifact and Dataset Instance.
    • Term is now strictly associated with agreements specified on a contract. Some legacy use of that term was associated with length of time, and that use has now been replaced by Period.

Deprecated

Deprecated columns

This functionality will be removed in a future release of FOCUS.

  • CostAndUsage
    • ProviderName
      • Due to definitional conflicts between the Provider and Publisher columns, this column is deprecated and will be removed in a future release. This column was replaced with the new ServiceProviderName column.
    • PublisherName
      • Due to definitional conflicts between the Provider and Publisher columns, this column is deprecated and will be removed in a future release.

v1.2

Announced June 2025

Added

New columns

  • BillingAccountType
  • InvoiceID
  • PricingCurrency
  • PricingCurrencyContractedUnitPrice
  • PricingCurrencyEffectiveCost
  • PricingCurrencyListUnitPrice
  • SubAccountType

New appendix entries

  • Added examples for commitment discount flexibility.
  • Added examples for SaaS scenarios.

New supported features

  • Added list of features the specification supports. See the supported_features subfolder for a full list.

New metadata column definition properties

  • Deprecated
  • PreviousColumnName

Changed

Changed columns

  • Normative requirements guidelines have been applied to all columns. While the formatting has changed significantly, the vast majority of such changes are not material unless specifically called out in the below list.
  • AvailabilityZone
    • Added a requirement that the value must be null when a charge is not specific to an availability zone.
  • BilledCost
    • Added requirement that the value must be 0 when payments are received by a third-party (e.g., marketplace).
    • Added requirement that the sum of BilledCost for an Invoice ID must match the payable amount on a corresponding invoice.
  • BillingAccountName
    • Removed requirement of uniqueness within a customer context.
  • ChargeDescription
    • Changed recommendation to specify maximum length in the Metadata Schema instead of publicly available documentation.
  • CommitmentDiscountQuantity
    • Revised requirement of value range to allow any valid decimal value.
  • CommitmentDiscountUnit
    • Revised requirement of nullability to be tied to the nullability of CommitmentDiscountQuantity (e.g., must be null when CommitmentDiscountQuantity is null).
  • ConsumedQuantity
    • Revised requirement of value range to allow any valid decimal value.
  • ConsumedUnit
    • Revised requirement of nullability to be tied to the nullability of ConsumedQuantity (e.g., must be null when ConsumedQuantity is null).
  • EffectiveCost
    • Clarified requirements for aggregation of values.
  • PricingUnit
    • Revised requirement of nullability to be tied to the nullability of PricingQuantity (e.g., must be null when PricingQuantity is null).
  • RegionName
    • Revised requirement of nullability to be tied to the nullability of RegionId (e.g., must be null when RegionId is null).
  • ResourceId
    • Revised requirement for uniqueness: the value must be unique within the provider.
  • ServiceName
    • Added requirement for mapping the value to a single ServiceCategory or "Other".
    • Added recommendation for mapping the value to a single ServiceSubcategory or "Other".
  • SkuId
    • Revised column definition to position SkuId as a stable, functional identifier beyond pricing constructs.
    • Revised requirement for presence: the value must be present when the provider supports unit pricing and publishes price lists.
    • Added requirements for a SkuId to be consistent across variations of billing accounts, contracts, and prices.
  • SkuMeter
    • Revised requirement for presence: the value must be present when the provider supports unit pricing and publishes price lists.
  • SkuPriceDetails
    • Defined a set of FOCUS-specified property names and units, and added requirements for how they are used.
    • Added requirement that custom properties must prefix names with "x_".
    • Revised requirement for presence: the value must be present when the provider supports unit pricing and publishes price lists.
  • SkuPriceId
    • Revised requirement for presence: the value must be present when the provider supports unit pricing and publishes price lists.
    • Revised requirement that the value must have a single parent SkuId, removing the prior exception for commitment discount flexibility.
    • Added requirement that the value must be associated with a given resource or service when ChargeCategory is "Usage" or "Purchase".
    • Added requirements for a SkuPriceId to be consistent across variations of billing accounts and contracts.
  • SubAccountName
    • Revised requirement of nullability to be tied to the nullability of SubAccountId (e.g., must be null when SubAccountId is null).
  • Tags
    • Resolved bug involving multiple user-defined tag structures.

Changed attributes

  • ColumnNamingAndOrdering
    • Renamed attribute to ColumnHandling.
  • CurrencyCodeFormat
    • Renamed attribute to CurrencyFormat.
    • Augmented definition to handle for virtual currencies.

Changed appendix entries

  • Revised the ordering of appendix entries.
  • Moved appendix examples to CSV section.

Changed metadata

Changed metadata properties
  • ProviderVersion
    • Renamed field to DataGeneratorVersion.

v1.1

Announced November 2024

Added:

  • CapacityReservationId column
  • CapacityReservationStatus column
  • CommitmentDiscountQuantity column
  • CommitmentDiscountUnit column
  • ServiceSubcategory column
  • SkuMeter column
  • SkuPriceDetails column
  • ProviderVersion metadata schema property

Changed:

  • CommitmentDiscountId column updates:
    • Must be globally unique within the provider.
    • Should be a fully-qualified identifier.
  • ConsumedQuantity column updates:
    • Must be null when CommitmentDiscountStatus is "Unused".
  • ConsumedUnit column updates:
    • Must be null when ChargeClass is not "Correction" and ChargeCategory is not "Usage".
    • Must be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" and CommitmentDiscountStatus is "Unused".
    • May be null when ChargeCategory is "Usage" and ChargeClass is "Correction".
  • EffectiveCost column updates:
    • When CommitmentDiscountStatus is "Unused", must be the difference between the used commitment discount amount and the portion of the total commitment discount purchase applicable for the charge period.
  • PricingCategory column updates:
    • Must not be "Committed" when the charge is for a commitment discount purchase.
  • SkuPriceId column updates:
    • SkuId can be used if the provider does not have a SkuPriceId but other requirements must be met.
  • Metadata updates:
    • Must be provided in the defined metadata schema.
    • Must be an object.
    • Must not be null.
    • Must include a reference to the schema of the data.
    • Schema reference must not be in the FOCUS dataset itself.
    • Must be an accurate and complete representation of the provided FOCUS dataset.
    • Metadata implementation should be publicly documented.
  • SchemaId metadata schema property updates:
    • Recommended to be a globally unique identifier (GUID) instead of a universally unique identifier (UUID) or SemVer version.

All 1.1 changes


v1.0

Announced June 20, 2024

Added:

New use cases:

  • Compare Billed Cost per Sub Account to budget

New attributes:

  • String handling

New columns:

  • ChargeClass
  • CommitmentDiscountStatus
  • ContractedCost
  • ContractedUnitPrice
  • RegionId
  • RegionName

New metadata properties:

  • DataGenerator

New metadata schema properties:

  • CreationDate
  • FocusVersion
  • SchemaId

New metadata column definition properties:

  • ColumnName
  • DataType
  • NumberScale
  • NumberPrecision
  • ProviderTagPrefix
  • StringEncoding
  • StringMaxLength

Changed:

  • Column naming convention attribute includes the following new provisions:
    • Column IDs should not exceed 50 characters.
    • Attribute renamed to Column naming and ordering to denote it also includes rules for column ordering.
  • ChargeCategory column updates:
    • Added "Credit" value for credits and any applicable credit corrections. See added ChargeClass column.
    • Updated "Usage", "Purchase", and "Tax" to include refunds/corrections. See added ChargeClass column.
    • Updated "Adjustment" value to exclude credits and refunds.
  • ChargeFrequency column updates:
    • Column is recommended and may not be present.
  • CommitmentDiscountCategory column updates:
    • Column is conditional and only required when the provider supports commitment discounts.
  • CommitmentDiscountId column updates:
    • Column is conditional and only required when the provider supports commitment discounts.
  • CommitmentDiscountName column updates:
    • Column is conditional and only required when the provider supports commitment discounts.
  • CommitmentDiscountType column updates:
    • Column is conditional and only required when the provider supports commitment discounts.
  • ConsumedQuantity column updates:
    • Column renamed from UsageQuantity. It is now limited to ChargeType "Usage" rows.
    • Column is conditional and only required when the provider supports the measurement of usage.
    • Column must not be null when ChargeCategory is "Usage" and ChargeClass is not "Correction".
  • ConsumedUnit column updates:
    • Column renamed from UsageUnit. It is now limited to ChargeType "Usage" rows.
    • Column is conditional and only required when the provider supports the measurement of usage.
    • Column must not be null when ChargeCategory is "Usage" and ChargeClass is not "Correction".
  • EffectiveCost column updates:
    • Clarified that effective cost does not mix or "blend" costs across multiple charges.
    • Specified that in the case of a purchase charge paid to cover future eligible charges, the Effective Cost is set to 0.
  • ListUnitPrice column updates:
    • Column is conditional and only required when the provider publishes a price list that excludes discounts.
    • Must not be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" or "Purchase".
    • Must be null when ChargeCategory is "Tax".
  • PricingCategory column updates:
    • Column is conditional and only required when the provider supports more than one pricing category value.
    • Changed "On-Demand" to "Standard".
    • Changed "Commitment-Based" to "Committed".
    • Must not be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" or "Purchase".
    • Must be null when ChargeCategory is "Tax".
  • PricingQuantity
    • Must not be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" or "Purchase".
    • Must be null when ChargeCategory is "Tax".
  • PricingUnit
    • Must not be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" or "Purchase".
    • Must be null when ChargeCategory is "Tax".
  • RegionId column updates:
    • Region column was renamed to RegionId when RegionName column was introduced
  • ResourceId column updates:
    • Column is conditional and only required when the provider supports billing based on provisioned resource instances.
  • ResourceName column updates:
    • Column is conditional and only required when the provider supports billing based on provisioned resource instances.
  • ResourceType column updates:
    • Column is conditional and only required when the provider supports billing based on provisioned resource instances and supports multiple "types" of resources.
  • SkuId column updates:
    • Column is conditional and only required when the provider publishes a SKU list.
    • Must not be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" or "Purchase".
    • Must be null when ChargeCategory is "Tax".
  • SkuPriceId column updates:
    • Column is conditional and only required when the provider publishes a SKU price list.
    • Must not be null when ChargeClass is not "Correction" and ChargeCategory is "Usage" or "Purchase".
    • Must be null when ChargeCategory is "Tax".
  • SubAccountId column updates:
    • Column is conditional and only required when the provider supports a sub account construct.
  • SubAccountName column updates:
    • Column is conditional and only required when the provider supports a sub account construct.
  • Tags column updates:
    • Column is conditional and only required when the provider supports setting user- or provider-defined tags.
    • Tag keys that cannot have a value must use a boolean true as the tag value.

Fixed:

  • CommitmentDiscountType column constraints were updated to show the column as required to align with the normative text.

Removed:

  • ChargeSubcategory column - See ChargeCategory and ChargeClass columns

All 1.0 changes


v1.0-preview

Announced November 15, 2023

Added:

  • Discount handling attribute
  • Key/value format attribute
  • Numeric format attribute
  • Unit format attribute
  • ChargeDescription column
  • ChargeFrequency column
  • ChargeSubcategory column
  • CommitmentDiscountCategory column
  • CommitmentDiscountId column
  • CommitmentDiscountName column
  • CommitmentDiscountType column
  • ListCost column
  • ListUnitPrice column
  • PricingCategory column
  • PricingQuantity column
  • PricingUnit column
  • ResourceType column
  • SkuId column
  • SkuPriceId column
  • Tags column
  • UsageQuantity column
  • UsageUnit column

Changed:

  • Column naming convention attribute includes the following new provisions:
    • Columns with a Category suffix must be normalized.
    • External, custom columns can be added but must be prefixed by x_.
    • FOCUS columns must be listed before custom columns in the dataset.
    • Added "SKU" as an exception to the "no acronyms" rule. The display name is "SKU" and column ID is Sku.
  • AmortizedCost column renamed to EffectiveCost
  • ChargeType column renamed to ChargeCategory

All 1.0-preview changes


v0.5

Announced June 24, 2023

Added:

  • Column naming convention attribute
  • Currency code format attribute
  • Date/time format attribute
  • Null handling attribute
  • AmortizedCost column
  • AvailabilityZone column
  • BilledCost column
  • BillingAccountId column
  • BillingAccountName column
  • BillingCurrency column
  • BillingPeriodEnd column
  • BillingPeriodStart column
  • ChargePeriodEnd column
  • ChargePeriodStart column
  • ChargeType column
  • InvoiceIssuerName column
  • ProviderName column
  • PublisherName column
  • Region column
  • ResourceId column
  • ResourceName column
  • ServiceCategory column
  • ServiceName column
  • SubAccountId column
  • SubAccountName column

All 0.5 changes


Columns History

This table maps the evolution of the specification, showcasing column introductions and updates from its initial version 0.5 to the comprehensive revisions in "1.0-preview", "1.0" and beyond.

Column ID Revision Introduced Status
AmortizedCost 0.5 Renamed to EffectiveCost in v1.0-preview
AvailabilityZone 0.5
BilledCost 0.5
BillingAccountId 0.5
BillingAccountName 0.5
BillingAccountType 1.2
BillingCurrency 0.5
BillingPeriodEnd 0.5
BillingPeriodStart 0.5
CapacityReservationId 1.1
CapacityReservationStatus 1.1
ChargeType 0.5 Renamed to ChargeCategory in v1.0-preview
ChargeCategory 1.0-preview Renamed from ChargeType in v1.0-preview
ChargeClass 1.0
ChargeDescription 1.0-preview
ChargeFrequency 1.0-preview
ChargePeriodEnd 0.5
ChargePeriodStart 0.5
ChargeSubcategory 1.0-preview Removed in v1.0
CommitmentDiscountCategory 1.0-preview
CommitmentDiscountId 1.0-preview
CommitmentDiscountName 1.0-preview
CommitmentDiscountStatus 1.0
CommitmentDiscountType 1.0-preview
CommitmentDiscountQuantity 1.1
CommitmentDiscountUnit 1.1
ConsumedQuantity 1.0 Renamed from UsageQuantity in v1.0
ConsumedUnit 1.0 Renamed from UsageUnit in v1.0
ContractedCost 1.0
ContractedUnitPrice 1.0
EffectiveCost 1.0-preview Renamed from AmortizedCost in v1.0-preview
InvoiceId 1.2
InvoiceIssuerName 0.5
ListCost 1.0-preview
ListUnitPrice 1.0-preview
PricingCategory 1.0-preview
PricingCurrency 1.2
PricingCurrencyContractedUnitPrice 1.2
PricingCurrencyEffectiveCost 1.2
PricingCurrencyListUnitPrice 1.2
PricingQuantity 1.0-preview
PricingUnit 1.0-preview
ProviderName 0.5
PublisherName 0.5
Region 0.5 Renamed to RegionId in v1.0
RegionId 1.0 Renamed from Region in v1.0
RegionName 1.0
ResourceId 0.5
ResourceName 0.5
ResourceType 1.0-preview
ServiceCategory 0.5
ServiceName 0.5
ServiceSubcategory 1.1
SkuId 1.0-preview
SkuMeter 1.1
SkuPriceDetails 1.1
SkuPriceId 1.0-preview
SubAccountId 0.5
SubAccountName 0.5
SubAccountType 1.2
Tags 1.0-preview
UsageQuantity 1.0-preview Renamed to ConsumedQuantity in v1.0
UsageUnit 1.0-preview Renamed to ConsumedUnit in v1.0