Deprecation of Cloud compute asset types :

Last updated: 2025-04-22

Source: https://support.freshservice.com/support/solutions/articles/50000010317-deprecation-of-cloud-compute-asset-types

Cloud compute assets like Azure VM are discovered from multiple sources, such as Probe, Agent, and Cloud application integrations. To maintain a single record for every discovered Cloud compute asset and avoid duplication, we will gradually migrate the Cloud compute assets for existing customers under the new Hardware asset sub-types irrespective of the discovery sources.

Overall, deprecating the Cloud compute asset type and standardizing with the Hardware asset type will provide several benefits, such as unified asset management, improved data accuracy, enhanced reporting and analytics, greater workflow reliability, and simplified asset reconciliation.

_Note:__The data migration process for existing customers using the deprecated Cloud compute asset types will be initiated after a support ticket is raised by the customer. See What should you do? section below for more information._

What will change after this deprecation?

To support a standard asset type classification, we will introduce new asset sub-types under the Hardware asset type for the assets discovered via cloud management applications.

All Cloudcompute asset types and associated sub-types will be mapped under the Hardware asset type and its new associated sub-types. The following table provides the mapping details:


Cloud compute assets (existing mapping)	Hardware assets (new mapping)
Cloud - Host	Hardware - Computer-Host
Cloud - Host - VMware VCenter Host	Hardware - Computer-Host - VMware Host
Cloud - Virtual Machine	Hardware - Computer-Server
Cloud - Virtual Machine - VMware VCenter VM	Hardware - Computer-Server - VMware VM
Cloud - Virtual Machine - AWS VM	Hardware - Computer-Server - AWS VM
Cloud - Virtual Machine - Azure VM	Hardware - Computer-Server - Azure VM
Cloud - Virtual Machine - GCP VM	Hardware - Computer-Server - GCP VM
Cloud - K8s Node	Hardware - Computer-Server - K8s Node
Cloud - K8s Node - AWS K8s Node	Hardware - Computer-Server - K8s Node - AWS K8s Node

_(Post deprecation)_To verify Cloud compute asset types (from the above list) are deprecated:

1\. Go to Assets > Cloud.

2\. Click the Filter icon. Then, click the Hierarchy View icon under Asset Type.

3\. Verify that the following Cloud asset types show ‘deprecated’ status.

How do I know if this deprecation impacts me?

This deprecation will impact customers subscribed to _Basic Discovery_ who match the following conditions:

If you have any assets under the deprecated Cloud asset type in Inventory.

If you have Cloud assets discovered via discovery sources, such as AWS, Azure, VMware, Intune, and so on.

_Note:_ _Customers subscribed to Advanced Discovery (powered by Device42)__are not impacted._

What is the impact of this deprecation?

As part of the deprecation process and mapping of all Cloudcompute asset types to their respective Hardware asset types, there will be an impact on the following application-related features:

Assets discovered:All the discovered Cloud compute assets will be automatically mapped to the new Hardware asset sub-types.

Workflows:

Existing workflows with deprecated asset types: If you have existing workflows configured with the deprecated Cloud compute asset types, they must be disabled. The existing workflows will not function for Cloud compute assets, as all the discovered assets will be mapped to the updated asset type.

You will need to create new workflows with the updated asset type.

Default and custom fields: For every asset previously discovered with the deprecated Cloud compute asset types, you will need to re-configure all the default and custom fields for the updated asset type.

Curated and custom reports: You will need to re-configure all the curated and custom reports related to the deprecatedCloudcompute asset types based on the updated asset type.

_Important:_ _Post deprecation, you must create new reports for any Custom reports that reference the deprecated Cloud compute_ _asset types. You should take a backup of each asset type with the export option._

Associations related to assets: For every asset previously discovered with the deprecated Cloud compute asset types, all the associations related to each asset will be retained.

What should you do?

Before data migration:

When is data migration initiated: The data migration process for existing customers using the deprecated Cloud compute asset types will be initiated after a support ticket is raised.

When to raise a support ticket: When you plan to install any additional discovery source for Cloud compute asset types (such as AWS Cloud Management), you will need to raise a support ticket to prevent data duplication.

What should be the title of the support ticket: You need to raise a support ticket to support@freshservice.com with the title _“Support Request: Adding a New Discovery App with Existing Cloud Discovery Setup.”_

What to expect after the support ticket is raised: The Freshservice engineering team will migrate the data from the deprecated Cloud compute asset types to the updated asset type. Post the data migration, you can install any new discovery source for Cloud assets. Then, both the existing and new Cloud discovery sources will update Cloud compute assets under the new Hardware asset type.

After data migration:

Create new workflows with the updated asset type, and disable the workflows that are based on the deprecated asset type.

Re-configure all the curated reports, and create new custom reports based on the deprecated asset types.

Re-configure all the default and custom fields listed for the updated asset type.

For any queries, reach out to us at support@freshservice.com.