From c98f3c648237321407396379ca667409dff2e042 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia=20Mendes?= <53820260+clmendes-MSFT@users.noreply.github.com> Date: Wed, 27 Nov 2024 16:37:20 +0000 Subject: [PATCH] Update image-version.md command was wrong. was referncing managed image instead of VMs --- articles/virtual-machines/image-version.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/virtual-machines/image-version.md b/articles/virtual-machines/image-version.md index 8e1395e9279..bf534943f13 100644 --- a/articles/virtual-machines/image-version.md +++ b/articles/virtual-machines/image-version.md @@ -166,7 +166,7 @@ In the example below, we are creating an image from a **VM**. The version of our It is a best practice to stop\deallocate the VM before creating an image. -Replace the value of `--managed-image` in this example with the ID of your VM. +Replace the value of `--virtual-machine` in this example with the ID of your VM. ```azurecli-interactive az sig image-version create \ @@ -176,7 +176,7 @@ az sig image-version create \ --gallery-image-version 1.0.0 \ --target-regions "westcentralus" "southcentralus=1" "eastus=1=standard_zrs" \ --replica-count 2 \ - --managed-image "/subscriptions//resourceGroups/MyResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM" + --virtual-machine "/subscriptions//resourceGroups/MyResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM" ``` > [!NOTE]