Skip to content

Commit 68a68d2

Browse files
MikeRayMSFTMikeRayMSFT
authored
docs: Freshness pass and T-SQL keyword formatting on 5 oldest Azure Arc articles (#37052)
1 parent 0f00f43 commit 68a68d2

5 files changed

Lines changed: 68 additions & 70 deletions

File tree

‎docs/sql-server/azure-arc/migrate-to-azure-sql-managed-instance.md‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: SQL Server migration in Azure Arc to Azure SQL Managed Instance in
55
author: danimir
66
ms.author: danil
77
ms.reviewer: mikeray, randolphwest, mathoma
8-
ms.date: 03/18/2026
8+
ms.date: 04/13/2026
99
ms.topic: how-to
1010
---
1111

@@ -36,7 +36,7 @@ First, you choose an appropriate SQL Managed Instance target and prepare your en
3636

3737
Database migration is available by default for all SQL Server instances enabled by Azure Arc, starting with [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)].
3838

39-
The **Database Migration** pane also has a useful summary of the migration status for your instance, such as the number of total databases, the recommended target, the number of completed migrations, and the number of ongoing migrations:
39+
The **Database Migration** pane also has a useful summary of the migration status for your instance, such as the number of total databases, the recommended target, the number of completed migrations, and the number of ongoing migrations:
4040

4141
:::image type="content" source="media/migrate-to-azure-sql-managed-instance/database-migration-summary.png" alt-text="Screenshot of the summary on the Database Migration pane in the Azure portal." lightbox="media/migrate-to-azure-sql-managed-instance/database-migration-summary.png":::
4242

