The following error is seen while updating a MCS Machine Catalog after resizing the size of the Master VM disk.

Exception:

   StudioErrorId : ProvisioningTaskError

   ErrorCategory : NotSpecified

   TaskState : FailedToCreateImagePreparationVm

   TaskStateInformation : Terminated

   ErrorId : FailedToCreateImagePreparationVm

   Operation : PreparingMasterImage

   ErrorMessage : Error: creating virtual machine failed. Exception: {"status":"Failed","error":

The Deployment error from Azure is seen:

• StorageFailure/BlobTierInadequateForContentLength","message":"Error while creating storage object"

Avoid resizing Master VM disks during the lifecycle of a MCS Machine Catalog where possible.

Workaround:

Modify the Storage Tier of the Machine profile under Azure Disk Size and Performance Settings according to the new disk size of the Master VM.

• i.e. if the disk size was upgraded from P10 to P20 (512GB) we need to edit the storage tier to P20 in the above setting.

Problem Cause

The error comes from a mismatch between the blob tier of the target storage container and the content length.  The content length is the size of the updated VHD/blob being updated by MCS.

During an MCS update:

• MCS creates a new snapshot based on the master VM.
• Uploads the VHD blob to Azure Storage
• If the new disk size is too big, Azure blocks the upload with the error BlobTierInadequateForContentLength 

https://learn.microsoft.com/en-us/rest/api/storageservices/blob-service-error-codes