This article answers frequently asked questions about Mirroring Azure Database for MySQL in Microsoft Fabric.
Features and capabilities
What authentication to the Azure Database for MySQL is allowed?
We support Basic (MySQL Authentication) for database users. Microsoft Entra ID authentication isn't currently supported. For more information, see Configure Microsoft Fabric mirrored databases from Azure Database for MySQL.
Is there a staging or landing zone for Azure Database for MySQL? If so, is it outside of OneLake?
A landing zone in OneLake stores both the snapshot and change data, to improve performance when converting files into delta tables.
How long does the initial replication take?
It depends on the size of the data that's being brought in.
How long does it take to replicate inserts/updates/deletes?
Near real-time latency.
Do you support replicating of views, partitioned or external tables?
No. Currently, only replicating regular tables are supported.
How do I manage connections?
Select the settings cog, then select on Manage connection and gateways. You can also delete existing connections from this page.
Can Power BI reports on mirrored data use direct lake mode?
Yes, since tables are all v-ordered delta tables.
Self-help for Mirroring Azure Database for MySQL in Microsoft Fabric
How do I know Fabric is replicating data on my Azure Database for MySQL?
If you're experiencing mirroring problems, perform the following server level checks using system views and functions to validate configuration. Contact support if troubleshooting is required.
- Execute the following query to check if binary logging is enabled and properly configured:
SHOW VARIABLES LIKE 'log_bin%';
For troubleshooting steps, see Troubleshoot Fabric mirrored databases from Azure Database for MySQL.
How to enable System assigned managed identity (SAMI) on Azure Database for MySQL?
With a single step in the Azure portal, you can enable System Assigned Managed Identity (SAMI) of your Azure Database for MySQL.
What are the replication statuses?
Can Azure Database for MySQL be virtual network integrated or only accessible through a Private Endpoint?
Yes, to access an Azure Database for MySQL that doesn't support public connectivity you can create a virtual network data gateway.
What steps does restarting the Mirroring include?
The data from source tables will be reinitialized. Each time you stop and start, the entire table is fetched again.
What happens if I remove a table from Mirroring?
The table is no longer replicated and its data is deleted from OneLake.
If I delete the Mirror, does it affect the source Azure Database for MySQL?
No, we just remove the replication configuration.
Can I mirror the same source database multiple times?
No, each Azure Database for MySQL can only be mirrored once. You just need a single copy of the data in Fabric OneLake, which you can share with others.
Can I mirror only specific tables from my Azure Database for MySQL databases?
Yes, specific tables can be selected during Mirroring configuration.
What happens to Mirroring during an HA failover for my Azure Database for MySQL?
Mirroring will continue transparently after an HA failover, as MySQL binary log replication handles failover scenarios automatically.
Security
Is data ever leaving the customers Fabric tenant?
No.
Is data staged outside of a customer environment?
No. Data isn't staged outside of customer environment, only in the customer's OneLake.
Cost Management
What are the costs associated with Mirroring?
There's no compute cost for mirroring data from the source to Fabric OneLake. The Mirroring storage cost is free up to a certain limit based on the purchased compute capacity SKU you provision. Learn more from the Mirroring section in Microsoft Fabric - Pricing.
What do we recommend a customer do to avoid or reduce Azure Database for MySQL costs?
See Plan and manage costs for Azure Database for MySQL. Consider using a dedicated, smaller Azure Database for MySQL, based on requirements.
How are ingress fees handled?
Fabric doesn't charge for Ingress fees into OneLake for Mirroring.
How are egress fees handled?
If the Azure Database for MySQL is located in a different region from your Fabric capacity, data egress is charged. If in the same region, there's no data egress.
Licensing
What are licensing options for Fabric Mirroring?
A Power BI Premium, Fabric Capacity, or Trial Capacity is required. For more information on licensing, see Microsoft Fabric licenses.
Stop or pause Fabric Mirroring
What are the results of stopping Mirroring?
Replication stops in the source database, but a copy of the tables is kept in OneLake. Restarting the mirroring results in all data being replicated from the start.
What if I stop or pause my Fabric capacity?
The Fabric capacity needs to be active and running. A paused or deleted capacity will impact Mirroring and no data are replicated.