Merge pull request #265092 from mattmcinnes/patch-105

Court72 · web-flow · commit 698a91a317a3 · 2024-02-02T15:24:47.000-07:00
Update retirement-overview.md
diff --git a/articles/virtual-machines/sizes/previous-gen-sizes-list.md b/articles/virtual-machines/sizes/previous-gen-sizes-list.md
@@ -1,78 +1,73 @@
 ---
-title: Previous generation Azure VM sizes 
+title: Previous generation Azure VM size series
 description: A list containing all previous generation and capacity limited VM size series.
 author: mattmcinnes
 ms.service: virtual-machines
 ms.subservice: sizes
 ms.topic: conceptual
-ms.date: 01/31/2024
+ms.date: 02/02/2024
 ms.author: mattmcinnes
 ms.reviewer: iamwilliew
 ---
 
-# Previous generation Azure VM sizes 
+# Previous generation Azure VM size series
 
-This article provides a list of all sizes that are considered *previous-gen* or *capacity limited*. For sizes that require it there are *migration guides* to help move to replacement sizes.
-
-To learn more about size series retirement, see the [size series retirement overview](./retirement-overview.md).
+This article provides a list of all size series that are considered *previous-gen*. Status is listed as *next-gen available* or *capacity limited* based on capacity. For sizes that require it there are *migration guides* to help move to replacement sizes.
 
 > [!NOTE]
-> *Previous generation* and *capacity limited* sizes **are not currently retired** and can still be used.
-
-## What are previous-gen sizes?
-Previous generations virtual machine sizes can still be used, but there are newer generations available. Capacity increases are not guaranteed for previous-gen sizes. It's recommended to migrate to the latest generation replacements.
-
-## What are capacity limited previous-gen sizes?
-Capacity limited virtual machine sizes are older sizes which are still fully supported, but they won't receive more capacity. Unlike other size series which will be deployed based on demand, capacity limited sizes are limited to what is currently deployed and decreases as hardware is phased out. There are newer or alternative sizes that are generally available.
+> Series listed as *previous-gen* are **not currently retired** and can still be used.
 
+## What are previous-gen size series?
+Previous generations virtual machine size series are running on older hardware. While they can still be used and are fully supported, there are newer generations available. It's recommended to migrate to the latest generation replacements.
 
+To learn more about previous-gen sizes, retirement, and the status states of previous-gen size series, see the [size series retirement overview](./retirement-overview.md).
 
 ## General purpose previous-gen sizes
 
 |Series name                 | Status                 | Migration guide   |
 |----------------------------|------------------------|-------------------|
