Merge pull request #36110 from MladjoA/patch-22

prmerger-automator[bot] · web-flow · commit e67b5e491672 · 2025-12-31T21:17:08.000Z
Update SQL Server image version and date in tutorial
diff --git a/azure-sql/managed-instance/replication-two-instances-and-sql-server-configure-tutorial.md b/azure-sql/managed-instance/replication-two-instances-and-sql-server-configure-tutorial.md
@@ -4,7 +4,7 @@ description: "A tutorial that configures replication between a publisher SQL man
 author: MladjoA
 ms.author: mlandzic
 ms.reviewer: mathoma
-ms.date: 08/26/2025
+ms.date: 12/31/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: security
 ms.topic: tutorial
@@ -29,11 +29,11 @@ In this tutorial, you learn how to:
 > - Configure a SQL managed instance as a replication distributor.
 > - Configure SQL Server as a subscriber.
 
-![Diagram showing replication between a SQL managed instance publisher, SQL managed instance distributor, and SQL Server subscriber](./media/replication-two-instances-and-sql-server-configure-tutorial/sqlmi-to-sql-replication.png)
+:::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/sqlmi-to-sql-replication.png" alt-text="Diagram showing replication between a SQL managed instance publisher, SQL managed instance distributor, and SQL Server subscriber.":::
 
 This tutorial is intended for an experienced audience and assumes the user is familiar with deploying and connecting to both SQL managed instances and SQL Server VMs within Azure.
 
-> [!NOTE]
+> [!NOTE]  
 > This article describes the use of [transactional replication](/sql/relational-databases/replication/transactional/transactional-replication) in Azure SQL Managed Instance. It's unrelated to [failover groups](failover-group-sql-mi.md), an Azure SQL Managed Instance feature that allows you to create complete readable replicas of individual instances. There are additional considerations when configuring [transactional replication with failover groups](replication-transactional-overview.md#with-failover-groups).
 
 ## Prerequisites
