Merge pull request #312182 from RochakSingh-blr/24-feb-update-cycle-changes

RM update cycle for stale articles

Author: prmerger-automator[bot]

articles/resource-mover/about-move-process.md

@@ -6,7 +6,7 @@ ms.author: v-rochak2
 ms.service: azure-resource-mover
 ms.topic: overview
 ms.date: 07/31/2025
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 ms.custom: UpdateFrequency.5
 # Customer intent: "As an Azure administrator, I want to understand the process of moving resources across regions, so that I can effectively manage dependencies and minimize downtime during the transition."
 ---

articles/resource-mover/common-questions.md

@@ -7,7 +7,7 @@ ms.service: azure-resource-mover
 ms.custom: engagement-fy23, UpdateFrequency.5
 ms.topic: faq
 ms.date: 07/31/2025
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 # Customer intent: As an Azure user, I want to understand the capabilities and limitations of the Azure Resource Mover, so that I can effectively plan and execute resource migrations across regions and subscriptions.
 ---
 

articles/resource-mover/overview.md

@@ -6,7 +6,7 @@ ms.author: v-rochak2
 ms.date: 07/31/2025
 ms.service: azure-resource-mover
 ms.topic: overview
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 ms.custom: mvc, engagement-fy23, UpdateFrequency.5
 # Customer intent: As an Azure administrator, I want to understand how Resource Mover simplifies the process of relocating Azure resources across regions, so that I can efficiently manage my resources in response to strategic business needs and compliance requirements.
 ---

articles/resource-mover/select-options-to-move-resources.md

@@ -6,7 +6,7 @@ ms.author: v-rochak2
 ms.date: 07/31/2025
 ms.service: azure-resource-mover
 ms.topic: overview
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 ms.custom: mvc, engagement-fy23, UpdateFrequency.5
 # Customer intent: As an Azure administrator, I want to compare the available tools for moving resources across regions, so that I can select the most suitable option for efficiently relocating my Azure resources based on their dependencies and requirements.
 ---

articles/resource-mover/support-matrix-extension-resource-types.md

@@ -6,7 +6,7 @@ ms.author: v-rochak2
 ms.date: 07/31/2025
 ms.service: azure-resource-mover
 ms.topic: concept-article
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 ms.custom: UpdateFrequency.5
 
 # Customer intent: "As a cloud architect, I want to understand which extension resource types are supported during region migrations, so that I can plan and execute effective resource relocations without encountering unsupported configurations."

articles/resource-mover/support-matrix-move-region-azure-vm.md

@@ -6,7 +6,7 @@ ms.author: v-rochak2
 ms.date: 07/31/2025
 ms.service: azure-resource-mover
 ms.topic: how-to
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 ms.custom: engagement-fy23, UpdateFrequency.5, linux-related-content
 # Customer intent: As a cloud administrator, I want to understand the prerequisites and supported configurations for moving Azure VMs between regions using Resource Mover, so that I can ensure a successful migration process without service interruptions.
 ---
@@ -28,11 +28,11 @@ Windows Server 2019 | Supported for Server Core, Server with Desktop Experience.
 Windows Server 2016  | Supported Server Core, Server with Desktop Experience.
 Windows Server 2012 R2 | Supported.
 Windows Server 2012 | Supported.
-Windows Server 2008 R2 with SP1/SP2 | Supported.<br/><br/> For machines running Windows Server 2008 R2 with SP1/SP2, you need to install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419).  SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
+Windows Server 2008 R2 with SP1/SP2 | Supported.<br/><br/> For machines running Windows Server 2008 R2 with SP1/SP2, you need to install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419). SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
 Windows 10 (x64) | Supported.
 Windows 8.1 (x64) | Supported.
 Windows 8 (x64) | Supported.
-Windows 7 (x64) with SP1 onwards | Install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows 7 with SP1.  SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the 'prepare' step won't succeed. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
+Windows 7 (x64) with SP1 onwards | Install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows 7 with SP1. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the 'prepare' step won't succeed. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
 
 
 ## Linux VM support
