Azure-docs: The resource group name of disk is in upper-case, however other resources isn't

[ToMakeSense]

I found the resource group name of disk is in upper-case, however other resources are not if I create the VM and related resources via Azure portal. I know this does not affect the use. But it is better to be consistent.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2e58109c-c8d3-6693-8e1d-03a89ca26168
• Version Independent ID: f20a7fc4-328a-e90d-29db-92a91aa1b2bd
• Content: Quickstart - Create a Windows VM in the Azure portal
• Content Source: articles/virtual-machines/windows/quick-create-portal.md
• Service: virtual-machines-windows
• GitHub Login: @cynthn
• Microsoft Alias: cynthn

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[mimckitt]

@ToMakeSense thanks for bringing this to our attention. It appears to be isolated to the disks as I created a few VMs and all the resource group names were all caps visually only when related to the disks. All else was however I put it in to begin with. This does no impact functionality as the capitalization on the backend is ignored.

From a doc perspective, there is not an issue. Rather a odd display issue with disks. I have raised this to the engineering team to look into. No ETA on when it will be address as it is low priority and does not actually impact functionality. We agree consistency is important so it will be address at some point :)

[ToMakeSense]

@MicahMcKittrick-MSFT Thanks for your reply, just want to help to improve Azure to be better.

[dylanhughes]

This still looks to be the case, any further update from engineering team when this will be resolved please?

[fazdamoa]

Querying the id of a disk from the Azure CLI returns capitalization of RG name in the id, and it shows in the portal as well. It doesn't seem to do this for other resources. As the RG name is incorrect in the id, az resource move command doesn't work (resource not found)

Changing the case of the RG name manually back to lowercase succeeds, and seems to be the only workaround.

[ashijit]

@mimckitt This is resulting in a disk resize failure for me, wherein the disk shows up in a resource group STAGING_UAT -

Failed to update disk 'staging_OsDisk_1_stringhere'. Error: The Resource 'Microsoft.Compute/disks/staging_OsDisk_1_stringhere' under resource group 'Staging_UAT' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

[xer0w]

I actually get the same behaviour for Disks and VM's for a particular RG, the resource group is shown in uppercase in the VM & Disks blades and if I query with Get-AzVM and Get-AzDisk, but lowercase from the Resource groups blade (or any other resources view)

[Lobosque]

This also happens in my azure account. where am I supposed to report this?

[ArgonQQ]

It would really interest myself why this is happening and why this is closed if there hasn't been a "solution" posted here 🧐 ⁉

[fazdamoa]

I had this problem in the Azure CLI when trying to grab disk IDs for a move command on multiple VMs.

The way I got around this in a bash script was this:

# OS Disk: Get name of disk and then query ID using this
osdiskname=$(az vm show -g rg1 -n vm1 --query "storageProfile.osDisk.name" -o tsv)
osdiskid=$(az disk show --name $osdiskname --resource-group rg1 --query "id" -o tsv)

# Get IDs of possible multiple data disks
datadisknames=$(az vm show -g rg1 -n vm1 --query "storageProfile.dataDisks[].name" -o tsv)
datadiskids=""
for i in $(echo $datadisknames); do datadiskids=`echo $datadiskids \`az disk show --name $i --resource-group rg1 --query "id" -o tsv\``; done

This gives the full Disk ID with the lower-case RG name.