ADS: Remove Azure Data Studio from migration content (#36519)

Author: rwestMSFT

.openpublishing.redirection.data-migration.json

@@ -4,6 +4,11 @@
       "source_path": "data-migration/sql-server/virtual-machines/database-migration-service.md",
       "redirect_url": "/data-migration/sql-server/virtual-machines/database-migration-service-offline",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "data-migration/sql-server/managed-instance/database-migration-service.md",
+      "redirect_url": "/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance",
+      "redirect_document_id": false
     }
   ]
 }

azure-sql/database/features-comparison.md

@@ -4,8 +4,8 @@ titleSuffix: Azure SQL Database & Azure SQL Managed Instance
 description: This article compares the database engine features of Azure SQL Database and Azure SQL Managed Instance
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.reviewer: danil, bonova, mathoma, danil, randolphwest
-ms.date: 01/27/2026
+ms.reviewer: danil, bonova, mathoma, randolphwest
+ms.date: 02/19/2026
 ms.service: azure-sql
 ms.subservice: service-overview
 ms.topic: product-comparison
@@ -84,7 +84,7 @@ The following table lists the major features of SQL Server and provides informat
 | [Link feature](../managed-instance/managed-instance-link-feature-overview.md) | No | Yes |
 | [Linked servers](/sql/relational-databases/linked-servers/linked-servers-database-engine) | No, see [Elastic query](elastic-query-horizontal-partitioning.md) | Yes. Only to [SQL Server and SQL Database](../managed-instance/transact-sql-tsql-differences-sql-server.md#linked-servers) without distributed transactions. |
 | [Linked servers](/sql/relational-databases/linked-servers/linked-servers-database-engine) that read from files (CSV, Excel)| No. Use [BULK INSERT](/sql/t-sql/statements/bulk-insert-transact-sql#e-importing-data-from-a-csv-file) or [OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql#g-accessing-data-from-a-csv-file-with-a-format-file) as an alternative for CSV format. | No. Use [BULK INSERT](/sql/t-sql/statements/bulk-insert-transact-sql#e-importing-data-from-a-csv-file) or [OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql#g-accessing-data-from-a-csv-file-with-a-format-file) as an alternative for CSV format. Track these requests on [SQL Managed Instance feedback item](https://feedback.azure.com/d365community/idea/db80cf6e-3425-ec11-b6e6-000d3a4f0f84)|
-| [Log shipping](/sql/database-engine/log-shipping/about-log-shipping-sql-server) | [Availability through redundancy](high-availability-sla-local-zone-redundancy.md) is included with every database. Disaster recovery is discussed in [Overview of business continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md). | Natively built in as a part of [Azure Data Migration Service (DMS)](/azure/dms/tutorial-sql-server-to-managed-instance) migration process. Natively built for custom data migration projects as an external [Log Replay Service](../managed-instance/log-replay-service-migrate.md).<br /> Not available as High availability solution, because other [Availability through redundancy](high-availability-sla-local-zone-redundancy.md) methods are included with every database and it isn't recommended to use Log-shipping as HA alternative. Disaster recovery is discussed in [Overview of business continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md). Not available as a replication mechanism between databases - use secondary replicas on [Business Critical tier](service-tiers-sql-database-vcore.md#business-critical), [failover groups](failover-group-sql-db.md), or [transactional replication](../managed-instance/replication-transactional-overview.md) as the alternatives. |
+| [Log shipping](/sql/database-engine/log-shipping/about-log-shipping-sql-server) | [Availability through redundancy](high-availability-sla-local-zone-redundancy.md) is included with every database. Disaster recovery is discussed in [Overview of business continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md). | Natively built in as a part of [Azure Database Migration Service (DMS)](/azure/dms/tutorial-sql-server-to-managed-instance) migration process. Natively built for custom data migration projects as an external [Log Replay Service](../managed-instance/log-replay-service-migrate.md).<br /> Not available as High availability solution, because other [Availability through redundancy](high-availability-sla-local-zone-redundancy.md) methods are included with every database and it isn't recommended to use Log-shipping as HA alternative. Disaster recovery is discussed in [Overview of business continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md). Not available as a replication mechanism between databases - use secondary replicas on [Business Critical tier](service-tiers-sql-database-vcore.md#business-critical), [failover groups](failover-group-sql-db.md), or [transactional replication](../managed-instance/replication-transactional-overview.md) as the alternatives. |
 | [Logins and users](/sql/relational-databases/security/authentication-access/principals-database-engine) | Yes, but `CREATE LOGIN` and `ALTER LOGIN` statements are limited. Windows logins are not supported. Microsoft Entra logins are in preview. `EXECUTE AS LOGIN` isn't supported - use `EXECUTE AS USER`.  | Yes, with some [differences](../managed-instance/transact-sql-tsql-differences-sql-server.md#logins-and-users). See [Windows Authentication for Azure SQL Managed Instance](../managed-instance/winauth-implementation-aad-kerberos.md) - the process requires Active Directory synchronization to Microsoft Entra ID. |
 | [Maintenance window](maintenance-window.md) selection | Yes | Yes |
 | [Configure advance notifications for planned maintenance events](advance-notifications.md) | Yes | Yes |
@@ -213,11 +213,11 @@ Azure SQL Database and Azure SQL Managed Instance support various data tools tha
 
 You can use different migration methods to move your data between SQL Server, Azure SQL Database, and Azure SQL Managed Instance. Some methods are **Online** and picking-up all changes that are made on the source while you're running migration, while in **Offline** methods you need to stop your workload that is modifying data on the source while the migration is in progress.
 
-| **Source** | **Azure SQL Database** | **Azure SQL Managed Instance** |
+| Source | Azure SQL Database | Azure SQL Managed Instance |
 | --- | --- | --- |
-| SQL Server (on-premises, AzureVM, Amazon RDS) | **Online:**  [Transactional Replication](replication-to-sql-database.md?view=azuresql-db&preserve-view=true) <br/> **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP | **Online:** [Managed Instance link](../managed-instance/managed-instance-link-feature-overview.md?view=azuresql-mi&preserve-view=true), [Log Replay Service](../managed-instance/log-replay-service-overview.md?view=azuresql-mi&preserve-view=true), [Azure Data Migration Service (DMS)](/azure/dms/tutorial-sql-server-managed-instance-online-ads), [Transactional Replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) <br/> **Offline:** [Azure Database Migration Service](/azure/dms/tutorial-sql-server-managed-instance-offline-ads), [Native backup/restore](../managed-instance/restore-sample-database-quickstart.md?view=azuresql-mi&preserve-view=true), [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP, [Snapshot replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) |
-| Single database | **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP | **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP |
-| SQL Managed Instance | **Online:** [Transactional Replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) <br/> **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP, [Snapshot replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) | **Online:** [Database copy/move](../managed-instance/database-copy-move-how-to.md?view=azuresql-mi&preserve-view=true), [Transactional Replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) <br/> **Offline:** Cross-instance point-in-time restore ([Azure PowerShell](/powershell/module/az.sql/restore-azsqlinstancedatabase#examples) or [Azure CLI](https://techcommunity.microsoft.com/t5/azure-sql-blog/cross-instance-point-in-time-restore-in-azure-sql-database/ba-p/386208)), [Native backup/restore](../managed-instance/restore-sample-database-quickstart.md?view=azuresql-mi&preserve-view=true), [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP, [Snapshot replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) |
+| SQL Server (on-premises, Azure VM, Amazon RDS) | **Online:**  [Transactional Replication](replication-to-sql-database.md?view=azuresql-db&preserve-view=true) <br/> **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP | **Online:** [Managed Instance link](../managed-instance/managed-instance-link-feature-overview.md?view=azuresql-mi&preserve-view=true), [Log Replay Service](../managed-instance/log-replay-service-overview.md?view=azuresql-mi&preserve-view=true), [SQL Server migration experience in Azure Arc](/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance), [Azure Database Migration Service (DMS)](/data-migration/sql-server/managed-instance/database-migration-service), [Transactional Replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) <br/> **Offline:** [Azure Database Migration Service](/data-migration/sql-server/managed-instance/database-migration-service), [Native backup/restore](../managed-instance/restore-sample-database-quickstart.md?view=azuresql-mi&preserve-view=true), [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP, [Snapshot replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) |
+| Azure SQL Database | **Offline:** [Azure Database Migration Service (DMS)](/data-migration/sql-server/database/database-migration-service), [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP | **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP |
+| Azure SQL Managed Instance | **Online:** [Transactional Replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) <br/> **Offline:** [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP, [Snapshot replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) | **Online:** [Database copy/move](../managed-instance/database-copy-move-how-to.md?view=azuresql-mi&preserve-view=true), [Transactional Replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) <br/> **Offline:** Cross-instance point-in-time restore ([Azure PowerShell](/powershell/module/az.sql/restore-azsqlinstancedatabase#examples) or [Azure CLI](https://techcommunity.microsoft.com/t5/azure-sql-blog/cross-instance-point-in-time-restore-in-azure-sql-database/ba-p/386208)), [Native backup/restore](../managed-instance/restore-sample-database-quickstart.md?view=azuresql-mi&preserve-view=true), [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database), BCP, [Snapshot replication](../managed-instance/replication-transactional-overview.md?view=azuresql-mi&preserve-view=true) |
 
 ## Related content
 

azure-sql/managed-instance/instance-create-quickstart.md

@@ -3,8 +3,8 @@ title: "Quickstart: Create Azure SQL Managed Instance"
 description: Create Azure SQL Managed Instance by using the Azure portal, PowerShell, and the Azure CLI.
 author: vladai78
 ms.author: vladiv
-ms.reviewer: mathoma
-ms.date: 10/25/2025
+ms.reviewer: mathoma, randolphwest
+ms.date: 02/19/2026
 ms.service: azure-sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: quickstart
@@ -258,16 +258,13 @@ To connect to SQL Managed Instance, follow these steps to retrieve the host name
 > [!div class="nextstepaction"]
 > [Connect your application to Azure SQL Managed Instance](connect-application-instance.md)
 
-
 ## Related content
 
 To restore an existing SQL Server database from on-premises to SQL Managed Instance: 
 
-- [Azure Database Migration Service](/azure/dms/tutorial-sql-server-managed-instance-online-ads)
+- [SQL Server migration experience in Azure Arc](/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance)
 - [Quickstart: Restore a database to Azure SQL Managed Instance with SSMS](restore-sample-database-quickstart.md)
-
 - [Quickstart: Configure an Azure VM to connect to Azure SQL Managed Instance](connect-vm-instance-configure.md)
 - [Migration overview: SQL Server to SQL Managed Instance](../migration-guides/managed-instance/sql-server-to-managed-instance-overview.md)
 - [Quickstart: Configure a point-to-site connection to Azure SQL Managed Instance from on-premises](point-to-site-p2s-configure.md)
 - [Monitor Azure SQL workloads with database watcher (preview)](../database-watcher-overview.md)
-

azure-sql/managed-instance/sql-managed-instance-paas-overview.md

@@ -3,8 +3,8 @@ title: What is Azure SQL Managed Instance?
 description: Learn about how Azure SQL Managed Instance provides near 100% compatibility with the latest SQL Server (Enterprise Edition) database engine.
 author: MashaMSFT
 ms.author: mathoma
-ms.reviewer: vanto
-ms.date: 10/10/2025
+ms.reviewer: vanto, randolphwest
+ms.date: 02/19/2026
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: overview
@@ -32,7 +32,7 @@ If you're new to Azure SQL Managed Instance, check out the *Azure SQL Managed In
 
 Azure SQL Managed Instance is a PaaS service that has near 100% compatibility with the latest Enterprise Edition SQL Server Database Engine. It provides a native [virtual network (VNet)](/azure/virtual-network/virtual-networks-overview) implementation that addresses common security concerns, and a [business model](https://azure.microsoft.com/pricing/details/sql-database/) favorable to existing SQL Server customers. SQL Managed Instance enables existing SQL Server customers to lift and shift their on-premises applications to the cloud with minimal application and database changes. At the same time, SQL Managed Instance provides all PaaS capabilities (automatic patching and version updates, [automated backups](automated-backups-overview.md), [high availability](high-availability-sla-local-zone-redundancy.md)) to drastically reduce management overhead and the total cost of ownership (TCO).
 
-SQL Managed Instance is designed for customers who want to migrate a large number of apps from an on-premises or IaaS, self-built, or ISV provided environment to a fully managed PaaS cloud environment, with as low a migration effort as possible. By using the fully automated [Azure Data Migration Service](/azure/dms/tutorial-sql-server-to-managed-instance#create-an-azure-database-migration-service-instance), or the [Managed Instance link](managed-instance-link-feature-overview.md), customers can lift and shift their existing SQL Server database or SQL Server instance to Azure SQL Managed Instance, which offers compatibility with SQL Server and complete isolation of customer instances with native VNet support.
+SQL Managed Instance is designed for customers who want to migrate a large number of apps from an on-premises or IaaS, self-built, or ISV provided environment to a fully managed PaaS cloud environment, with as low a migration effort as possible. By using the [SQL Server migration experience in Azure Arc](/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance), or the [Managed Instance link](managed-instance-link-feature-overview.md), customers can lift and shift their existing SQL Server database or SQL Server instance to Azure SQL Managed Instance, which offers compatibility with SQL Server and complete isolation of customer instances with native VNet support.
 
 With Software Assurance, you can allocate your existing licenses for discounted rates on SQL Managed Instance by using the [Azure Hybrid Benefit for SQL Server](https://azure.microsoft.com/pricing/hybrid-benefit/). SQL Managed Instance is the best migration destination in the cloud for SQL Server instances that require high security and a rich programmability surface.
 
@@ -91,8 +91,9 @@ The following list shows SQL Server features that are compatible with Azure SQL
     **Data migration**
     - [Native backup and restore](restore-sample-database-quickstart.md)
     - Configurable database file layout
-    - Migrations at scale with [Azure Database Migration Service](/azure/dms/tutorial-sql-server-managed-instance-online-ads)
+    - [SQL migration experience in Azure Arc portal](/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance)
     - [Migrate with Managed Instance link](managed-instance-link-migrate.md)
+    - Automated migrations at scale with [Azure Database Migration Service](/azure/dms/migration-dms-powershell-cli)
     :::column-end:::
     :::column:::
     **Operational**

data-migration/includes/create-database-migration-service-instance.md

@@ -1,12 +1,13 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 06/26/2024
+ms.date: 02/19/2026
 ms.service: azure-database-migration-service
 ms.topic: include
 ms.collection:
   - sql-migration-content
-ms.custom: sfi-image-nochange
+ms.custom:
+  - sfi-image-nochange
 ---
 
 **Step 1:** In the [Azure portal](https://portal.azure.com/#browse/Microsoft.DataMigration%2Fservices), navigate to the **Azure Database Migration Service** page. Create a new instance of Azure Database Migration Service, or reuse an existing instance that you created earlier.
@@ -37,7 +38,7 @@ To create a new instance of Database Migration Service:
 
 1. If the self-hosted integration runtime (SHIR) is required, on the overview page of your Database Migration Service and under Settings, select **Integration runtime**, and complete the following steps:
 
-   1. Select **Configure integration runtime** and choose the **[Download and install integration runtime](https://aka.ms/sql-migration-shir-download)** link to open the download link in a web browser. Download the integration runtime, and then install it on a computer that meets the prerequisites for connecting to the source SQL Server instance. For more information, see [SHIR recommendations](/azure/dms/migration-using-azure-data-studio?tabs=azure-sql-mi#recommendations-for-using-a-self-hosted-integration-runtime-for-database-migrations).
+   1. Select **Configure integration runtime** and choose the **[Download and install integration runtime](https://aka.ms/sql-migration-shir-download)** link to open the download link in a web browser. Download the integration runtime, and then install it on a computer that meets the prerequisites for connecting to the source SQL Server instance. For more information, see [Self-hosted integration runtime for database migrations](../sql-server/self-hosted-integration-runtime.md).
 
       :::image type="content" source="media/create-database-migration-service-instance/dms-portal-shir-configure.png" alt-text="Screenshot that shows the Download and install integration runtime link." lightbox="media/create-database-migration-service-instance/dms-portal-shir-configure.png":::