Breadcrumbs

Automatic asset association for Cloud Recommendations

When Cloud Recommendations are imported, Yarken attempts to associate each recommendation with the relevant Application, Service, or Product asset.

This association helps recommendations appear in the appropriate asset and dashboard views (Application, Product, or Service Portfolio dashboards) without requiring you to assign every recommendation manually.

Automatic association applies to recommendations imported through:

  • Recommendation file uploads

  • Advanced Integrations

Prerequisites

For automatic asset association, confirm that:

  • The recommendation file contains the cloud Resource ID.

  • Cloud Consumption data has already been loaded for the affected resources.

  • Application, Service, or Product tags are populated in the Cloud Consumption records.

  • Tag values match existing asset names in Yarken.

The recommendation can still be imported when these conditions are not met, but it will not be automatically associated with an asset.

How automatic association works

For each imported Cloud Recommendation, Yarken:

  1. Reads the Resource ID from the recommendation.

  2. Searches Cloud Consumption data for a record with the same Resource ID.

  3. Checks the asset tags on the matching consumption record in the following order:

    1. Application Tag

    2. Service Tag

    3. Product Tag

  4. Uses the first populated tag as the asset name.

  5. Searches the Assets table for an asset with the same name.

  6. Associates the recommendation with the matching asset.

Only the first populated tag is evaluated. For example, when an Application Tag is available, Yarken does not evaluate the Service Tag or Product Tag.

Manual associations take precedence

When a recommendation already has an asset assigned manually, Yarken retains that association.

The automatic process does not replace an existing manual asset assignment.

When an asset is not associated

The recommendation remains available even when Yarken cannot determine an asset.

The Asset ID remains blank when:

  • No Cloud Consumption record has the same Resource ID.

  • The matching consumption record has no Application, Service, or Product tag.

  • The selected tag does not match an asset name in Yarken.

A missing association does not cause the recommendation import to fail. Yarken continues processing the remaining records.

Example

Consider an imported recommendation with the following value:

  • Resource ID: /subscriptions/123/resourceGroups/production/providers/Microsoft.Compute/virtualMachines/vm-01

Yarken finds a Cloud Consumption record with the same Resource ID and the following tags:

  • Application Tag: Customer Portal

  • Service Tag: Web Hosting

  • Product Tag: Digital Services

Because Application Tag has the highest priority, Yarken selects Customer Portal.

If an asset named Customer Portal exists in Yarken, the recommendation is associated with that asset. The recommendation can then appear in views and reports related to the Customer Portal application.

If the Application Tag were blank, Yarken would use Web Hosting, the Service Tag. The Product Tag would only be considered when both the Application Tag and Service Tag are blank.

Validate automatic asset associations

After the recommendation import completes:

  1. Open Admin > Recommendations.

  2. Select the Details tab.

  3. Find a sample of the imported recommendations.

  4. Confirm that Cloud Resource ID contains the expected resource.

  5. Review Asset Type and Asset Code.

    Screenshot 2026-08-04 at 3.11.30 PM-20260804-094205.png

  6. Confirm that the recommendation is associated with the expected Application, Service, or Product.

  7. Open the relevant asset or Application Portfolio view and verify that the recommendation appears.

When the asset fields are blank, compare the recommendation Resource ID with Cloud Consumption data. Then verify that the selected Application, Service, or Product tag exactly matches an existing asset name.

Related content