Skip to content

Commit 0d65507

Browse files
committed
Update move resource license
1 parent 1eee35e commit 0d65507

File tree

2 files changed

+29
-5
lines changed

2 files changed

+29
-5
lines changed
-53.4 KB
Loading

docs/sql-server/azure-arc/move-resources.md

Lines changed: 29 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Move resources to a new resource group or subscription
2+
title: Move Resources to a New Resource Group or Subscription
33
description: This article explains how to move resources to a new resource group or subscription for SQL Server enabled by Azure Arc.
44
author: MikeRayMSFT
55
ms.author: mikeray
6-
ms.reviewer: mikeray, randolphwest
7-
ms.date: 09/09/2024
6+
ms.reviewer: sashan
7+
ms.date: 07/08/2025
88
ms.topic: how-to
99
ms.custom:
1010
- build-2025
@@ -17,20 +17,26 @@ This article describes how you can move resources to a new resource group or sub
1717
- SQL Server instances
1818
- Databases
1919

20+
Before you begin, review [Known limitations](#known-limitations).
21+
2022
## Requirements
2123

2224
To complete this task, make sure that:
2325

2426
- The *Machine - Azure Arc* resource and all SQL Server instances are in the same resource group.
25-
2627
- The new subscription or resource group needs to meet all [prerequisites](prerequisites.md).
2728

2829
In addition:
2930

3031
- If Microsoft Purview is enabled, you must disable it in the compliance portal before the move.
3132
- If best practices assessment is enabled, you must disable it before the move.
33+
- SQL Server license and SQL Server extended security update license aren't moved automatically.
34+
35+
After the move:
3236

33-
After the move, you can reenable any features that you disabled.
37+
1. Reenable any features that you disabled.
38+
1. Configure SQL Server license in the new location.
39+
1. Configure ESU in the new location.
3440

3541
## Move resources to a new resource group or subscription
3642

@@ -96,3 +102,21 @@ The following steps explain how to reconfigure best practices assessment after a
96102
1. Update the Log Analytics workspace with one from the new subscription and then enable best practices assessment.
97103

98104
Moving to a different subscription requires manual reconfiguration with the preceding steps for all SQL Server instances affected for best practices assessment.
105+
106+
## Known limitations
107+
108+
Moving the SQL Server p-core license to the new subscription or resource group is currently not supported. You'll need to:
109+
110+
1. Manually delete the old license
111+
1. Re-create and reconfigure the license in the new location
112+
113+
For details, review [Manage the unlimited virtualization benefit for SQL Server](manage-configuration.md#manage-pcore-license).
114+
115+
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.
116+
117+
> [!IMPORTANT]
118+
> 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.
119+
120+
## Related content
121+
122+
- [Manage inventory of SQL Server resources with Azure Arc](view-inventory.md)

0 commit comments

Comments
 (0)