@@ -67,9 +67,9 @@ Create two SQL managed instances within this new resource group using the [Azure
 - The name of the publisher SQL managed instance should be `sql-mi-publisher` (along with a few characters for randomization), and the name of the virtual network should be `vnet-sql-mi-publisher`.
 - The name of the distributor SQL managed instance should be `sql-mi-distributor` (along with a few characters for randomization), and it should be *in the same virtual network as the publisher SQL managed instance*.
 
-  ![Screenshot showing the use of the publisher VNet for the distributor.](./media/replication-two-instances-and-sql-server-configure-tutorial/use-same-vnet-for-distributor.png)
+  :::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/use-same-vnet-for-distributor.png" alt-text="Screenshot showing the use of the publisher VNet for the distributor.":::
 
-For more information about creating a SQL managed instance, see [Create a SQL managed instance in the portal](instance-create-quickstart.md).
+For more information about creating a SQL managed instance, see [Quickstart: Create Azure SQL Managed Instance](instance-create-quickstart.md).
 
   > [!NOTE]  
   > For the sake of simplicity, and because it's the most common configuration, this tutorial suggests placing the distributor SQL managed instance within the same virtual network as the publisher. However, it's possible to create the distributor in a separate virtual network. To do so, you'll need to configure VNet peering between the virtual networks of the publisher and distributor, and then configure VNet peering between the virtual networks of the distributor and subscriber.
@@ -79,11 +79,11 @@ For more information about creating a SQL managed instance, see [Create a SQL ma
 Create a SQL Server virtual machine using the [Azure portal](https://portal.azure.com). The SQL Server virtual machine should have the following characteristics:
 
 - Name: `sql-vm-subscriber`
-- Image: SQL Server 2016 or later
+- Image: SQL Server version that supports transactional replication with Azure SQL Managed Instance, per the [supportability matrix](replication-transactional-overview.md#supportability-matrix)
 - Resource group: the same as the SQL managed instance
 - Virtual network: `sql-vm-subscriber-vnet`
 
-For more information about deploying a SQL Server VM to Azure, see [Quickstart: Create a SQL Server VM](../virtual-machines/windows/sql-vm-create-portal-quickstart.md).
+For more information about deploying a SQL Server VM to Azure, see [Quickstart: Create SQL Server on a Windows virtual machine in the Azure portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md).
 
 ## Configure VNet peering
 
@@ -133,15 +133,15 @@ Get-AzVirtualNetworkPeering `
 
 Once VNet peering is established, test connectivity by launching SQL Server Management Studio (SSMS) on the SQL Server host and connecting to both SQL managed instances. For more information on connecting to a SQL managed instance using SSMS, see [Use SSMS to connect to SQL Managed Instance](point-to-site-p2s-configure.md#connect-with-ssms).
 
-![Screenshot showing how to test connectivity to the SQL managed instances.](./media/replication-two-instances-and-sql-server-configure-tutorial/test-connectivity-to-mi.png)
+:::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/test-connectivity-to-mi.png" alt-text="Screenshot showing how to test connectivity to the SQL managed instances.":::
 
-<a id="create-a-private-dns-zone"></a>
+<a id="creating-a-private-dns-zone"></a>
 
-## Creating a private DNS zone
+## Create a private DNS zone
 
 A private DNS zone allows DNS routing between the SQL managed instances and SQL Server.
 
-### Create a private DNS zone
+### Create a private zone
 
 1. Sign into the [Azure portal](https://portal.azure.com).
 1. Select **Create a resource** to create a new Azure resource.
@@ -150,7 +150,7 @@ A private DNS zone allows DNS routing between the SQL managed instances and SQL
 1. Choose the subscription and resource group from the dropdown list.
 1. Provide an arbitrary name for your DNS zone, such as `repldns.com`.
 
-   ![Screenshot showing the Create private DNS zone in the Azure portal.](./media/replication-two-instances-and-sql-server-configure-tutorial/create-private-dns-zone.png)
+   :::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/create-private-dns-zone.png" alt-text="Screenshot showing the Create private DNS zone in the Azure portal." lightbox="media/replication-two-instances-and-sql-server-configure-tutorial/create-private-dns-zone.png":::
 
 1. Select **Review + create**. Review the parameters for your private DNS zone, and then select **Create** to create your resource.
 
@@ -160,7 +160,7 @@ A private DNS zone allows DNS routing between the SQL managed instances and SQL
 1. Select **+ Record set** to create a new A record.
 1. Provide the name of your SQL Server VM as well as the private internal IP address.
 
-   ![Screenshot showing how to configure an A record.](./media/replication-two-instances-and-sql-server-configure-tutorial/configure-a-record.png)
+   :::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/configure-a-record.png" alt-text="Screenshot showing how to configure an A record." lightbox="media/replication-two-instances-and-sql-server-configure-tutorial/configure-a-record.png":::
 
 1. Select **OK** to create the A record.
 
@@ -172,7 +172,7 @@ A private DNS zone allows DNS routing between the SQL managed instances and SQL
 1. Select your subscription from the dropdown list, and then select the virtual network for your publisher SQL managed instance.
 1. Check the box next to **Enable auto registration**.
 
-   ![Screenshot showing how to create a VNet link.](./media/replication-two-instances-and-sql-server-configure-tutorial/configure-vnet-link.png)
+   :::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/configure-vnet-link.png" alt-text="Screenshot showing how to create a VNet link." lightbox="media/replication-two-instances-and-sql-server-configure-tutorial/configure-vnet-link.png":::
 
 1. Select **OK** to link your virtual network.
 1. Repeat these steps to add a link for the subscriber virtual network, with a name such as `Sub-link`.
@@ -182,11 +182,13 @@ A private DNS zone allows DNS routing between the SQL managed instances and SQL
 [Create an Azure storage account](/azure/storage/common/storage-account-create#create-a-storage-account) for the working directory, and then create a [file share](/azure/storage/files/storage-how-to-create-file-share) within the storage account.
 
 Copy the file share path in the format of:
+
 `\\storage-account-name.file.core.windows.net\file-share-name`
 
 Example: `\\replstorage.file.core.windows.net\replshare`
 
 Copy the storage access key connection string in the format of:
+
 `DefaultEndpointsProtocol=https;AccountName=<Storage-Account-Name>;AccountKey=****;EndpointSuffix=core.windows.net`
 
 Example: `DefaultEndpointsProtocol=https;AccountName=replstorage;AccountKey=123456789aBcDeFgHiJkLmNoPqRsTuVwXyZ==;EndpointSuffix=core.windows.net`
@@ -250,18 +252,20 @@ Once connectivity is established and you have a sample database, you can configu
 1. Open a **New Query** window, and run the following Transact-SQL code to configure distribution on the distributor SQL managed instance:
 
    ```sql
-   EXEC sp_adddistributor @distributor = 'sql-mi-distributor.b6bf57.database.windows.net', @password = '<distributor_admin_password>'
-
-   EXEC sp_adddistributiondb @database = N'distribution'
-
-   EXEC sp_adddistpublisher @publisher = 'sql-mi-publisher.b6bf57.database.windows.net', -- primary publisher
-        @distribution_db = N'distribution',
-        @security_mode = 0,
-        @login = N'azureuser',
-        @password = N'<publisher_password>',
-        @working_directory = N'\\replstorage.file.core.windows.net\replshare',
-        @storage_connection_string = N'<storage_connection_string>'
-        -- example: @storage_connection_string = N'DefaultEndpointsProtocol=https;AccountName=replstorage;AccountKey=123456789aBcDeFgHiJkLmNoPqRsTuVwXyZ==;EndpointSuffix=core.windows.net'
+   EXECUTE sp_adddistributor
+       @distributor = 'sql-mi-distributor.b6bf57.database.windows.net',
+       @password = '<distributor_admin_password>';
+
+   EXECUTE sp_adddistributiondb @database = N'distribution';
+
+   EXECUTE sp_adddistpublisher
+       @publisher = 'sql-mi-publisher.b6bf57.database.windows.net', -- primary publisher@distribution_db = N'distribution',
+       @security_mode = 0,
+       @login = N'azureuser',
+       @password = N'<publisher_password>',
+       @working_directory = N'\\replstorage.file.core.windows.net\replshare',
+       @storage_connection_string = N'<storage_connection_string>' -- example:
+       @storage_connection_string = N'DefaultEndpointsProtocol = https;AccountName = replstorage;AccountKey = 123456789aBcDeFgHiJkLmNoPqRsTuVwXyZ = = ;EndpointSuffix = core.windows.net';
    ```
 
    > [!NOTE]  
@@ -271,8 +275,12 @@ Once connectivity is established and you have a sample database, you can configu
 1. Open a **New Query** window, and run the following Transact-SQL code to register the distributor at the publisher:
 
    ```sql
-   Use MASTER
-   EXEC sys.sp_adddistributor @distributor = 'sql-mi-distributor.b6bf57.database.windows.net', @password = '<distributor_admin_password>'
+   USE master;
+   GO
+
+   EXECUTE sys.sp_adddistributor
+       @distributor = 'sql-mi-distributor.b6bf57.database.windows.net',
+       @password = '<distributor_admin_password>';
    ```
 
 ## Create the publication
@@ -290,7 +298,7 @@ Once distribution has been configured, you can create the publication. To do so,
 1. On the **Snapshot Agent** page, check the box next to **Create snapshot immediately and keep the snapshot available to initialize subscriptions**. Select **Next**.
 1. On the **Agent Security** page, select **Security Settings...**. Provide SQL Server login credentials to use for the Snapshot Agent and to connect to the publisher. Select **OK** to close the **Snapshot Agent Security** page. Select **Next**.
 
-   ![Screenshot showing how to configure Snapshot Agent security.](./media/replication-two-instances-and-sql-server-configure-tutorial/snapshot-agent-security.png)
+   :::image type="content" source="media/replication-two-instances-and-sql-server-configure-tutorial/snapshot-agent-security.png" alt-text="Screenshot showing how to configure Snapshot Agent security.":::
 
 1. On the **Wizard Actions** page, choose to **Create the publication** and (optionally) choose to **Generate a script file with steps to create the publication** if you want to save this script for later.
 1. On the **Complete the Wizard** page, name your publication `ReplTest`, and select **Next** to create your publication.
@@ -336,22 +344,28 @@ Once replication has been configured, you can test it by inserting new items on
 Run the following T-SQL snippet to view the rows on the subscriber:
 
 ```sql
-Use ReplSub
-select * from dbo.ReplTest
+USE ReplSub;
+GO
+
+SELECT *
+FROM dbo.ReplTest;
 ```
 
 Run the following T-SQL snippet to insert additional rows on the publisher, and then check the rows again on the subscriber.
 
 ```sql
-Use ReplTutorial
-INSERT INTO ReplTest (ID, c1) VALUES (15, 'pub')
+USE ReplTutorial;
+GO
+
+INSERT INTO ReplTest (ID, c1)
+VALUES (15, 'pub');
 ```
 
 ## Clean up resources
 
 1. Navigate to your resource group in the [Azure portal](https://portal.azure.com).
 1. Select the SQL managed instances, and then select **Delete**. Type `yes` in the text box to confirm you want to delete the resource, and then select **Delete**. This process might take some time to complete in the background, and until it's done, you'll not be able to delete the *virtual cluster* or any other dependent resources. Monitor the delete in the **Activity** tab to confirm your SQL managed instance has been deleted.
-1. Once the SQL managed instance is deleted, delete the _virtual cluster_ by selecting it in your resource group, and then choosing **Delete**. Type `yes` in the text box to confirm you want to delete the resource, and then select **Delete**.
+1. Once the SQL managed instance is deleted, delete the *virtual cluster* by selecting it in your resource group, and then choosing **Delete**. Type `yes` in the text box to confirm you want to delete the resource, and then select **Delete**.
 1. Delete any remaining resources. Type `yes` in the text box to confirm you want to delete the resource, and then select **Delete**.
 1. Delete the resource group by selecting **Delete resource group**, typing in the name of the resource group `myResourceGroup`, and then selecting **Delete**.
 
@@ -383,12 +397,12 @@ Using a forward slash instead of backslash in the file path for the file share c
 
 ### Couldn't connect to Subscriber
 
-```error-text
+```output
 The process could not connect to Subscriber 'SQL-VM-SUBSCRIBER
 Could not open a connection to SQL Server [53].
 A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections.
 ```
-T
+
 Possible solutions:
 
 - Ensure port 1433 is open.