@@ -83,7 +83,7 @@ To use SQL Server migration in Azure Arc, you need the following prerequisites:
8383
- An active Azure subscription. If you don't have one, you can [create a free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
8484
- Your SQL Server instance must be [enabled by Azure Arc](overview.md) with the Azure extension for SQL Server version `1.1.3238.349` or later. You can upgrade your extension by using the [Azure portal](/azure/azure-arc/servers/manage-vm-extensions-portal#upgrade-extensions) or the [Azure CLI](/azure/azure-arc/servers/manage-vm-extensions-cli#upgrade-extensions).
8585

86-
Before you start the migration process, make sure that you've prepared your environment for your [chosen migration method](#integrated-migration-methods):
86+
Before you start the migration process, make sure that you've prepared your environment for your [chosen migration method](#integrated-migration-methods):
8787
- Prepare for [Managed Instance link migration](migration-sql-mi-prepare-link.md).
8888
- Prepare for [LRS migration](migration-sql-mi-prepare-log-replay-service.md).
8989

@@ -139,9 +139,9 @@ After your target is ready, start the migration process.
139139

140140
#### [MI link migration](#tab/mi-link)
141141

142-
Once you've prepared your environment for [Managed Instance link migration](migration-sql-mi-prepare-link.md), you can migrate your SQL Server databases to Azure SQL Managed Instance.
142+
Once you've prepared your environment for [Managed Instance link migration](migration-sql-mi-prepare-link.md), you can migrate your SQL Server databases to Azure SQL Managed Instance.
143143

144-
> [!NOTE]
144+
> [!NOTE]
145145
> Creating each link can take up to 10 minutes. Use the [Activity log](migrate-to-azure-sql-managed-instance-troubleshoot.md#view-azure-activity-log-for-migration-issues) to track background changes during the link creation process.
146146
147147
Follow these steps to migrate your SQL Server databases to SQL Managed Instance by using the Managed Instance link:
@@ -218,7 +218,7 @@ Select a database and then use **Cutover** to open the **Cutover** pane and see
218218
219219
## Reverse a migration
220220

221-
Reverse migration back to SQL Server from Azure SQL Managed Instance might be supported depending on the [update policy](/azure/azure-sql/managed-instance/update-policy) of your SQL managed instance. For example:
221+
Reverse migration back to SQL Server from Azure SQL Managed Instance might be supported depending on the [update policy](/azure/azure-sql/managed-instance/update-policy) of your SQL managed instance. For example:
222222
- [SQL Server 2022 update policy](/azure/azure-sql/managed-instance/update-policy#sql-server-2022-update-policy): Databases from instances configured with the **SQL Server 2022** update policy can be restored back to SQL Server 2022 instances.
223223
- [SQL Server 2025 update policy](/azure/azure-sql/managed-instance/update-policy#sql-server-2025-update-policy): Databases from instances configured with the **SQL Server 2025** update policy can be restored back to SQL Server 2025 instances.
224224
- [Always-up-to-date update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy): Databases from instances configured with the **Always-up-to-date** update policy can't be restored back to SQL Server.
@@ -227,7 +227,6 @@ If your source SQL Server version is earlier than SQL Server 2022, reverse migra
227227

228228
Reverse migration isn't available through the SQL Server migration in Azure Arc experience. You can manually reverse a migration through other tools such as [native backup and restore](/azure/azure-sql/managed-instance/restore-database-to-sql-server), or [manually configuring a link in SSMS](/azure/azure-sql/managed-instance/managed-instance-link-configure-how-to-ssms).
229229

230-
231230
## Limitations
232231

233232
The limitations of the [Managed Instance link](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview#limitations) and [LRS](/azure/azure-sql/managed-instance/log-replay-service-migrate#limitations) apply to migrations through the Azure portal.

‎docs/sql-server/azure-arc/migration-sql-mi-prepare-link.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Prepare your SQL Server instance enabled by Azure Arc for migration
55
author: danimir
66
ms.author: danil
77
ms.reviewer: mikeray, randolphwest, mathoma
8-
ms.date: 03/18/2026
8+
ms.date: 04/13/2026
99
ms.topic: how-to
1010
---
1111

@@ -39,9 +39,9 @@ The following table lists the minimum supported SQL Server versions for the link
3939
| SQL Server version | Minimum required servicing update |
4040
| --- | --- |
4141
| SQL Server 2025 (17.x) | [SQL Server 2025 RTM (17.0.1000.7)](../sql-server-2025-release-notes.md) |
42-
| SQL Server 2022 (16.x) | [SQL Server 2022 RTM (16.0.1000.6)](../sql-server-2022-release-notes.md) |
42+
| SQL Server 2022 (16.x) | [SQL Server 2022 RTM (16.0.1000.6)](../sql-server-2022-release-notes.md) |
4343
| SQL Server 2019 (15.x) | [SQL Server 2019 CU20 (15.0.4312.2)](https://support.microsoft.com/topic/kb5024276-cumulative-update-20-for-sql-server-2019-4b282be9-b559-46ac-9b6a-badbd44785d2) |
44-
| SQL Server 2017 (14.x) | [SQL Server 2017 CU31 (14.0.3456.2)](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate31) or later and the matching [SQL Server 2017 Azure Connect pack (14.0.3490.10)](/troubleshoot/sql/releases/sqlserver-2017/azureconnect) build |
44+
| SQL Server 2017 (14.x) | [SQL Server 2017 CU31 (14.0.3456.2)](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate31) or later and the matching [SQL Server 2017 Azure Connect pack (14.0.3490.10)](/troubleshoot/sql/releases/sqlserver-2017/azureconnect) build |
4545
| SQL Server 2016 (13.x) | [SQL Server 2016 SP3 (13.0.6300.2)](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-cumulative-update-cu-builds) and the matching [SQL Server 2016 Azure Connect pack (13.0.7000.253)](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-azure-connect-pack-builds) build |
4646
| SQL Server 2014 (12.x) and earlier | Versions before SQL Server 2016 aren't supported. |
4747

@@ -54,7 +54,7 @@ This section describes the permissions that you need to migrate your SQL Server
5454
On the source SQL Server instance, you need the following permissions:
5555

5656
- If you enable [least privilege](configure-least-privilege.md), necessary permissions such as **sysadmin** are [granted](configure-windows-accounts-agent.md#database-migration) as needed during the database migration process.
57-
- If you can't use least privilege, the person performing the migration needs **sysadmin** permissions on the source SQL Server instance. Additionally, if you need to cancel a migration, also manually assign **sysadmin** permissions to the `NT AUTHORITY\SYSTEM` account.
57+
- If you can't use least privilege, the person performing the migration needs **sysadmin** permissions on the source SQL Server instance. Additionally, if you need to cancel a migration, also manually assign **sysadmin** permissions to the `NT AUTHORITY\SYSTEM` account.
5858

5959
To migrate with the Managed Instance link, you need one of the following permissions on the SQL Managed Instance target:
6060

@@ -186,7 +186,7 @@ For more information, see the [syntax to enable trace flags](../../t-sql/databas
186186

187187
### Restart SQL Server and validate the configuration
188188

189-
If you did not need to upgrade the version of SQL Server, enable the availability group feature, or add startup trace flags, you can skip this section.
189+
If you didn't need to upgrade the version of SQL Server, enable the availability group feature, or add startup trace flags, you can skip this section.
190190

191191
After you ensure that you're on a supported version of SQL Server, enable the Always On availability groups feature, and add your startup trace flags, restart your SQL Server instance to apply all of these changes:
192192

@@ -385,11 +385,11 @@ Consider the following points:
385385

386386
## Limitations
387387

388-
Consider the following limitations:
388+
Consider the following limitations:
389389
- The limitations of the [Managed Instance link](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview#limitations) apply to migrations through the Azure portal.
390-
- Azure Extension for SQL Server version `1.1.3238.349` and earlier only supports migrating one database at a time through the link. To migrate multiple databases at the same time, upgrade to Azure Extension for SQL Server version `1.1.3348.364` or later.
391-
- Cancelling a migration requires **sysadmin** permissions on the source SQL Server instance. If your SQL Server instance isn't using least privilege, manually assign **sysadmin** permissions to the `NT AUTHORITY\SYSTEM` account.
392-
- Configuring a link through the Azure portal for the purpose of migration isn't compatible with links created manually, either through SQL Server Management Studio (SSMS), or Transact-SQL (T-SQL). Review the [known issue](migrate-to-azure-sql-managed-instance-troubleshoot.md#known-interoperability-issue-with-existing-links) to learn more.
390+
- Azure Extension for SQL Server version `1.1.3238.349` and earlier only supports migrating one database at a time through the link. To migrate multiple databases at the same time, upgrade to Azure Extension for SQL Server version `1.1.3348.364` or later.
391+
- Canceling a migration requires **sysadmin** permissions on the source SQL Server instance. If your SQL Server instance isn't using least privilege, manually assign **sysadmin** permissions to the `NT AUTHORITY\SYSTEM` account.
392+
- Configuring a link through the Azure portal for the purpose of migration isn't compatible with links created manually, either through SQL Server Management Studio (SSMS), or Transact-SQL (T-SQL). Review the [known issue](migrate-to-azure-sql-managed-instance-troubleshoot.md#known-interoperability-issue-with-existing-links) to learn more.
393393
- Monitoring the migration through the Azure portal is available only to SQL Server instances that meet monitoring [licensing requirements](sql-monitoring.md#prerequisites).
394394

395395
## Troubleshoot common issues
@@ -399,8 +399,8 @@ To troubleshoot common issues when migrating to Azure SQL Managed Instance, see
399399
## Related content
400400

401401
- [Managed Instance link best practices](/azure/azure-sql/managed-instance/managed-instance-link-best-practices)
402-
- [SQL Server migration in Azure Arc](migration-overview.md)
403-
- [Prepare environment for an LRS migration](migration-sql-mi-prepare-log-replay-service.md)
404-
- [SQL Server enabled by Azure Arc overview](overview.md)
402+
- [SQL Server migration in Azure Arc Overview](migration-overview.md)
403+
- [Prepare environment for LRS migration - SQL Server migration in Azure Arc](migration-sql-mi-prepare-log-replay-service.md)
404+
- [SQL Server enabled by Azure Arc](overview.md)
405405
- [Migration experience feedback directly to the product group](https://aka.ms/arc-migrations-feedback)
406406
- [Migration to Azure SQL Managed Instance - SQL Server migration in Azure Arc](migrate-to-azure-sql-managed-instance.md)

‎docs/sql-server/azure-arc/permissions-granted-agent-extension.md‎

Lines changed: 40 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Server level roles created by Azure extension for SQL Server
3-
description: Explains server level roles create when you install Azure extension for SQL Server. Used by SQL Server enabled by Azure Arc
2+
title: Server Level Roles Created by Azure Extension for SQL Server
3+
description: "Explains server level roles create when you install Azure extension for SQL Server. Used by SQL Server enabled by Azure Arc"
44
author: MikeRayMSFT
55
ms.author: mikeray
66
ms.reviewer: nikitatakru
7-
ms.date: 02/06/2024
7+
ms.date: 04/13/2026
88
ms.topic: reference
99
---
1010

@@ -22,50 +22,50 @@ This article lists the server and database roles and mappings that the installat
2222

2323
| Feature | Permission | Level | Role |
2424
|------ |------ |------ |------ |------ |------ |------ |------ |
25-
| Default | VIEW SERVER STATE | Server Level | SQLArcExtensionServerRole |
26-
| | CONNECT SQL | Server Level | SQLArcExtensionServerRole |
27-
| | VIEW ANY DEFINITION | Server Level | SQLArcExtensionServerRole |
28-
| | VIEW ANY DATABASE | Server Level | SQLArcExtensionServerRole |
29-
| | CONNECT ANY DATABASE | Server Level | SQLArcExtensionServerRole |
30-
| | SELECT dbo.sysjobactivity | msdb | SQLArcExtensionUserRole |
31-
| | SELECT dbo.sysjobs | msdb | SQLArcExtensionUserRole |
32-
| | SELECT dbo.syssessions | msdb | SQLArcExtensionUserRole |
33-
| | SELECT dbo.sysjobHistory | msdb | SQLArcExtensionUserRole |
34-
| | SELECT dbo.sysjobSteps | msdb | SQLArcExtensionUserRole |
35-
| | SELECT dbo.syscategories | msdb | SQLArcExtensionUserRole |
36-
| | SELECT dbo.sysoperators | msdb | SQLArcExtensionUserRole |
37-
| | SELECT dbo.suspectpages | msdb | SQLArcExtensionUserRole |
38-
| | SELECT dbo.backupset | msdb | SQLArcExtensionUserRole |
39-
| | SELECT dbo.backupmediaset | msdb | SQLArcExtensionUserRole |
40-
| | SELECT dbo.backupmediafamily | msdb | SQLArcExtensionUserRole |
41-
| | SELECT dbo.backupfile | msdb | SQLArcExtensionUserRole |
42-
| Backup | CREATE ANY DATABASE | Server Level | SQLArcExtensionServerRole |
25+
| Default | `VIEW SERVER STATE` | Server Level | SQLArcExtensionServerRole |
26+
| | `CONNECT SQL` | Server Level | SQLArcExtensionServerRole |
27+
| | `VIEW ANY DEFINITION` | Server Level | SQLArcExtensionServerRole |
28+
| | `VIEW ANY DATABASE` | Server Level | SQLArcExtensionServerRole |
29+
| | `CONNECT ANY DATABASE` | Server Level | SQLArcExtensionServerRole |
30+
| | `SELECT dbo.sysjobactivity` | `msdb` | SQLArcExtensionUserRole |
31+
| | `SELECT dbo.sysjobs` | `msdb` | SQLArcExtensionUserRole |
32+
| | `SELECT dbo.syssessions` | `msdb` | SQLArcExtensionUserRole |
33+
| | `SELECT dbo.sysjobHistory` | `msdb` | SQLArcExtensionUserRole |
34+
| | `SELECT dbo.sysjobSteps` | `msdb` | SQLArcExtensionUserRole |
35+
| | `SELECT dbo.syscategories` | `msdb` | SQLArcExtensionUserRole |
36+
| | `SELECT dbo.sysoperators` | `msdb` | SQLArcExtensionUserRole |
37+
| | `SELECT dbo.suspectpages` | `msdb` | SQLArcExtensionUserRole |
38+
| | `SELECT dbo.backupset` | `msdb` | SQLArcExtensionUserRole |
39+
| | `SELECT dbo.backupmediaset` | `msdb` | SQLArcExtensionUserRole |
40+
| | `SELECT dbo.backupmediafamily` | `msdb` | SQLArcExtensionUserRole |
41+
| | `SELECT dbo.backupfile` | `msdb` | SQLArcExtensionUserRole |
42+
| Backup | `CREATE ANY DATABASE` | Server Level | SQLArcExtensionServerRole |
4343
| | db_backupoperator role | All databases | SQLArcExtensionUserRole |
4444
| | dbcreator | Server Level | SQLArcExtensionServerRole |
45-
| Azure Control Plane | CREATE TABLE | msdb | SQLArcExtensionUserRole |
46-
| | ALTER ANY SCHEMA | msdb | SQLArcExtensionUserRole |
47-
| | CREATE TYPE | msdb | SQLArcExtensionUserRole |
48-
| | EXECUTE | msdb | SQLArcExtensionUserRole |
49-
| | db_datawriter role | msdb | SQLArcExtensionUserRole |
50-
| | db_datareader role | msdb | SQLArcExtensionUserRole |
51-
| Availability Group Discovery | VIEW ANY DEFINITION | Server Level | SQLArcExtensionServerRole |
52-
| Availability Group Failover | ALTER ANY AVAILABILITY GROUP | Server Level | SQLArcExtensionServerRole |
53-
| Purview | SELECT | All databases | SQLArcExtensionUserRole |
54-
| | EXECUTE | All databases | SQLArcExtensionUserRole |
55-
| Migration Assessment | EXECUTE dbo.agent_datetime | msdb | SQLArcExtensionUserRole |
56-
| | SELECT dbo.sysjobs | msdb | SQLArcExtensionUserRole |
57-
| | SELECT dbo.sysmail_account | msdb | SQLArcExtensionUserRole |
58-
| | SELECT dbo.sysmail_profile | msdb | SQLArcExtensionUserRole |
59-
| | SELECT dbo.sysmail_profileaccount | msdb | SQLArcExtensionUserRole |
60-
| | SELECT dbo.syssubsystems | msdb | SQLArcExtensionUserRole |
61-
| | SELECT sys.sql_expression_dependencies | All databases | SQLArcExtensionUserRole |
45+
| Azure Control Plane | `CREATE TABLE` | `msdb` | SQLArcExtensionUserRole |
46+
| | `ALTER ANY SCHEMA` | `msdb` | SQLArcExtensionUserRole |
47+
| | `CREATE TYPE` | `msdb` | SQLArcExtensionUserRole |
48+
| | `EXECUTE` | `msdb` | SQLArcExtensionUserRole |
49+
| | db_datawriter role | `msdb` | SQLArcExtensionUserRole |
50+
| | db_datareader role | `msdb` | SQLArcExtensionUserRole |
51+
| Availability Group Discovery | `VIEW ANY DEFINITION` | Server Level | SQLArcExtensionServerRole |
52+
| Availability Group Failover | `ALTER ANY AVAILABILITY GROUP` | Server Level | SQLArcExtensionServerRole |
53+
| Purview | `SELECT` | All databases | SQLArcExtensionUserRole |
54+
| | `EXECUTE` | All databases | SQLArcExtensionUserRole |
55+
| Migration Assessment | `EXECUTE dbo.agent_datetime` | `msdb` | SQLArcExtensionUserRole |
56+
| | `SELECT dbo.sysjobs` | `msdb` | SQLArcExtensionUserRole |
57+
| | `SELECT dbo.sysmail_account` | `msdb` | SQLArcExtensionUserRole |
58+
| | `SELECT dbo.sysmail_profile` | `msdb` | SQLArcExtensionUserRole |
59+
| | `SELECT dbo.sysmail_profileaccount` | `msdb` | SQLArcExtensionUserRole |
60+
| | `SELECT dbo.syssubsystems` | `msdb` | SQLArcExtensionUserRole |
61+
| | `SELECT sys.sql_expression_dependencies` | All databases | SQLArcExtensionUserRole |
6262

6363
## Run with least privilege
6464

6565
To run Azure extension for SQL Server with least privilege, follow the instructions at [Operate SQL Server enabled by Azure Arc with least privilege](configure-least-privilege.md).
6666

67-
At this time, the least privilege configuration is not the default.
67+
At this time, the least privilege configuration isn't the default.
6868

6969
## Related content
7070

71-
[Configure Windows service accounts and permissions](../../database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md)
71+
- [Configure Windows service accounts and permissions](../../database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md)

‎docs/sql-server/azure-arc/release-notes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Latest release notes for SQL Server enabled by Azure Arc
44
author: anosov1960
55
ms.author: sashan
66
ms.reviewer: mikeray, randolphwest, mathoma
7-
ms.date: 03/18/2026
7+
ms.date: 04/13/2026
88
ms.topic: release-notes
99
ms.custom:
1010
- ignite-2025

0 commit comments

Comments
 (0)