Skip to content

azure-database-mysql-limitations.md

Latest commit

 

History

History
84 lines (47 loc) · 4.17 KB

azure-database-mysql-limitations.md

File metadata and controls

84 lines (47 loc) · 4.17 KB
title Limitations in Microsoft Fabric Mirrored Databases from Azure Database for MySQL (Preview)
description Learn about the limitations for mirrored databases from Azure Database for MySQL in Microsoft Fabric.
ms.reviewer vamehta, jingwang, maghan
ms.date 03/18/2026
ms.topic concept-article
ai-usage ai-assisted

Limitations in Microsoft Fabric mirrored databases from Azure Database for MySQL (preview)

This article lists current limitations in the Microsoft Fabric mirrored databases from Azure Database for MySQL. This article is subject to change.

For troubleshooting, see:

Troubleshoot Fabric mirrored databases

Troubleshoot Fabric mirrored databases from Azure Database for MySQL.

Server level limitations

The following limitations apply at the MySQL server level when configuring mirroring in Microsoft Fabric.

  • Mirroring in Fabric supports MySQL versions 8.0 (8.0.x, starting from 8.0.21).

  • The Burstable Compute Tier isn't supported.

  • Custom ports or High Availability (HA) aren't supported.

  • You can't configure mirroring in Fabric on a Read Replica server.

  • Entra ID Authentication isn't supported.

  • Recovering a server with Mirroring in Fabric enabled through Point in Time Restore (PITR) requires Mirroring to be reconfigured on the new server.

  • Before executing a Major Version Upgrade (MVU), disable Mirroring in Fabric and re-enable it once the upgrade finishes.

Database level limitations

The following limitations apply to individual databases when using mirroring in Microsoft Fabric.

  • Mirroring multiple databases on the same server isn't supported.

  • After you configure a mirrored database, you can't add or remove tables.

  • The maximum number of tables that you can mirror into Fabric is 1,000 tables.

  • You can't replicate a database named fabric_info because it's reserved for system use.

Network and connectivity security

Mirroring requires extra configuration for network-isolated servers.

  • Virtual Network enabled Azure MySQL servers aren't supported for Fabric Mirroring.

  • If your server isn't publicly accessible and doesn't allow Azure services to connect to it, you can create a virtual network data gateway to mirror the data. Make sure the Azure Virtual Network or the gateway machine's network can connect to the Azure Database for MySQL flexible server when allowed by the firewall rule.

Table level

Certain table configurations and data types have limitations when mirroring to Fabric.

  • You can't mirror a table if it doesn't have a primary key.

  • DDL operations (for example, ALTER TABLE, TRUNCATE, DROP TABLE) are unsupported and might disrupt replication.

  • The following MySQL data types aren't supported: tinytext, text, mediumtext, longtext, tinyblob, blob, mediumblob, longblob. Tables containing unsupported data types are mirrored excluding the columns containing unsupported data types.

  • Database and table names are case-sensitive. When setting up a mirrored database, ensure the input matches the MySQL settings.

SQL analytics endpoint limitations

The SQL analytics endpoint for mirrored databases has the same limitations as the Lakehouse SQL analytics endpoint.

Supported regions

All Microsoft Fabric regions support database mirroring and open mirroring. For more information, see Fabric region availability.

Related content