What to do if Meter ID is incorrect in Azure Billing Usage API usage data

Question

I get the wrong counter id from the Azure Usage Billing API. The following is an accurate record of the answer, which is incorrect. Note that instead of Guid. This is the text "1core" . Therefore, I can not find this indicator from the data of the tariff map API. I also noticed that many other properties, such as the Resource Category, are also null. The same entry is repeated on different days.

Can someone tell me why this could be? And also, how should I view this entry when trying to calculate my monthly bill?

{ "id":"/subscriptions/1a11aa11-5c9b-4c94-b875-b7b55af5d316/providers/Microsoft.Commerce/UsageAggregates/Daily_BRSDT_20160312_0000", "name":"Daily_BRSDT_20160312_0000", "type":"Microsoft.Commerce/UsageAggregate", "properties":{ "subscriptionId":"1a11aa11-5c9b-4c94-b875-b7b55af5d316", "usageStartTime":"2016-03-11T00:00:00+00:00", "usageEndTime":"2016-03-12T00:00:00+00:00", "instanceData":"{\"Microsoft.Resources\":{\"resourceUri\":\"/subscriptions/1a11aa11-5c9b-4c94-b875-b7b55af5d316/resourceGroups/OPENTEXT-RESOURCE/providers/Microsoft.Compute/virtualMachines/OpenText-Test01\",\"location\":\"eastus\",\"partNumber\":\"1AA1A1X2X3J6Z5CTGYDP3JINVU3KI3SQMOF62ZDVD4WHVECLMDI72J5ZD42PMNW4IEDRHARE6JZZ3LHM65KKHRDNLEL5EOQALXEFO5A\",\"orderNumber\":\"a1aa1111-bed9-4451-bdf7-274f05f35201\",\"additionalInfo\":{\"ImageType\":\"\",\"ServiceType\":\"Standard_A1\",\"VMName\":\"\",\"UsageType\":\"ComputeHR_SW\"}}}", "meterId":"1core", "infoFields":{ }, "quantity":8.0 } }, 

Answer 1

I received an official response from MSFT that this particular entry relates to resources related to third party items. Unfortunately, these elements of the third-party market do not implement the billing API, which is now in preview. If you also see such entries, please ignore these entries and simply highlight in the report that the resources of third-party markets may not be in the billing report. Please note that this may change in the near future, although there is no date.