Inconsistent functionality between Azure CLI and Powershell cmdlet

Question

I tried to create 2 virtual machines with the same parameters but with 2 different ways:

The Powershell cmdlet:

New-AzVm -ResourceGroupName $rg -Name "Testing1img" -Credential $credential -Image UbuntuLTS

Azure CLI from Powershell:

az vm create `
  --name "Testing2img" `
  --resource-group $rg `
  --admin-username $credential.UserName `
  --admin-password $credential.Password `
  --image "UbuntuLTS"

Both create an Ubuntu LTS VM on the same resource group (different name). The problem I have is that they create VMs with slightly different settings.

In the first case it creates:

an Ubuntu 16.04 Linux
DNS name is being assigned

In the second case we have:

an Ubuntu 18.04 Linux
No Dns name is being configured

Why these (even small) differences? Shouldn't they both create the same exact VMs? Someone asking for an UbuntuLTS would expect the latest available image and not 16.04.

I run them directly from MS Terminal (Azure Cloud Shell). I think both are at the latest. The pwsh is at 7.0.3 and the cli at 2.13.0. — Efthymios Kalyviotis
– Efthymios Kalyviotis, Commented Oct 26, 2020 at 20:26

Phil Evans · Accepted Answer · 2021-02-15 02:13:44Z

1

For New-AzVM you can specify the Ubuntu version with... -Image Canonical:UbuntuServer:18.04-LTS:latest

answered Feb 15, 2021 at 2:13

Phil Evans

113 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Inconsistent functionality between Azure CLI and Powershell cmdlet

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related