Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes how you can move resources to a new resource group or subscription with SQL Server enabled by Azure Arc. The capability applies to both:
- SQL Server instances
- Databases
Before you begin, review 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.
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:
- Reenable any features that you disabled.
- Configure SQL Server license in the new location.
- Configure ESU in the new location.
Move resources to a new resource group or subscription
In the Azure portal, locate the resource group.
Select the server.
The server resource type is Machine - Azure Arc. Don't select any other types of resources.
If the SQL Server instance is a failover cluster instance, select all of the Machine - Azure Arc server resources for the active and inactive nodes.
Select Move > Move to another resource group or Move to another subscription.
Under Move resources, provide the required information. Select Next.
Review the information and select Move.
Wait for the resource move to finish. It takes resources up to one hour to move items and reflect the new location in the portal.
Verify that the move is complete
Verify that the Azure Arc-enabled SQL Server instances and associated databases are in the new resource group or subscription.
Enable features
Enable any features that you disabled before the move.
The following table identifies features that remain enabled after the resource move, along with features that you need to reenable.
Feature | Before move | After move |
---|---|---|
Patching | Enabled | Enabled |
Extended Security Updates | Enabled | Enabled |
License type | Enabled | Enabled |
Viewing databases | Enabled | Enabled |
Viewing availability groups | Enabled | Enabled |
Viewing failover cluster instances | Enabled | Enabled |
Automated backups | Enabled | Enabled |
Monitoring dashboards | Enabled | Enabled |
Microsoft Entra ID | Enabled | Enabled |
Microsoft Purview | Enabled | Disabled. To enable, review Connect to and manage Azure Arc-enabled SQL Server in Microsoft Purview. |
Best practices assessment | Enabled | Disabled. Review the following section about enabling best practices assessment. |
Microsoft Defender | Enabled | Disabled. To enable, review Protect SQL Server with Microsoft Defender for Cloud. |
Enable best practices assessment
The way to enable best practices assessment depends on whether the resource moved resource groups or subscriptions.
Resources moved within the same subscription
- Before the move, disable best practices assessment.
- Move the resource.
- Enable best practices assessment.
Alternatively, use an Azure policy to enable best practices assessment at scale.
Resources moved to a different subscription
The following steps explain how to reconfigure best practices assessment after a move to a different subscription, to a different resource group, or within the same Log Analytics workspace.
- Before the move, disable best practices assessment.
- Move the resource.
- 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:
- Manually delete the old license
- Re-create and reconfigure the license in the new location
For details, review Manage the unlimited virtualization benefit for SQL Server.
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.