I created Azure Managed Application. I used managed images in `mainTemplate.json` to create new VMs, like in example:

```
{
    "type": "Microsoft.Compute/images",
    "apiVersion": "2018-04-01",
    "name": "front-image",
    "location": "[parameters('location')]",
    "properties": {
        "storageProfile": {
            "osDisk": {
                "osType": "linux",
                "osState": "Generalized",
                "blobUri": "[concat('https://sdfasdfasdf.blob.core.windows.net/images/myserver.vhd')]",
                "caching": "ReadWrite",
                "storageAccountType": "Standard_LRS"
            }
        }
    }
}, {
    "apiVersion": "2016-04-30-preview",
    "type": "Microsoft.Compute/virtualMachines",
    "name": "myserver",
    "location": "[parameters('location')]",
    "dependsOn": ["myserver-nic", "myserver-images"],
    "properties": {
        "storageProfile": {
            "imageReference": {
                "id": "[resourceId('Microsoft.Compute/images', 'myserver-image')]"
            }
        },
        ...
    }
}

```

This work well in Service catalog. But when I trying deploy application from Azure Marketplace, I have next error:

**The source blob <https://sdfasdfasdf.blob.core.windows.net/images/myserver.vhd> does not belong to a storage account in subscription \*\*\*\*\*\* .**

In Azure [FAQ](https://learn.microsoft.com/en-us/azure/virtual-machines/windows/faq-for-disks) I found next:

Q: Can I use a VHD file in an Azure storage account to create a managed disk with a different subscription?

A: Yes.

What I doing wrong?