Consolidating managed image stuff

Author: cynthn

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

@@ -4889,6 +4889,21 @@
             "redirect_url": "/previous-versions/azure/virtual-machines/tag-template",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/virtual-machines/windows/create-vm-generalized-managed.md",
+            "redirect_url": "/azure/virtual-machines/vm-generalized-image-version",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/virtual-machines/windows/upload-generalized-managed.md",
+            "redirect_url": "/azure/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/virtual-machines/windows/capture-image-resource.md",
+            "redirect_url": "/azure/virtual-machines/capture-image-resource",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/virtual-machines/workloads/sap/baremetal-infrastructure-portal.md",
             "redirect_url": "/azure/baremetal-infrastructure/connect-baremetal-infrastructure",

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

@@ -1,26 +1,27 @@
 ---
 title: Create a managed image in Azure 
-description: Create a managed image of a generalized VM or VHD in Azure. Images can be used to create multiple VMs that use managed disks. 
+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/24/2022
+ms.date: 02/28/2023
 ms.author: cynthn
 ms.custom: legacy
-ms.collection: windows
 
 ---
 # Create a managed image of a generalized VM in Azure
 
-**Applies to:** :heavy_check_mark: Windows VMs 
+**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets 
 
 
-Managed images are helpful in development and test environments where you need a consistent baseline VM. A managed image resource can be created from a generalized virtual machine (VM) that is stored as either a managed disk or an unmanaged disk in a storage account. The image can then be used to create multiple VMs. For information on how managed images are billed, see [Managed Disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/). 
+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.
@@ -201,6 +202,46 @@ To create a managed image from a VM that doesn't use managed disks, you need the
 	$image = New-AzImage -ImageName $imageName -ResourceGroupName $rgName -Image $imageConfig
     ```
 
+
+## Create a VM from a managed image
+
+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
+
+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.
+4. Select **Create VM** from the menu.
+5. Enter the virtual machine information. The user name and password entered here will be used to log in to the virtual machine. When complete, select **OK**. You can create the new VM in an existing resource group, or choose **Create new** to create a new resource group to store the VM.
+6. Select a size for the VM. To see more sizes, select **View all** or change the **Supported disk type** filter. 
+7. Under **Settings**, make changes as necessary and select **OK**. 
+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
+
+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.
+
+ 
+
+The simplified parameter set for [New-AzVm](/powershell/module/az.compute/new-azvm) only requires that you provide a name, resource group, and image name to create a VM from an image. New-AzVm will use the value of the **-Name** parameter as the name of all of the resources that it creates automatically. In this example, we provide more detailed names for each of the resources but let the cmdlet create them automatically. You can also create resources beforehand, such as the virtual network, and pass the resource name into the cmdlet. New-AzVm will use the existing resources if it can find them by their name.
+
+The following example creates a VM named *myVMFromImage*, in the *myResourceGroup* resource group, from the image named *myImage*. 
+
+
+```azurepowershell-interactive
+New-AzVm `
+    -ResourceGroupName "myResourceGroup" `
+    -Name "myVMfromImage" `
+	-ImageName "myImage" `
+    -Location "East US" `
+    -VirtualNetworkName "myImageVnet" `
+    -SubnetName "myImageSubnet" `
+    -SecurityGroupName "myImageNSG" `
+    -PublicIpAddressName "myImagePIP" 
+```
+
+
 
 ## Next steps
 - [Create a VM from a managed image](create-vm-generalized-managed.md).	

articles/virtual-machines/windows/create-vm-generalized-managed.md

@@ -1,51 +1,27 @@
 ---
-title: Create a VM from an uploaded generalized Windows VHD 
-description: Upload a generalized Windows VHD to Azure and use it to create new VMs, in the Resource Manager deployment model.
+title: Upload a VHD to Azure 
+description: Upload a VHD to Azure to use as a basis for images for creating new virtual machines.
 author: cynthn
 ms.service: virtual-machines
 ms.subservice: imaging
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 12/12/2019
+ms.date: 02/28/2023
 ms.author: cynthn 
 ms.custom: devx-track-azurepowershell
 ---
 
-# Upload a generalized Windows VHD and use it to create new VMs in Azure
+# Upload a VHD
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets 
 
-This article walks you through using PowerShell to upload a VHD of a generalized VM to Azure, create an image from the VHD, and create a new VM from that image. You can upload a VHD exported from an on-premises virtualization tool or from another cloud. Using [Managed Disks](../managed-disks-overview.md) for the new VM simplifies the VM management and provides better availability when the VM is placed in an availability set. 
+This article walks you through using PowerShell to upload a VHD of a generalized VM to Azure. You can upload a VHD exported from an on-premises virtualization tool or from another cloud. Uploading to a managed disk simplifies the eventual creation of a [image](image-version.md) you can use to create multiple VMs.
 
-For a sample script, see [Sample script to upload a VHD to Azure and create a new VM](/previous-versions/azure/virtual-machines/scripts/virtual-machines-windows-powershell-upload-generalized-script).
 
 ## Before you begin
 
-- Before uploading any VHD to Azure, you should follow [Prepare a Windows VHD or VHDX to upload to Azure](prepare-for-upload-vhd-image.md).
-- Review [Plan for the migration to Managed Disks](on-prem-to-azure.md#plan-for-the-migration-to-managed-disks) before starting your migration to [Managed Disks](../managed-disks-overview.md).
-
- 
-## Generalize the source VM by using Sysprep
-
-If you haven't already, you need to Sysprep the VM before uploading the VHD to Azure. Sysprep removes all your personal account information, among other things, and prepares the machine to be used as an image. For details about Sysprep, see the [Sysprep Overview](/windows-hardware/manufacture/desktop/sysprep--system-preparation--overview).
-
-Make sure the server roles running on the machine are supported by Sysprep. For more information, see [Sysprep Support for Server Roles](/windows-hardware/manufacture/desktop/sysprep-support-for-server-roles).
-
-> [!IMPORTANT]
-> If you plan to run Sysprep before uploading your VHD to Azure for the first time, make sure you have [prepared your VM](prepare-for-upload-vhd-image.md). 
-> 
-> 
-
-1. Sign in to the Windows virtual machine.
-1. Open the Command Prompt window as an administrator. 
-1. Delete the panther directory (C:\Windows\Panther).
-1. Change the directory to %windir%\system32\sysprep, and then run `sysprep.exe`.
-1. In the **System Preparation Tool** dialog box, select **Enter System Out-of-Box Experience (OOBE)**, and make sure that the **Generalize** check box is enabled.
-1. For **Shutdown Options**, select **Shutdown**.
-1. Select **OK**.
-   
-    ![Start Sysprep](./media/upload-generalized-managed/sysprepgeneral.png)
-1. When Sysprep finishes, it shuts down the virtual machine. Do not restart the VM.
+- Before uploading a Linux VHD to Azure, review [Bringing and creating Linux images in Azure](./linux/imaging.md)
+- Before uploading a Windows VHD to Azure, you should follow [Prepare a Windows VHD or VHDX to upload to Azure](prepare-for-upload-vhd-image.md).
 
 
 ## Upload the VHD