yeah, i find the whole azure support lacking.
We have this server with 20+ disks, some in storage pool and now I have no way mapping them out to see which logical drive maps to which vm disk. the support after 3 months of back and forth just gave up and closed it citing known issue without official documentation...
That's actually not that hard. The LUN numbers map through 1:1 to the guest OS. So the external LUN #1 is the internal LUN #1, etc...
Then you can use the Windows OS storage pool commands to figure out the internal mapping.
However, you do have a point -- the disk WWN or GUID or something properly unique ought be available via the Portal or the ARM REST API! That's far easier to automate robustly.
I thought that's how too, but maybe I got my mental model messed up.
Will give it a proper visit, the last time I tried to downgrade some ssd to hdd resulted in windows boot loop. fun times, had to take a snapshot then fiddle it's registry in another vm so it'd use the last known working registry to get it back up.
