Configure and migrate FOCUS 1.2 data

FOCUS 1.2 expands the standardized cloud cost and billing information that technology providers can make available for FinOps analysis.

Yarken supports data ingestion using both FOCUS 1.0 and FOCUS 1.2. Existing integrations using FOCUS 1.0 can continue to load data into Yarken and do not need to migrate to FOCUS 1.2.

If FOCUS 1.2 is available from your cloud provider, you can use it to take advantage of additional supported fields for invoice reconciliation, pricing currency, pricing information, and account classification.

Use this page to:

• Understand what's new in FOCUS 1.2

• Check whether your cloud provider supports FOCUS 1.2

• Configure a new FOCUS 1.2 export

• Understand the additional FOCUS 1.2 fields supported by Yarken

• Optionally migrate an existing FOCUS 1.0 export to FOCUS 1.2

• Validate FOCUS 1.2 data before using it for production reporting

What's new in FOCUS 1.2

FOCUS 1.2 expands the standardized cost and usage data that technology providers can make available.

Key additions include:

• Invoice reconciliation — InvoiceId and related invoice information provide a standardized way to associate cost and usage records with invoices.

• Pricing currency — New pricing-currency fields support reporting of effective, contracted, and list pricing in the applicable pricing currency.

• Account classification — BillingAccountType and SubAccountType provide additional context about provider billing account structures.

• Capacity reservations — New fields can describe capacity reservations and whether reserved capacity is used or unused.

• Commitment information — Additional fields provide information about commitment quantities and units.

• Service and SKU detail — Additional service and SKU fields provide more detailed classification and pricing information.

Before you start

Before configuring FOCUS 1.2 or migrating an existing FOCUS 1.0 integration:

1. Identify the cloud provider and billing accounts that will supply cost and usage data to Yarken.

2. Check which FOCUS versions your provider supports for the required billing scope.

3. Decide whether FOCUS 1.0 or FOCUS 1.2 best meets your reporting requirements.

4. If you choose FOCUS 1.2, review any provider-specific requirements and schema differences.

5. If migrating an existing integration, identify Yarken mappings, Analytics views, allocation rules, Chargeback definitions, or other processes that depend on the existing FOCUS 1.0 data.

6. Plan to validate the FOCUS 1.2 dataset before replacing an existing export.

Check which FOCUS version your provider supports

FOCUS defines a common specification, but each technology provider determines which FOCUS versions and fields it makes available.

To check your provider:

1. Open the provider's billing or cost-management documentation.

2. Find its FOCUS cost and usage export documentation.

3. Check the FOCUS version available when creating an export.

4. Check whether the version is generally available or in preview.

5. Review the provider's schema or conformance information.

6. Confirm that the fields required for your reporting are populated.

See External resources for the FOCUS, AWS, and Microsoft documentation.

FOCUS 1.2 fields supported by Yarken

Yarken supports mapping selected additional FOCUS 1.2 fields during data ingestion.

The following fields are currently supported:

Configure AWS FOCUS 1.2 data

AWS provides FOCUS 1.2 cost and usage data through AWS Data Exports.

When creating the export, select the FOCUS 1.2 dataset available for your billing environment. AWS refers to this dataset as FOCUS 1.2 with AWS columns.

If you already use AWS FOCUS 1.0

AWS FOCUS 1.2 contains schema and behavioral differences from FOCUS 1.0. Depending on the data you currently use, these can include:

• New FOCUS columns

• Removal or replacement of some AWS extension columns

• Changes to some field values

• Changes to null handling

• Different representation of some AWS-specific information

• Additional rows for some capacity-reservation scenarios

AWS validation considerations

When comparing AWS FOCUS 1.0 and FOCUS 1.2 data:

• Do not expect record counts to be identical.

• Compare financial totals rather than relying only on row counts.

• Check fields used by existing allocation and reporting logic.

• Review tags and other AWS-specific fields used for ownership or classification.

• Validate billing periods and account structures.

• Confirm that downstream Yarken reporting produces the expected results.

Configure Microsoft Azure FOCUS 1.2 data

Microsoft provides FOCUS cost and usage data through Azure Cost Management exports.

When configuring an export, check the FOCUS dataset versions currently available for your Azure billing scope.

Before enabling or migrating an Azure export:

1. Check Microsoft's current FOCUS schema documentation.

2. Confirm the FOCUS dataset version available for your billing scope.

3. Check whether that version is generally available or in preview.

4. Review which FOCUS 1.2 fields Microsoft currently populates.

5. Confirm that the fields required by your Yarken reporting contain the expected data.

Move an existing export to FOCUS 1.2 (optional)

1. Confirm provider support

Check that FOCUS 1.2 is available for the provider, billing account type, and scope you use.

Review the provider's current schema and migration documentation before changing the existing export.