-| Basic A-series             | Capacity limited       |
-| Standard A-series          | Capacity limited       |
-| Compute-intensive A-series | Capacity limited       |
-| Standard D-series          | Capacity limited       | 
-| Preview DC-series          | Capacity limited       |
-| DS-series                  | Capacity limited       |
+| Basic A-series             | [Capacity limited](./retirement-overview.md#capacity-limited) |
+| Standard A-series          | [Capacity limited](./retirement-overview.md#capacity-limited) |
+| Compute-intensive A-series | [Capacity limited](./retirement-overview.md#capacity-limited) |
+| Standard D-series          | [Capacity limited](./retirement-overview.md#capacity-limited) | 
+| Preview DC-series          | [Capacity limited](./retirement-overview.md#capacity-limited) |
+| DS-series                  | [Capacity limited](./retirement-overview.md#capacity-limited) |
 
 For a list of general purpose sizes listed as "retired" and "announced for retirement" (sizes that are no longer available or soon to be unavailable for use), see [retired general purpose sizes](./retired-sizes-list.md#general-purpose-retired-sizes).
 
 ## Compute optimized previous-gen sizes
 
 |Series name                | Status                  | Migration guide   |
 |---------------------------|-------------------------|-------------------|
-| F-series                  | Previous-gen            |                   |
-| Fs-series                 | Previous-gen            |                   |
+| F-series                  | [Next-gen available](./retirement-overview.md#next-gen-available) |                   |
+| Fs-series                 | [Next-gen available](./retirement-overview.md#next-gen-available) |                   |
 
 For a list of compute optimized sizes listed as "retired" and "announced for retirement" (sizes that are no longer available or soon to be unavailable for use), see [retired compute optimized sizes](./retired-sizes-list.md#compute-optimized-retired-sizes).
 
 ## Memory optimized previous-gen sizes
 
 |Series name                | Replacement series      |Migration guide |
 |---------------------------|-------------------------|----------------|
-| GS-series                 | Capacity limited        |                |
-| G-series                  | Capacity limited        |                |
-| Memory-optimized D-series | Capacity limited        |                |
-| Memory-optimized DS-series| Capacity limited        |                |
+| GS-series                 | [Capacity limited](./retirement-overview.md#capacity-limited)  |                |
+| G-series                  | [Capacity limited](./retirement-overview.md#capacity-limited)  |                |
+| Memory-optimized D-series | [Capacity limited](./retirement-overview.md#capacity-limited)  |                |
+| Memory-optimized DS-series| [Capacity limited](./retirement-overview.md#capacity-limited)  |                |
 
 For a list of memory optimized sizes listed as "retired" and "announced for retirement" (sizes that are no longer available or soon to be unavailable for use), see [retired memory optimized sizes](./retired-sizes-list.md#memory-optimized-retired-sizes).
 
 ## Storage optimized previous-gen sizes
 
 |Series name                | Replacement series   | Migration guide|
 |---------------------------|----------------------|----------------|
-| Ls-series                 | Capacity limited     |                |
+| Ls-series                 | [Capacity limited](./retirement-overview.md#capacity-limited) |                |
 
 For a list of storage optimized sizes listed as "retired" and "announced for retirement" (sizes that are no longer available or soon to be unavailable for use), see [retired storage optimized sizes](./retired-sizes-list.md#storage-optimized-retired-sizes).
 
 ## GPU accelerated previous-gen sizes
 
 |Series name                 | Status                 | Migration guide   |
 |----------------------------|------------------------|-------------------|
-| NVv2-series                | Previous-gen           |                   |
+| NVv2-series                | [Next-gen available](./retirement-overview.md#next-gen-available) |                   |
 
 For a list of GPU accelerated sizes listed as "retired" and "announced for retirement" (sizes that are no longer available or soon to be unavailable for use), see [retired GPU accelerated sizes](./retired-sizes-list.md#gpu-accelerated-retired-sizes).
 
diff --git a/articles/virtual-machines/sizes/retired-sizes-list.md b/articles/virtual-machines/sizes/retired-sizes-list.md
@@ -1,29 +1,33 @@
 ---
-title: Retired Azure VM sizes 
+title: Retired Azure VM size series 
 description: A list containing all retired and soon to be retired VM size series and their replacement series.
 author: mattmcinnes
 ms.service: virtual-machines
 ms.subservice: sizes
 ms.topic: conceptual
-ms.date: 01/31/2024
+ms.date: 02/02/2024
 ms.author: mattmcinnes
 ms.reviewer: iamwilliew
 ---
 
-# Retired Azure VM sizes 
+# Retired Azure VM size series
 
 This article provides a list of all sizes that are retired or have been announced for retirement. For sizes that require it there are migration guides to help move to replacement sizes.
 
-To learn more about size series retirement, see the [size series retirement overview](./retirement-overview.md).
+> [!WARNING]
+> Series with *Retirement Status* listed as *Retired* are **no longer available** and can't be provisioned.
 
-> [!NOTE]
-> Series with *Retirement Status* listed as **Retired** are **no longer available** and can't be provisioned.
->
-> If you are currently using one of the size series listed as *Retired*, view the migration guide to switch to a replacement series as soon as possible.
+## What are retired size series?
+Retired virtual machine size series are running on older hardware which is no longer supported. The hardware will be replaced with newer generations of hardware.
+
+Series with *Retirement Status* listed as *Announced* are still available, but will be retired on the *Planned Retirement Date*. It's recommended that you plan your migration to a replacement series well before the listed retirement date.
 
-Series with *Retirement Status* listed as **Announced** are still available, but will be retired on the *Planned Retirement Date*. It's recommended that you plan your migration to a replacement series well before the listed retirement date.
+To learn more about size series retirement, previous-gen sizes, and the retirement process, see the [size series retirement overview](./retirement-overview.md).
+
+> [!IMPORTANT] 
+> If you are currently using one of the size series listed as *Retired*, view the migration guide to switch to a replacement series as soon as possible.
 
-*Capacity limited* series and *previous-gen* series are not retired and still fully supported, but they have limitations similar to series that are announced for retirement. For a list of previous-gen sizes, see [previous generation Azure VM sizes](./previous-gen-sizes-list.md).
+*Previous-gen* size series are not retired and still fully supported, but they have limitations similar to series that are announced for retirement. For a list of previous-gen sizes, see [previous generation Azure VM sizes](./previous-gen-sizes-list.md).
 
 ## General purpose retired sizes
 
@@ -49,8 +53,8 @@ Currently there are no retired storage optimized series retired or announced for
 |-------------------|-------------------|-----------------------------|-------------------------|-----------------|
 | NV-Series         | **Retired**       | -                           | 9/6/23                  | [NV-series Retirement](./migration-guides/nv-series-retirement.md)    |
 | NC-Series         | **Retired**       | -                           | 9/6/23                  | [NC-series Retirement](./migration-guides/nc-series-retirement.md)    |
-| NCv2-Series       | **Retired**       | -                           | 9/6/23                  | [NC-series Retirement](./migration-guides/ncv2-series-retirement.md)  |
-| ND-Series         | **Retired**       | -                           | 9/6/23                  | [NC-series Retirement](./migration-guides/nd-series-retirement.md)    |
+| NCv2-Series       | **Retired**       | -                           | 9/6/23                  | [NCv2-series Retirement](./migration-guides/ncv2-series-retirement.md)  |
+| ND-Series         | **Retired**       | -                           | 9/6/23                  | [ND-series Retirement](./migration-guides/nd-series-retirement.md)    |
 
 ## FPGA accelerated retired sizes
 
diff --git a/articles/virtual-machines/sizes/retirement-overview.md b/articles/virtual-machines/sizes/retirement-overview.md
@@ -1,38 +1,64 @@
 ---
 title: Previous-gen and retired VM sizes
-description: Overview of the retirement process for virtual machine sizes and information on previous-gen sizes.
+description: Overview of the retirement process for virtual machine size series and information on previous-gen sizes.
 author: mattmcinnes
 ms.service: virtual-machines
 ms.subservice: sizes
 ms.topic: overview
-ms.date: 01/31/2024
+ms.date: 02/02/2024
 ms.author: mattmcinnes
 ms.reviewer: iamwilliew
 ---
 
-# Previous-gen and retired VM sizes
+# Previous-gen and retired VM size series
 
- This process requires that previously established VM sizes are moved to "previous-gen" status, then eventually retired and made unavailable. This article provides an overview of the retirement of virtual machine sizes and explains the reasoning behind this process.
+Azure virtual machine sizes are the amount of resources allocated to a virtual machine in the cloud. These resources are a portion of the physical server’s hardware capabilities. A *size series* is a collection of all sizes that are available within a single physical server’s hardware. As a size series' physical hardware ages and newer components are released, Microsoft stops deploying more of previously established series' hardware. Once users migrate off of said hardware or the hardware becomes sufficiently outdated, it's retired to make room for new infrastructure.
 
 ![A diagram showing a greyed out Azure VM icon with an arrow pointing to a new sparkling Azure VM icon.](./media/size-retirement-new-vm.png "Moving from old to new VM sizes")
 
-When hardware begins the retirement process, it's recommended to migrate workloads to newer generation hardware that provides better performance and reliability. This helps you to avoid any potential issues that may arise from using outdated hardware. By keeping your hardware up-to-date, you can ensure that your workloads are running smoothly and efficiently.
+When hardware becomes *previous-gen* or begins the retirement process, we recommend migrating workloads to newer generation hardware. Newer hardware provides better performance and future scalability. Migrating also helps you to avoid any potential issues that may arise from using outdated hardware. By keeping your hardware up-to-date, you can ensure that your workloads are running smoothly and efficiently.
+
+This article describes the various states of older hardware and explains the processes behind these states.
 
 ## Previous-gen sizes
 
-Previous generation sizes **are not currently retired** and can still be used. These sizes are still fully supported, but they won't receive more capacity. It's recommended to migrate to the latest generation replacements as soon as possible. For a list of sizes that are considered "previous-gen", see the [list of previous-gen sizes](./previous-gen-sizes-list.md). 
+Previous generation size series **are not currently retired** and can still be used. These sizes are still fully supported, but they aren't guaranteed to receive more capacity. We recommend migrating to the latest generation replacements as soon as possible, especially when trying to scale up your installations.
+
+There are two types of previous-gen sizes; *next-gen available* and *capacity limited*.
+
+### Next-gen available
+
+Size series listed as *next-gen available* means that while no capacity limitation plans have been made, there are sufficient deployments of newer alternative sizes to justify considering these series "previous-gen". *Next-gen available* series have no formal announcement of retirement timelines, but they'll eventually be retired.
+
+For a list of previous-gen size series that are considered *next-gen available*, see the [list of previous-gen sizes](./previous-gen-sizes-list.md).
+
+### Capacity limited
+
+Size series listed as *capacity limited* means that while no retirement plans have been made, no extra capacity for this series will be deployed. Similar to *next-gen available* previous-gen series, there are sufficient deployments of newer alternative sizes available to replace *capacity limited* size deployments.
+
+If you had one VM running on a *capacity limited* size and require another VM of a similar size in the same series, there is no guarantee that capacity will be able to fulfill this request. Any new VMs should be created using sizes in [series that aren't considered previous-gen](../sizes.md). Migrating to sizes considered *next-gen available* is not recommended since these sizes are also similarly outdated.
+
+For a list of previous-gen size series that are considered *capacity limited*, see the [list of previous-gen sizes](./previous-gen-sizes-list.md). 
 
 ## Retired sizes
 
-Retiring hardware is necessary over time to ensure that the latest and greatest technology is available on Azure. This ensures that the hardware is reliable, secure, and efficient. It also allows for the latest features and capabilities that may not be present on previous generations of hardware.
+Retired size series are **no longer available** and can't be used. If you have VMs running on sizes that are considered *retired*, migrate to a newer next-gen size as soon as possible.
+
+Retiring hardware is necessary over time to ensure that the latest and greatest technology is available on Azure. Retirement ensures that the hardware is reliable, secure, and efficient. It also allows for the latest features and capabilities that may not be present on previous generations of hardware.
 
-Retired sizes are **no longer available** and can't be used. For a list of retired sizes, see the [list of retired sizes](./retired-sizes-list.md).
+Hardware which is currently listed as *previous-gen* are often preparing for retirement which will be announced formally prior to the retirement date.
+
+For information on size series that have been retired or are scheduled for retirement, see the [list of retired sizes](./retired-sizes-list.md).
 
 ## Migrate to newer sizes
 
-Migrating to newer sizes allows you to keep up with the latest hardware available on Azure. You can [resize your VM](./resize-vm.md) to a newer size using the Azure portal, Azure PowerShell, Azure CLI, or Terraform.
+Migrating to newer sizes allows you to keep up with the latest hardware and features available on Azure.
+
+Some size series have specific migration instructions due to the unique hardware or software features. To see a list of migration guide, see [retired size migration guides](./retired-sizes-list.md) and [previous-gen size migration guides](./previous-gen-sizes-list.md).
+
+For sizes without specific instructions, you can [resize your VM](./resize-vm.md) to a newer size using the Azure portal, Azure PowerShell, Azure CLI, or Terraform. Make sure that the new size has support for all features that your workload requires.
 
 ## Next steps
 - For more information on VM sizes, see [Sizes for virtual machines in Azure](../sizes.md).
 - For a list of retired sizes, see [Retired Azure VM sizes](./retired-sizes-list.md).
-- For a list of previous-gen sizes, see [Previous generation Azure VM sizes](./previous-gen-sizes-list.md).
+- For a list of previous-gen sizes, see [Previous generation Azure VM sizes](./previous-gen-sizes-list.md).
