Azure Snapshot storage type such as Standard HDD Managed Disks are falling under 'Other' service category instead of the 'Disks' service category.
The Standard HDD managed disks under Other are part of
Microsoft.Compute/restorePointCollections, those do not typically have a
dedicated meterid (meter_guid) associated with the restore point
collection resource itself. Restore point collections act as containers
for VM restore points, which are essentially snapshots of managed disks
at a specific point in time.
Billing for Azure managed disks, including Standard HDD, is generally
tracked at the disk resource level, not at the restore point collection
level. The restore points themselves represent snapshots and may incur
storage charges, but these are billed under snapshot or backup meters,
not as separate Standard HDD managed disk meters within the
restorePointCollections resource.
As a result, there will not be a meterid specifically for
Standard HDD managed disks under
Microsoft.Compute/restorePointCollections in the billing data. Instead,
any costs related to the storage of restore points (snapshots) are
reflected under the relevant snapshot or backup meter, not as a direct
meterid for the managed disk itself within the restore point collection.
Our platform only maps directly attached disks costs for Compute-Disk at the moment to the 'Disks' service category, but there is no mapping for RestorePointCollections hence why they are falling under 'Other' Service Category.