I recently had to promote a VM image for a scale set between subscriptions. It turns out this was very complex; but this blog was a life saver. So, I highly recommend reading it if you need to do this.
This is re-blogged; so just click the link below to see the full original block (which I highly recommend).
Introduction
Azure Managed Disks were made generally available (GA) in February 2017. Managed Disks greatly simplify working with Azure Virtual Machines (VM) and Virtual Machine Scale Sets (VMSS). They effectively eliminate the need for you to have to worry about Azure Storage accounts and related VHD constraints/limits. When using managed disks for VMs or VMSS, you select the type of disk storage (SSD or HDD) and the size of disk needed. The Azure platform takes care of the rest. Besides the simplified management aspect, managed disks bring several additional benefits, but I’ll not reiterate those here, as there is a lot of good info already available (here, here and here).
While managed disks simplify management of Azure VMs, they also simplify working with VM images. Prior to managed disks, an image would need to be copied to the Storage account where the derived VM would be created…
View original post 1,255 more words
Coding Stream of Consciousness 