2. Create the FOCUS 1.2 export

Create a new export using the provider's FOCUS 1.2 dataset.

Where possible, keep the existing export active during validation instead of immediately replacing it.

3. Run both exports in parallel

Where practical, run the existing export and the FOCUS 1.2 export in parallel for at least one complete billing period.

Parallel running gives you a period in which you can compare financial results and identify schema, mapping, or reporting differences before cutover.

Different FOCUS versions can legitimately produce different record counts or field values, so do not use row counts alone to determine whether the datasets match.

4. Update ingestion mappings

Configure the FOCUS 1.2 dataset as required by your Yarken ingestion process.

Map the fields required for your reporting, including the additional supported FOCUS 1.2 fields where they are supplied by the provider.

Review existing mappings for fields that have been renamed, replaced, removed, or represented differently in the new provider dataset.

5. Validate the data

Before using the new export for production reporting, validate:

• Total cost for comparable billing periods

• Billing and charge periods

• Billing and pricing currencies

• Billing account and sub-account structures

• Provider, service, product, and resource dimensions

• Tags and ownership information

• Cost and pricing measures

• Consumption measures used by reporting

• FOCUS 1.2 fields required by your use cases

6. Validate downstream reporting

Check the Yarken capabilities that consume the data, including those relevant to your environment:

• Analytics views

• Dashboards

• Cost Explorer

• TBM mappings and allocation

• Chargeback and showback

• Planning and forecasting

• Recommendations

• Custom reports and calculations

7. Complete the move to FOCUS 1.2

After validating the FOCUS 1.2 data and downstream reporting, you can choose to replace your existing FOCUS 1.0 export.

Before replacing the previous export:

1. Choose an appropriate date to start using the FOCUS 1.2 export as your primary data source.

2. Where possible, align the change with a billing-period boundary to simplify reconciliation.

3. Confirm that FOCUS 1.2 data is being ingested successfully into Yarken.

4. Verify that expected reporting, mappings, allocations, and other downstream processes are working correctly.

5. Retire the previous FOCUS 1.0 export when you are satisfied with the FOCUS 1.2 results and no longer require the previous export.

Validate your FOCUS 1.2 migration

If you choose to migrate an existing FOCUS 1.0 integration, complete the following checks before replacing your existing export:

• FOCUS 1.2 is available for the required provider and billing scope.

• A new FOCUS 1.2 export has been created.

• The existing and new exports have been compared over a suitable period.

• Required FOCUS 1.2 fields are present in the source data.

• Required fields are populated by the provider.

• Yarken ingestion mappings have been reviewed.

• Cost totals have been reconciled.

• Currency fields have been validated.

• Billing account and sub-account mappings have been validated.

• Tags and ownership mappings have been reviewed.

• Analytics and dashboards have been validated.

• TBM allocation has been validated where applicable.

• Chargeback or showback results have been validated where applicable.

• Custom calculations or reports have been checked.

• The final cutover has been planned.

Troubleshoot FOCUS 1.2 data

A field is missing

Confirm that:

• The source export is using FOCUS 1.2.

• The field exists in the provider's implementation.

• The provider populates the field for your data.

• The field has been included in the Yarken ingestion mapping.

A field exists but has no values

Check the provider's FOCUS schema documentation.

Costs do not match the previous export

Check:

• The billing and charge periods being compared

• The cost measures used in the comparison

• Currency fields

• Provider-specific FOCUS migration changes

• Filters and account scope

• Changes in row representation between versions

Downstream reports have changed

Review any:

• Renamed or replaced source fields

• Provider extension fields

• Tags

• Allocation rules

• Chargeback definitions

• Custom calculations

• Analytics filters and dimensions

External resources

Provider capabilities and FOCUS versions can change over time. Use the current provider documentation when configuring or migrating an export.

• FOCUS 1.2 specification — Review the FOCUS 1.2 schema, terminology, and requirements.

• FOCUS provider getting-started guidance — Check provider adoption and available FOCUS datasets.

• Introducing FOCUS 1.2 — Review the capabilities and fields introduced with FOCUS 1.2.

• AWS FOCUS 1.2 with AWS columns — Review the AWS FOCUS 1.2 schema and AWS-specific columns.

• AWS: Migrating from FOCUS 1.0 to FOCUS 1.2 — Review AWS-specific schema and behavioral changes before migration.

• AWS Data Exports — Review current AWS Data Exports configuration guidance.

• Microsoft Cost Management FOCUS schema — Review Microsoft's FOCUS cost and usage fields and version-specific information.

• Microsoft Cost Management exports — Review Microsoft's current instructions for creating and managing exports.

Related content

• FinOps

• Consumption Data

• Cloud Usage Data

• Getting Started with Analytics

• Cost Explorer

• Technology Business Management