You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In result files, for VMs storage, Microsoft.Compute/disks type may be used instead of Microsoft.Compute/virtualMachines in "impacted" file/tab
Actual Behavior
AZQR version : azqr version 2.0.3-preview.0.3
Environment : WSL2
AZQR result files (csv and xlsx) seems to provide the following mismatch :
In "Inventory" file/tab, Disks are identified as Microsoft.Compute/disks whereas in "Impacted", the same resources are identified as Microsoft.Compute/virtualMachines resource type.
(Maybe the type was filled with ManagedBy information instead of Resource type ?)
Steps to Reproduce the Problem
Scan a resource group where Disks do not follow this recommendation : Use Azure Disks with Zone Redundant Storage for higher resiliency and availability and compare the used resource type in Inventory and Impacted files/tabs.
Thanks for your help,
Regards,
David
The text was updated successfully, but these errors were encountered:
Expected Behavior
In result files, for VMs storage, Microsoft.Compute/disks type may be used instead of Microsoft.Compute/virtualMachines in "impacted" file/tab
Actual Behavior
AZQR version : azqr version 2.0.3-preview.0.3
Environment : WSL2
AZQR result files (csv and xlsx) seems to provide the following mismatch :
In "Inventory" file/tab, Disks are identified as Microsoft.Compute/disks whereas in "Impacted", the same resources are identified as Microsoft.Compute/virtualMachines resource type.
(Maybe the type was filled with ManagedBy information instead of Resource type ?)
Steps to Reproduce the Problem
Scan a resource group where Disks do not follow this recommendation : Use Azure Disks with Zone Redundant Storage for higher resiliency and availability and compare the used resource type in Inventory and Impacted files/tabs.
Thanks for your help,
Regards,
David
The text was updated successfully, but these errors were encountered: