Blog Post

Azure SQL Blog
6 MIN READ

MI link support for multiple databases in an Always On availability group is now generally available

danimir's avatar
danimir
Icon for Microsoft rankMicrosoft
Nov 17, 2026

Multi-database MI link mode is now generally available, enabling multiple databases in an Always On availability group to replicate between SQL Server and Azure SQL Managed Instance through a single MI link.

We are excited to announce the general availability of multi-database mode for MI link, which enables you to replicate multiple databases in an Always On availability group between SQL Server and Azure SQL Managed Instance through a single MI link.

Managed Instance link provides near-real-time database replication between SQL Server and Azure SQL Managed Instance, helping you modernize to Azure at your own pace. Built on distributed availability group technology, MI link provides a secure and reliable connection between SQL Server and Azure SQL Managed Instance and can be used for migration, disaster recovery, and hybrid scenarios.

With multi-database mode, you can extend an existing Always On availability group to Azure SQL Managed Instance and replicate all databases in that availability group through a single MI link. You can also start with standalone databases. When standalone databases are selected in SQL Server Management Studio (SSMS), the wizard creates a single-node availability group and adds the selected databases to it.

With general availability, multi-database mode makes it easier to manage scenarios involving multiple databases while maintaining the flexibility and near-real-time replication provided by MI link.

What’s new with general availability

General availability introduces these important updates compared with the public preview:

  • All Azure SQL Managed Instance update policies are now supported, including the SQL Server 2022 update policy, which was not supported during the public preview. You can now set up bidirectional multi-database MI link mode between SQL Server 2022 and Azure SQL Managed Instance using the SQL Server 2022 update policy. Note that SQL Server 2025 and Managed Instances using the SQL Server 2025 update policy have been supported since public preview.
  • With SQL Server 2022 CU11 and SQL Server 2025 CU28, we are introducing three new stored procedures to improve supportability and troubleshooting of MI link in multi-database mode:
    • sys.sp_milink_check - provides information about the replication health of individual databases in multi-database mode. Use this stored procedure to determine whether an individual database is stuck in seeding or replication.
    • sys.sp_milink_reseed - restarts seeding for individual databases that are stuck in seeding in multi-database mode without requiring you to remove and re-add the database to the availability group.
    • sys.sp_milink_repair - repairs an unhealthy replication for an individual database in multi-database mode link.
  • Use SQL Server Management Studio (SSMS) 22.12.1 when configuring and managing MI link in multi-database mode. This version includes a number of experience improvements and bug fixes.

We are also introducing better support for multiple SQL Server nodes in Always On availability groups:

  • Multi-node availability group support in the MI link wizard (preview) enables automatic configuration of all server nodes in an Always On availability group with MI link, allowing the link to persist after an availability group failover. Instead of configuring each server node yourself, the MI link wizard can configure all server nodes for you. This SSMS feature is in preview and must be enabled by selecting Tools > Manage Preview Features in SSMS.

Support for the SQL Server 2022 update policy expands the range of SQL Managed Instance environments that can take advantage of multi-database mode and provides greater flexibility when planning migrations and hybrid configurations. Multi-node availability group support in the MI link wizard (preview) eliminates the need to manually configure each server node, saving time and helping ensure that the MI link persists across local availability group failovers.

How multi-database mode works

With multi-database mode, MI link extends an Always On availability group between SQL Server and Azure SQL Managed Instance. A single link replicates multiple databases in the availability group to the target replica.

The link uses a distributed availability group to replicate changes in near real time from the current primary replica to database copies on the secondary replica, keeping the databases synchronized.

You can:

  • Extend an existing Always On availability group to Azure SQL Managed Instance.
  • Start with standalone SQL Server databases and let SSMS create the availability group.
  • Add or remove databases from the availability group as your environment evolves.
  • Fail over or cut over the availability group to Azure SQL Managed Instance when you are ready.

This approach simplifies working with applications that rely on multiple databases because the databases can be managed and migrated together through a single MI link rather than through separate links for each database.

Supportability

RequirementDetails
SQL Server

SQL Server 2022 with CU27 and later or SQL Server 2025 with CU9 and later. Enterprise or Developer edition.

Standard edition is not supported for multi-database mode because Basic availability groups support only a single database.

Azure SQL Managed Instance

All service tiers, General Purpose, Next-Gen and Business Critical are supported. Use the following Azure SQL Managed Instance update policy for the following configurations:

For one-way replication from SQL Server to Azure SQL Managed Instance:

  • For one-way replication from SQL Server 2022, use Azure SQL Managed Instance with update set to SQL Server 2022, SQL Server 2025, or Always-up-to-date. 
  • For one-way replication from SQL Server 2025, use Azure SQL Managed Instance with update policy set to SQL Server 2025, or Always-up-to-date. SQL Server 2022 update policy is not supported.

For two-way replication and bidirectional failover (role-reversal) between SQL Server and Azure SQL Managed Instance, the update policy must match the exact version of your SQL Server:

  • For bidirectional replication and failover between SQL Server 2022 and Azure SQL Managed Instance, use SQL Server 2022 update policy only. Other update policies are not supported. 
  • For bidirectional replication and failover between SQL Server 2025 and Azure SQL Managed Instance, use SQL Server 2025 update policy only. Other update policies are not supported. 
SSMSSSMS 22.12.1 or later for the multi-database link capability.
AutomationAz module 16.3.0 or later and Az.Sql 7.1.0 or later, or the corresponding Azure APIs.

One link for an existing multi-database availability group

If you already use an Always On availability group, multi-database link mode lets you extend the complete database group to Azure SQL Managed Instance without creating a separate availability group for every database. All databases in the link move together as one managed group. Databases on the primary are read-write, while their copies on the secondary are read-only. Use of your existing Always On AG listener endpoint is supported with multi-database mode MI link, allowing the link to remain operational after a local AG failover.

Image 1: A multi-database Always On availability group replicated to Azure SQL Managed Instance through one Managed Instance link.

The diagram illustrates the availability group relationship rather than a specific Azure SQL Managed Instance service-tier replica count. Managed Instance link is supported across all Azure SQL Managed Instance service tiers.

Run multiple links in different directions

A single SQL Server instance can participate in multiple links. Each link can carry a different availability group, and supported links can replicate in different directions at the same time.

In the following example, AG1 (containing DB1, DB2, and DB3) replicates from SQL Server to Azure SQL Managed Instance through MI link 1. AG2 (containing DB4, DB5, and DB6) replicates from Azure SQL Managed Instance to SQL Server through MI link 2. Both links can operate at the same time between the two instances.

Image 2: Two multi-database availability groups using separate links with opposite replication directions.

Important: Database names must be unique in this configuration. A database cannot be renamed on the secondary while it is participating in replication to resolve a naming conflict.

Replicate one availability group to multiple managed instances

Multi-database mode also supports fan-out topologies. You can replicate multiple availability groups to one managed instance, or replicate the same availability group to different managed instances. For example, separate links can target managed instances in different Azure regions.

Image 3: One multi-database availability group replicated through separate links to two Azure SQL managed instances.

Get started

To use MI link multi-database mode, install SSMS 22.12.1 and make sure that your SQL Server and Azure SQL Managed Instance environments meet the requirements for the scenario you want to configure.

To enable automatic configuration of multiple server nodes in your availability group, in SSMS select Tools > Manage Preview Features, and select "Enable multi-node availability group support in the Managed Instance link wizard."

Learn more about configuring MI link with multiple databases in an Always On availability group.

Share your feedback

We would love to hear about your experience with multi-database mode. Please share questions, feedback, and feature suggestions through the Managed Instance link feedback form.

Updated Nov 17, 2026
Version 1.0