From readme here https://github.com/Azure/vm-scale-sets/tree/master/preview/disk, looks like this feature is no longer in preview since 2017, is that true? If so please kindly update the document
What permission is required to attach to additional disk? From the API document does it mean as long as we have the resource ID of the managed disk we can attach it to any VMSS?
I tried using az vmss disk attach command and was able to attach existing disk to one instance of vmss, but when I tried to attach the same disk to a second instance I got following error:
Disk '{disk_id}' cannot be attached as the disk is already owned by VM '{instance_id}'
Our use case would be attaching the existing disk to all VMs inside the VMSS, is this capable for existing disks? Is duplicating the disk only option for us? Any potential on a feature request to allow existing disk attachable to multiple VMs?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks for the feedback! We are currently investigating and will update you shortly.
@mayanknayar Can you please share your insights on the customer's questions?
The first one is doc-enhancement and the other two are questions related to, whether those scenarios are supported or not.
I am assigning the issue to you for the doc update in point 1. Thanks :)
Thanks for following up, I did some more research and for question 3 seems replication of data disks is the only option.
Question 2 is still an outstanding question from us
@mayanknayar Did you get a chance to take a look at the customer's question? Thanks :)
We are currently closing out long standing backlog in order to better determine which issues are still valid and which have been addressed. If you are still seeing a specific problem with this document please open a new issue so we can properly assign the feedback to the correct author and get it addressed ASAP.