Vhd and target vm are not in the same blob storage

Hello!
Thank you for your attention to my question.
I am now reading the azure-quickstart-templates / cloudera-on-centos / module code.
I would like to imitate your code and then develop your own projects to achieve the company's products through the arm template automatically deployed to azure.
But I met it hard.

I'm currently trying to automate the deployment of virtual clusters. Every one of the machines / cluster should get its own storage account to keep things faster and also make deletion easier.

Scripting with Azure CLI is so far without problems, only when trying to use another storage account then where our own image is located, I get the error that the image and target VHD for the new machine must be located in the same storage account.

The disk's VHD must be in the same account as the VHD of the source image (source account: foo, target account: bar

Am I right in assuming this is an API limitation? Anyone has a recommendation how to work around this?

Obvious way around is kind of a pain in the ass because I have to copy the image blob from one account to another before deploying the virtual machine, which is not really an option for time reasons

Start with the azure-quickstart-templates/cloudera-on-centos/module code and reproduce the deployment using Azure CLI with separate source and target storage accounts. Determine whether the Azure API permits this layout and document a supported workaround or the limitation.

Written by the indexing model from the issue text.