It is sometimes found that an Azure asset is not found in the expected group in a Perspective.  It is instead seen as categorized under its Resource Group, Subscription, or "Other" group. 

This is expected behavior when the asset has a cost line item in the bill but has not yet been collected and/or processed via a call to the Azure API or cannot be derived form the bill and stored on our Asset database.  This also may occur for a new asset type that is not yet supported. 

When data is processed for display within a perspective if we can’t find the actual asset itself associated with the line item in our database we first fall back to the Resource Group of the line item and then to its Subscription.  The asset will then be placed in a group if one exists for its Resource Group or Subscription.  If no such category exists then the asset will default to appear in the "Other" grouping.   This is currently expected behavior and is designed to place the cost for an asset line item in a relevant grouping or "Other" if a categorization determination cannot be made.