From 393b9368178ba1efee6af4987f3370f3218bf3d8 Mon Sep 17 00:00:00 2001 From: Jan-Hendrik Peters Date: Wed, 1 Apr 2026 08:53:26 +0200 Subject: [PATCH 1/3] Update move-resources.md --- docs/sql-server/azure-arc/move-resources.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/sql-server/azure-arc/move-resources.md b/docs/sql-server/azure-arc/move-resources.md index d2be01d9d45..7b676173efa 100644 --- a/docs/sql-server/azure-arc/move-resources.md +++ b/docs/sql-server/azure-arc/move-resources.md @@ -60,6 +60,14 @@ Wait for the resource move to finish. It takes resources up to one hour to move Verify that the Azure Arc-enabled SQL Server instances and associated databases are in the new resource group or subscription. +> [!IMPORTANT] +> +> If the SQL instances or databases associated with the moved virtual machines do not show up after up to three hours, +> ensure that the Azure Connected Machine Agent is still running and connected to Azure Arc. +> +> Upgrading the `WindowsAgent.SqlServer` extension on the virtual machine will also trigger a refresh of the +> SQL instance and database inventory. + ## Enable features Enable any features that you disabled before the move. From ec02fb1c4300f23dd2a11be0beefad90b57655d4 Mon Sep 17 00:00:00 2001 From: Jan-Hendrik Peters Date: Sun, 5 Apr 2026 22:36:41 +0200 Subject: [PATCH 2/3] Update docs/sql-server/azure-arc/move-resources.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/sql-server/azure-arc/move-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sql-server/azure-arc/move-resources.md b/docs/sql-server/azure-arc/move-resources.md index 7b676173efa..18fc5e3f6d6 100644 --- a/docs/sql-server/azure-arc/move-resources.md +++ b/docs/sql-server/azure-arc/move-resources.md @@ -62,7 +62,7 @@ Verify that the Azure Arc-enabled SQL Server instances and associated databases > [!IMPORTANT] > -> If the SQL instances or databases associated with the moved virtual machines do not show up after up to three hours, +> If the SQL instances or databases associated with the moved virtual machines don't appear in the portal within three hours, > ensure that the Azure Connected Machine Agent is still running and connected to Azure Arc. > > Upgrading the `WindowsAgent.SqlServer` extension on the virtual machine will also trigger a refresh of the From 70fce7ca0fa5927d8c934efbeceef20bf35fb8bd Mon Sep 17 00:00:00 2001 From: Jan-Hendrik Peters Date: Sun, 5 Apr 2026 22:37:06 +0200 Subject: [PATCH 3/3] Update docs/sql-server/azure-arc/move-resources.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/sql-server/azure-arc/move-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sql-server/azure-arc/move-resources.md b/docs/sql-server/azure-arc/move-resources.md index 18fc5e3f6d6..932d66c541e 100644 --- a/docs/sql-server/azure-arc/move-resources.md +++ b/docs/sql-server/azure-arc/move-resources.md @@ -63,7 +63,7 @@ Verify that the Azure Arc-enabled SQL Server instances and associated databases > [!IMPORTANT] > > If the SQL instances or databases associated with the moved virtual machines don't appear in the portal within three hours, -> ensure that the Azure Connected Machine Agent is still running and connected to Azure Arc. +> ensure that the Azure Connected Machine agent is still running and connected to Azure Arc. > > Upgrading the `WindowsAgent.SqlServer` extension on the virtual machine will also trigger a refresh of the > SQL instance and database inventory.