Merge pull request #230872 from cynthn/delete-move

Delete move

Author: v-shils

articles/virtual-machines/.openpublishing.redirection.virtual-machines.json

@@ -15,6 +15,21 @@
             "redirect_url": "/previous-versions/azure/virtual-machines/linux/tutorial-load-balancer",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/virtual-machines/linux/move-vm.md",
+            "redirect_url": "/azure-resource-manager/management/move-resource-group-and-subscription#use-azure-cli",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-machines/windows/move-vm.md",
+            "redirect_url": "/azure-resource-manager/management/move-resource-group-and-subscription",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-machines/windows/aws-to-azure.md",
+            "redirect_url": "/azure/migrate/tutorial-migrate-aws-virtual-machines",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/virtual-machines/windows/tutorial-load-balancer.md",
             "redirect_url": "/previous-versions/azure/virtual-machines/windows/tutorial-load-balancer",
@@ -185,6 +200,16 @@
             "redirect_url": "/troubleshoot/azure/virtual-machines/rdp",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/virtual-machines/linux/capture-image.md",
+            "redirect_url": "/azure/virtual-machines/capture-image-resource",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-machines/linux/upload-vhd.md",
+            "redirect_url": "/azure/virtual-machines/linux/disks-upload-vhd-to-managed-disk-cli",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/virtual-machines/troubleshooting/redeploy-to-new-node-linux.md",
             "redirect_url": "/troubleshoot/azure/virtual-machines/redeploy-to-new-node-linux",

articles/virtual-machines/TOC.yml

@@ -576,16 +576,8 @@
         displayName: Windows custom images, images, windows, upload, prepare, VHD
         href: ./windows/prepare-for-upload-vhd-image.md
       - name: Generalizing a VM
+        displayName: generalize sysprep deprovision
         href: generalize.md
-      - name: Upload a VHD and create a managed image
-        displayName: Windows custom images, images, windows, upload, prepare, VHD, managed
-        href: ./windows/upload-generalized-managed.md
-      - name: Capture a managed image
-        displayName: Windows custom images, images, windows, upload, prepare, VHD, managed, capture
-        href: ./windows/capture-image-resource.md
-      - name: Create a VM from a managed image
-        displayName: Windows custom images, images, windows, upload, prepare, VHD, create, managed
-        href: ./windows/create-vm-generalized-managed.md
       - name: Visual Studio
         href: /visualstudio/install/using-visual-studio-vm
     - name: VM Image Builder
@@ -674,6 +666,8 @@
       - name: Windows
         displayName: Image builder, images, building, packer
         href: ./windows/build-image-with-packer.md
+    - name: Capture a legacy managed image
+      href: capture-image-resource.md
   - name: Dedicated hosts
     displayName: sole-tenant, sole tenant, isolated, isolation
     items:
@@ -1372,6 +1366,8 @@
       - name: PowerShell
         displayName: Convert disk to another disk type
         href: ./windows/convert-disk-storage.md
+    - name: Migrate AWS and on-premises disk to Azure
+      href: ./windows/on-prem-to-azure.md
     - name: Migrate to premium SSDs with Azure Site Recovery
       items:
       - name: Linux
@@ -1952,16 +1948,11 @@
   - name: Move and migrate VMs
     items:
     - name: Change subscription or resource group
-      items:
-      - name: CLI
-        displayName: Change subscription or resource group
-        href: ./linux/move-vm.md
-      - name: PowerShell
-        displayName: Change subscription or resource group
-        href: ./windows/move-vm.md
-      - name: Change subscription for Marketplace VMs
-        displayName: Change subscription or resource group
-        href: azure-cli-change-subscription-marketplace.md
+      displayName: move migrate
+      href: ../azure-resource-manager/management/move-resource-group-and-subscription.md
+    - name: Change subscription for Marketplace VMs
+      displayName: offer plan sku marketplace
+      href: azure-cli-change-subscription-marketplace.md
     - name: Move VMs to another region
       href: ../site-recovery/azure-to-azure-tutorial-migrate.md?context=/azure/virtual-machines/context/context
     - name: Move to an availability zone
@@ -1970,15 +1961,8 @@
       href: move-region-maintenance-configuration.md
     - name: Move Maintenance Control configuration resources to another region
       href: move-region-maintenance-configuration-resources.md
-    - name: Migrate AWS and on-premises VMs
-      href: ./windows/on-prem-to-azure.md
-      items:
-      - name: Migrate from Amazon Web Services (AWS) to Azure
-        href: ./windows/aws-to-azure.md
-      - name: Upload on-premises VM
-        href: ./linux/upload-vhd.md
-      - name: Use Azure Site Recovery
-        href: ../site-recovery/migrate-overview.md?context=/azure/virtual-machines/context/context
+    - name: Migrate AWS VMs to Azure
+      href: /azure/migrate/tutorial-migrate-aws-virtual-machines
 - name: Infrastructure automation
   items:
   - name: Overview

