Closed cluppino closed 4 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.
Storage team, please help to look into this issue.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv, @vaibhav-agar, @amjads1.
This cmdlet is from Az.Compute, so remove storage tag, and add Compute tag.
@Vaibhav-Agar would you be able to take a look at this ?
Hi, I am facing a very similar problem so I am just leaving a comment to follow this and be informed how it can be removed
Hi @cluppino,
Refer the text below from the link here: https://docs.microsoft.com/en-us/rest/api/compute/disks/createorupdate
storageAccountId | string | Required if createOption is Import. The Azure Resource Manager identifier of the storage account containing the blob to import as a disk.
From the script you provided, I can see that the createOption is indeed Import and hence StorageAccountID is a required field. Please let me know if you still have questions here.
storageAccountId is a parameter of New-AzDiskConfig, not New-AzDisk
The sample script is incorrect at this page: https://learn.microsoft.com/en-us/azure/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-vhd
Description
New-Azdisk command fails requiring a storageaccountId parameter
Script has previously worked both locally and in Cloud Shell Testing on both local with latest Module Updates and also in Cloud Shell now fails
Steps to reproduce
Disk VHD Image located in a Blob container (Page Blob) Use commands below to create new managed disk from blob
Environment data
Collected from Cloud Shell
Module versions
Debug output
Error output