VM deployment using JSON and specialized disk does not display Computer Name
VM deployment using a JSON template and specialized disk does not
As per Microsoft support the following answer was received:
This behavior is currently by design.
The portal reads the Computer name information from the OSProfile settings section of a VM. But when creating a VM from an existing disk we don’t include this section in the template (or powershell) because this is only used for generalized images.
At the moment we cannot edit the OSProfile of an existing VM, thus the name property on the portal remains blank.
Unfortunately, although this may be by design it does not provide clients with the comfort that an Azure VM deployed using their own specialized image (ie migration to Azure from on prem) is successful.
This should be considered or at least published as a know limitation with deploying VMs using specialized VHDs.
Joshua Wong commented
If this can provide support for modifying the OSProfile (i.e. computer name, admin username, etc) that would be extremely useful if they are null or fix the issue of why they are not properly returning the value. The downstream impact of this is that terraforming these VMs is impossible due to the computerName and adminUsername being null.
They heard you.. Its out there.. KB 4018140 - computer-names-of-specialized-virtual-machines-are-missing-or-blank-in