Skip to content

Update move-resources.md #10308

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nyanhp wants to merge 1 commit into
base: live
Choose a base branch
from
+8 −0
Open

Update move-resources.md #10308

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/sql-server/azure-arc/move-resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wording is awkward/ambiguous: “do not show up after up to three hours” reads like both a delay and a maximum. Consider rephrasing to “don’t show up within three hours” (or specify the expected propagation window more directly).

Suggested change
> 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,

Copilot uses AI. Check for mistakes.
> ensure that the Azure Connected Machine Agent is still running and connected to Azure Arc.
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with other Azure Arc docs and the product name, use “Azure Connected Machine agent” (lowercase “agent”) rather than “Azure Connected Machine Agent”. Consider linking “Azure Connected Machine agent” to the agent overview if helpful.

Suggested change
> 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.

Copilot uses AI. Check for mistakes.
>
> Upgrading the `WindowsAgent.SqlServer` extension on the virtual machine will also trigger a refresh of the
Comment on lines +65 to +68
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This article applies to Arc-enabled machines (virtual or physical), but the new IMPORTANT note refers to “moved virtual machines”. Consider changing to “moved machines/servers” to avoid implying this only applies to VMs.

Suggested change
> 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
> If the SQL instances or databases associated with the moved 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 machine will also trigger a refresh of the

Copilot uses AI. Check for mistakes.
> SQL instance and database inventory.
Comment on lines +65 to +69
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The note calls out upgrading the WindowsAgent.SqlServer extension on the “virtual machine”. This is Windows-specific and VM-specific; Arc-enabled SQL Server can also be on Linux/physical machines (for Linux it’s LinuxAgent.SqlServer). Consider referring generically to “the Azure extension for SQL Server” (and, if you include the extension name, mention both Windows and Linux) and adding a link to the existing extension upgrade instructions so the guidance is actionable.

Suggested change
> 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.
> If the SQL instances or databases associated with the moved servers 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 Azure extension for SQL Server (for example, `WindowsAgent.SqlServer` or `LinuxAgent.SqlServer`) will also trigger a refresh of the SQL instance and database inventory. For upgrade steps, see [Upgrade Azure extension for SQL Server](upgrade-azure-extension-sql-server.md).

Copilot uses AI. Check for mistakes.

## Enable features

Enable any features that you disabled before the move.
Expand Down
Loading