articles/virtual-machines/capture-image-portal.md

@@ -58,4 +58,4 @@ For images stored in an Azure Compute Gallery (formerly known as Shared Image Ga
 
 ## Next steps
 
-- [Azure Compute Galleries overview](shared-image-galleries.md)	
+- [Azure Compute Galleries overview](shared-image-galleries.md)

articles/virtual-machines/capture-image-resource.md

@@ -1,53 +1,53 @@
 ---
-title: Create a managed image in Azure 
+title: Create a legacy managed image in Azure 
 description: Create a legacy managed image of a generalized VM or VHD in Azure. 
 author: cynthn
 ms.service: virtual-machines
 ms.subservice: imaging
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 02/28/2023
+ms.date: 03/15/2023
 ms.author: cynthn
 ms.custom: legacy
 
 ---
-# Create a managed image of a generalized VM in Azure
+# Create a legacy managed image of a generalized VM in Azure
 
 **Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets 
 
-
-This article covers the older managed image technology. For the most current technology, customers are encouraged to use [Azure Compute Gallery](azure-compute-gallery.md). All new features, like ARM64, Trusted Launch, and Confidential VM  are only supported through Azure Compute Gallery.  If you have an existing managed image, you can use it as a source and create an Azure Compute Gallery image.  For more information, see [Create an image definition and image version](image-version.md).
-
-One managed image supports up to 20 simultaneous deployments. Attempting to create more than 20 VMs concurrently, from the same managed image, may result in provisioning timeouts due to the storage performance limitations of a single VHD. To create more than 20 VMs concurrently, use an [Azure Compute Gallery](shared-image-galleries.md) (formerly known as Shared Image Gallery) image configured with 1 replica for every 20 concurrent VM deployments.
+> [!IMPORTANT]
+> This article covers the older managed image technology. For the most current technology, customers are encouraged to use [Azure Compute Gallery](azure-compute-gallery.md). All new features, like ARM64, Trusted Launch, and Confidential VM  are only supported through Azure Compute Gallery.  If you have an existing managed image, you can use it as a source and create an Azure Compute Gallery image.  For more information, see [Create an image definition and image version](image-version.md).
+>
+> One managed image supports up to 20 simultaneous deployments. Attempting to create more than 20 VMs concurrently, from the same managed image, may result in provisioning timeouts due to the storage performance limitations of a single VHD. To create more than 20 VMs concurrently, use an [Azure Compute Gallery](shared-image-galleries.md) (formerly known as Shared Image Gallery) image configured with 1 replica for every 20 concurrent VM deployments.
 
 For information on how managed images are billed, see [Managed Disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
 
 ## Prerequisites
 
 You need a [generalized](generalize.md) VM in order to create an image.
 
-## Create a managed image from a VM using the portal 
-
-1. Go to the [Azure portal](https://portal.azure.com). Search for and select **Virtual machines**.
-
-2. Select your VM from the list.
-
-3. In the **Virtual machine** page for the VM, on the upper menu, select **Capture**. The **Create an image** page appears.
-4. For **Share image to Azure compute gallery**, select **No, capture only a managed image.**
-5. For **Resource Group**, you can either create the image in the same resource group as the VM or select another resource group in your subscription.
 
-4. For **Name**, either accept the pre-populated name or type your own name for the image.
+## CLI: Create a legacy managed image of a VM
 
-6. If you want to delete the source VM after the image has been created, select **Automatically delete this virtual machine after creating the image**.
-7. 7. If you want the ability to use the image in any [availability zone](../availability-zones/az-overview.md), select **On** for **Zone resiliency**.
-
-8. Select **Create** to create the image.
-
-After the image is created, you can find it as an **Image** resource in the list of resources in the resource group.
+Create a managed image of the VM with [az image create](/cli/azure/image#az-image-create). The following example creates an image named *myImage* in the resource group named *myResourceGroup* using the VM resource named *myVM*.
 
+```azurecli
+az image create \
+   --resource-group myResourceGroup \
+   --name myImage --source myVM
+```
+   
+   > [!NOTE]
+   > The image is created in the same resource group as your source VM. You can create VMs in any resource group within your subscription from this image. From a management perspective, you may wish to create a specific resource group for your VM resources and images.
+   >
+   > If you are capturing an image of a generation 2 VM, also use the `--hyper-v-generation V2` parameter. for more information, see [Generation 2 VMs](generation-2.md).
+   > 
+   > If you would like to store your image in zone-resilient storage, you need to create it in a region that supports [availability zones](../availability-zones/az-overview.md) and include the `--zone-resilient true` parameter.
+   
+This command returns JSON that describes the VM image. Save this output for later reference.
 
 
-## Create a managed image of a VM using PowerShell
+## PowerShell: Create a legacy managed image of a VM
 
 Creating an image directly from the VM ensures that the image includes all of the disks associated with the VM, including the OS disk and any data disks. This example shows how to create a managed image from a VM that uses managed disks.
 
@@ -96,7 +96,7 @@ To create a VM image, follow these steps:
     New-AzImage -Image $image -ImageName $imageName -ResourceGroupName $rgName
     ```	
 
-## Create an image from a managed disk using PowerShell
+## PowerShell: Create a legacy managed image from a managed disk 
 
 If you want to create an image of only the OS disk, specify the managed disk ID as the OS disk:
 
@@ -136,7 +136,7 @@ If you want to create an image of only the OS disk, specify the managed disk ID
     ```	
 
 
-## Create a managed image from a snapshot using PowerShell
+## PowerShell: Create a legacy managed image from a snapshot
 
 You can create a managed image from a snapshot of a generalized VM by following these steps:
 
@@ -169,7 +169,7 @@ You can create a managed image from a snapshot of a generalized VM by following
     ```	
 
 
-## Create a managed image from a VM that uses a storage account
+## PowerShell: Create a legacy managed image from a VM that uses a storage account
 
 To create a managed image from a VM that doesn't use managed disks, you need the URI of the OS VHD in the storage account, in the following format: https://*mystorageaccount*.blob.core.windows.net/*vhdcontainer*/*vhdfilename.vhd*. In this example, the VHD is in *mystorageaccount*, in a container named *vhdcontainer*, and the VHD filename is *vhdfilename.vhd*.
 
@@ -203,11 +203,41 @@ To create a managed image from a VM that doesn't use managed disks, you need the
     ```
 
 
-## Create a VM from a managed image
+## CLI: Create a VM from a legacy managed image
+Create a VM by using the image you created with [az vm create](/cli/azure/vm). The following example creates a VM named *myVMDeployed* from the image named *myImage*.
+
+```azurecli
+az vm create \
+   --resource-group myResourceGroup \
+   --name myVMDeployed \
+   --image myImage\
+   --admin-username azureuser \
+   --ssh-key-value ~/.ssh/id_rsa.pub
+```
+
+## CLI: Create a VM in another resource group from a legacy managed image
+
+You can create VMs from an image in any resource group within your subscription. To create a VM in a different resource group than the image, specify the full resource ID to your image. Use [az image list](/cli/azure/image#az-image-list) to view a list of images. The output is similar to the following example.
+
+```json
+"id": "/subscriptions/guid/resourceGroups/MYRESOURCEGROUP/providers/Microsoft.Compute/images/myImage",
+   "location": "westus",
+   "name": "myImage",
+```
+
+The following example uses [az vm create](/cli/azure/vm#az-vm-create) to create a VM in a resource group other than the source image, by specifying the image resource ID.
+
+```azurecli
+az vm create \
+   --resource-group myOtherResourceGroup \
+   --name myOtherVMDeployed \
+   --image "/subscriptions/guid/resourceGroups/MYRESOURCEGROUP/providers/Microsoft.Compute/images/myImage" \
+   --admin-username azureuser \
+   --ssh-key-value ~/.ssh/id_rsa.pub
+```
 
-One managed image supports up to 20 simultaneous deployments. Attempting to create more than 20 VMs concurrently, from the same managed image, may result in provisioning timeouts due to the storage performance limitations of a single VHD. To create more than 20 VMs concurrently, use an [Azure Compute Gallery](shared-image-galleries.md) (formerly known as Shared Image Gallery) image configured with 1 replica for every 20 concurrent VM deployments.
 
-### Portal
+## Portal: Create a VM from a legacy managed image
 
 1. Go to the [Azure portal](https://portal.azure.com) to find a managed image. Search for and select **Images**.
 3. Select the image you want to use from the list. The image **Overview** page opens.
@@ -218,7 +248,7 @@ One managed image supports up to 20 simultaneous deployments. Attempting to crea
 8. On the summary page, you should see your image name listed as a **Private image**. Select **Ok** to start the virtual machine deployment.
 
 
-### PowerShell
+## PowerShell: Create a VM from a legacy managed image
 
 You can use PowerShell to create a VM from an image by using the simplified parameter set for the [New-AzVm](/powershell/module/az.compute/new-azvm) cmdlet. The image needs to be in the same resource group where you'll create the VM.
 

articles/virtual-machines/generalize.md

@@ -6,7 +6,7 @@ ms.service: virtual-machines
 ms.subservice: imaging
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 05/13/2022
+ms.date: 03/15/2023
 ms.author: cynthn
 ms.custom: portal
 
@@ -114,3 +114,7 @@ Once Sysprep has finished, set the status of the virtual machine to **Generalize
 ```azurepowershell-interactive
 Set-AzVm -ResourceGroupName $rgName -Name $vmName -Generalized
 ```
+
+## Next steps
+
+- Learn more about [Azure Compute Gallery](shared-image-galleries.md).