Merge pull request #34584 from MikeRayMSFT/250701-css-move-resource-license

CSS: Add licensing and ESU for move.

Author: JamesJBarnett

docs/sql-server/azure-arc/media/move-resources/machine-azure-arc.png

@@ -1,10 +1,10 @@
 ---
-title: Move resources to a new resource group or subscription
+title: Move Resources to a New Resource Group or Subscription
 description: This article explains how to move resources to a new resource group or subscription for SQL Server enabled by Azure Arc.
 author: MikeRayMSFT
 ms.author: mikeray
-ms.reviewer: mikeray, randolphwest
-ms.date: 09/09/2024
+ms.reviewer: sashan
+ms.date: 07/08/2025
 ms.topic: how-to
 ms.custom:
   - build-2025
@@ -17,20 +17,26 @@ This article describes how you can move resources to a new resource group or sub
 - SQL Server instances
 - Databases
 
+Before you begin, review [Known limitations](#known-limitations).
+
 ## Requirements
 
 To complete this task, make sure that:
 
 - The *Machine - Azure Arc* resource and all SQL Server instances are in the same resource group.
-
 - The new subscription or resource group needs to meet all [prerequisites](prerequisites.md).
 
 In addition:
 
 - If Microsoft Purview is enabled, you must disable it in the compliance portal before the move.
 - If best practices assessment is enabled, you must disable it before the move.
+- SQL Server license and SQL Server extended security update license aren't moved automatically.
+
+After the move:
 
-After the move, you can reenable any features that you disabled.
+1. Reenable any features that you disabled.
+1. Configure SQL Server license in the new location.
+1. Configure ESU in the new location.
 
 ## Move resources to a new resource group or subscription
 
@@ -96,3 +102,21 @@ The following steps explain how to reconfigure best practices assessment after a
 1. Update the Log Analytics workspace with one from the new subscription and then enable best practices assessment.
 
 Moving to a different subscription requires manual reconfiguration with the preceding steps for all SQL Server instances affected for best practices assessment.
+
+## Known limitations
+
+Moving the SQL Server p-core license to the new subscription or resource group is currently not supported. You'll need to:
+
+1. Manually delete the old license
+1. Re-create and reconfigure the license in the new location
+
+  For details, review [Manage the unlimited virtualization benefit for SQL Server](manage-configuration.md#manage-pcore-license).
+
+Moving the SQL Server ESU p-core license to the new subscription or resource group is currently not supported. If you create a license in the location, it will be treated as a new ESU subscription with a new back-billing charge.
+
+> [!IMPORTANT]  
+> While moving the VMs with ESU enabled to a new subscription or resource group is supported, if they used to be covered by a SQL Server ESU p-core license in the old location and not billed individually, the move will result in these VMs being billed for ESU individually as they will no longer be covered by a p-core license.
+
+## Related content
+
+- [Manage inventory of SQL Server resources with Azure Arc](view-inventory.md)