@@ -119,12 +119,12 @@ This table summarized support for the Azure VM OS disk, data disk, and temporary
 
 **Component** | **Support** | **Details**
 --- | --- | ---
-OS disk maximum size | 2048 GB | [Learn more](/azure/virtual-machines/managed-disks-overview) about VM disks.
+OS disk maximum size | 2,048 GB | [Learn more](/azure/virtual-machines/managed-disks-overview) about VM disks.
 Temporary disk | Not supported | The temporary disk is always excluded from the prepare process.<br/><br/> Don't store any persistent data on the temporary disk. [Learn more](/azure/virtual-machines/managed-disks-overview#temporary-disk).
-Data disk maximum size | 8192 GB for managed disks
+Data disk maximum size | 8,192 GB for managed disks
 Data disk minimum size |  2 GB for managed disks |
 Data disk maximum number | Up to 64, in accordance with support for a specific Azure VM size | [Learn more](/azure/virtual-machines/sizes) about VM sizes.
-Data disk change rate | Maximum of 10 MBps per disk for premium storage. Maximum of 2 MBps per disk for Standard storage. | If the average data change rate on the disk is continuously higher than the maximum, the preparation won't catch up.<br/><br/>  However, if the maximum is exceeded sporadically, preparation can catch up, but you might see slightly delayed recovery points.
+Data disks change rate | Maximum of 10 MBps per disk for premium storage. Maximum of 2 MBps per disk for Standard storage. | If the average data change rate on the disk is continuously higher than the maximum, the preparation won't catch up.<br/><br/>  However, if the maximum is exceeded sporadically, preparation can catch up, but you might see slightly delayed recovery points.
 Data disk (Standard storage account) | Not supported. | Change the storage type to managed disk, and then try moving the VM.
 Data disk (Premium storage account) | Not supported | Change the storage type to managed disk, and then try moving the VM.
 Managed disk (Standard) | Supported  |
@@ -146,7 +146,7 @@ Premium P10 or P15 disk | 8 KB    | 2 MB/s | 168 GB per disk
 Premium P10 or P15 disk | 16 KB | 4 MB/s |    336 GB per disk
 Premium P10 or P15 disk | 32 KB or greater | 8 MB/s | 672 GB per disk
 Premium P20 or P30 or P40 or P50 disk | 8 KB    | 5 MB/s | 421 GB per disk
-Premium P20 or P30 or P40 or P50 disk | 16 KB or greater |20 MB/s | 1684 GB per disk
+Premium P20 or P30 or P40 or P50 disk | 16 KB or greater |20 MB/s | 1,684 GB per disk
 
 ## Supported VM networking settings
 
@@ -186,7 +186,7 @@ If you're using a network security group (NSG) rules to control outbound connect
     - **EventHub*
     - *AzureKeyVault*
     - *GuestAndHybridManagement*
-- We recommend you test rules in a non-production environment. [Review some examples](../site-recovery/azure-to-azure-about-networking.md#outbound-connectivity-using-service-tags).
+- We recommend you test rules in a nonproduction environment. [Review some examples](../site-recovery/azure-to-azure-about-networking.md#outbound-connectivity-using-service-tags).
 
 ## Next steps
 

articles/resource-mover/support-matrix-move-region-sql.md

@@ -6,7 +6,7 @@ ms.author: v-rochak2
 ms.date: 07/31/2025
 ms.service: azure-resource-mover
 ms.topic: concept-article
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 ms.custom: UpdateFrequency.5
 # Customer intent: As a database administrator, I want to understand the support and limitations for moving Azure SQL resources between regions, so that I can effectively plan and execute resource relocations while ensuring compliance with feature availability and prerequisites.
 ---

articles/resource-mover/whats-new.md

@@ -7,7 +7,7 @@ ms.date: 07/31/2025
 ms.service: azure-resource-mover
 ms.topic: whats-new 
 ms.custom: UpdateFrequency.5
-ms.update-cycle: 180-days
+ms.update-cycle: 365-days
 # Customer intent: "As a cloud administrator, I want to utilize the features of Azure Resource Mover for managing resource migrations across subscriptions and regions, so that I can streamline the organization and billing of our cloud resources."
 ---