![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 62%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
That's expected - these two settings are not equivalent. Azure premium disks are block devices stored on SSD, but the guest OS never sees the physical media. What the OS reports is the virtual controller and bus presented by the underlying hypervisor. Premium, Standard SSD and Standard HDD managed disks are all exposed through the same virtual SCSI stack, and many OS tools label that as SAS or SCSI instead of SSD because they have no way to probe the actual backing storage.
Inside a VM you do not have direct access to the underlying hardware, so tools like lsblk, fdisk, or Device Manager in Windows determine the disk type based on the presented controller type. When they see a virtual SCSI device they default to showing HDD or SAS even if the real storage is SSD.
The authoritative source is the Azure control plane (portal, ARM, CLI). If the disk resource says Premium SSD LRS then the data is on SSD even if the OS reports HDD.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin