Supported metric in Microsoft.Compute/virtualMachines namespace does not look to return any values

[narph]

In azure/compute_vm metricset atm we retrieve all metric definitions, group them and then collect values based on their names.
We see a few new(?) metrics added to the Microsoft.Compute/virtualMachines namespace (when retrieving the metric definitions https://management.azure.com//subscriptions/{sub}/resourceGroups/{group}/providers/Microsoft.Compute/virtualMachines/{name}/providers/microsoft.insights/metricDefinitions?api-version=2018-01-01&metricnamespace=Microsoft.Compute/virtualMachines):

"name":{
            "value":"VM Cached Bandwidth Consumed Percentange",
            "localizedValue":"VM Cached Bandwidth Consumed Percentange"
         },
         "displayDescription":"Percentage of cached disk bandwidth consumed by the VM.",

"name":{
            "value":"VM Cached IOPS Consumed Percentange",
            "localizedValue":"VM Cached IOPS Consumed Percentange"
         },
         "displayDescription":"Percentage of cached disk IOPS consumed by the VM.",

"name":{
            "value":"VM Uncached Bandwidth Consumed Percentange",
            "localizedValue":"VM Uncached Bandwidth Consumed Percentange"
         },
         "displayDescription":"Percentage of uncached disk bandwidth consumed by the VM.",

"name":{
            "value":"VM Uncached IOPS Consumed Percentange",
            "localizedValue":"VM Uncached IOPS Consumed Percentange"
         },
         "displayDescription":"Percentage of uncached disk IOPS consumed by the VM.",

But when retrieving the values based on the metrics the api returns:

{"code":"BadRequest","message":"Failed to find metric configuration for provider: Microsoft.Compute, resource Type: virtualMachines, metric: VM Cached Bandwidth Consumed Percentange, Valid metrics: Percentage CPU,Network In,Network Out,Disk Read Bytes,Disk Write Bytes,Disk Read Operations/Sec,Disk Write Operations/Sec,CPU Credits Remaining,CPU Credits Consumed,Per Disk Read Bytes/sec,Per Disk Write Bytes/sec,Per Disk Read Operations/Sec,Per Disk Write Operations/Sec,Per Disk QD,OS Per Disk Read Bytes/sec,OS Per Disk Write Bytes/sec,OS Per Disk Read Operations/Sec,OS Per Disk Write Operations/Sec,OS Per Disk QD,Data Disk Read Bytes/sec,Data Disk Write Bytes/sec,Data Disk Read Operations/Sec,Data Disk Write Operations/Sec,Data Disk Queue Depth,Data Disk Bandwidth Consumed Percentage,Data Disk IOPS Consumed Percentage,OS Disk Read Bytes/sec,OS Disk Write Bytes/sec,OS Disk Read Operations/Sec,OS Disk Write Operations/Sec,OS Disk Queue Depth,OS Disk Bandwidth Consumed Percentage,OS Disk IOPS Consumed Percentage,Inbound Flows,Outbound Flows,Inbound Flows Maximum Creation Rate,Outbound Flows Maximum Creation Rate,Premium Data Disk Cache Read Hit,Premium Data Disk Cache Read Miss,Premium OS Disk Cache Read Hit,Premium OS Disk Cache Read Miss,VM Cached Bandwidth Consumed Percentage,VM Cached IOPS Consumed Percentage,VM Uncached Bandwidth Consumed Percentage,VM Uncached IOPS Consumed Percentage,Network In Total,Network Out Total"}

The message is highly confusing since in the list of valid metrics we can find VM Cached Bandwidth Consumed Percentage.

We do not see these 4 metrics in the official list of supported metrics or in Azure monitor at the resource level.
Older vm type resources seem to not be affected by this issue.

A possible workaround at the moment is ignoring the error in the logs and dropping the empty events by matching their error message (https://www.elastic.co/guide/en/beats/metricbeat/current/drop-event.html).
Values for the other metrics are still being returned.

[elasticmachine]

Pinging @elastic/integrations-platforms (Team:Platforms)

[narph]

close for now, was fixed on the Azure side.