azure-database-mysql-mirroring-faq.yml

### YamlMime:FAQ
metadata:
  title: "Frequently asked questions for Mirroring Azure Database for MySQL in Microsoft Fabric (preview)"
  description: This article answers frequently asked questions about Mirroring Azure Database for MySQL in Microsoft Fabric.
  ms.reviewer: vamehta, jingwang, maghan
  ms.topic: faq
  ms.date: 03/18/2026
title: "Frequently asked questions for Mirroring Azure Database for MySQL in Microsoft Fabric (preview)"
summary: |
  This article answers frequently asked questions about Mirroring Azure Database for MySQL in Microsoft Fabric.

sections:
  - name: Features and capabilities
    questions:
      - question: |
          What authentication to the Azure Database for MySQL is allowed? 
        answer:
          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](azure-database-mysql-tutorial.md).

      - question: |
          Is there a staging or landing zone for Azure Database for MySQL? If so, is it outside of OneLake? 
        answer: 
          A landing zone in OneLake stores both the snapshot and change data, to improve performance when converting files into delta tables.

      - question: |
          How long does the initial replication take? 
        answer: 
          It depends on the size of the data that's being brought in. 

      - question: |
          How long does it take to replicate inserts/updates/deletes? 
        answer: 
          Near real-time latency.
      - question: |
          Do you support replicating of views, partitioned or external tables? 
        answer: 
          No. Currently, only replicating regular tables are supported.

      - question: |
          How do I manage connections? 
        answer: 
          Select the settings cog, then select on **Manage connection and gateways**. You can also delete existing connections from this page.

      - question: |
          Can Power BI reports on mirrored data use direct lake mode?
        answer: 
          Yes, since tables are all v-ordered delta tables.

  - name: Self-help for Mirroring Azure Database for MySQL in Microsoft Fabric
    questions:
      - question: |
          How do I know Fabric is replicating data on my Azure Database for MySQL? 
        answer: |
           If you're experiencing mirroring problems, perform the following server level checks using system views and functions to validate configuration. [Contact support](/power-bi/support/service-support-options) if troubleshooting is required.
           - Execute the following query to check if binary logging is enabled and properly configured: 
              ```sql
              SHOW VARIABLES LIKE 'log_bin%';
              ```

           For troubleshooting steps, see [Troubleshoot Fabric mirrored databases from Azure Database for MySQL](azure-database-mysql-troubleshoot.md).
      - question: |
          How to enable System assigned managed identity (SAMI) on Azure Database for MySQL? 
        answer: |
          With a single step in the Azure portal, you can [enable System Assigned Managed Identity (SAMI) of your Azure Database for MySQL](azure-database-mysql-tutorial.md#prepare-your-azure-database-for-mysql).

      - question: |
          What are the replication statuses? 
        answer: 
          See [Monitor Fabric Mirror replication](monitor.md).

      - question: |
          Can Azure Database for MySQL be virtual network integrated or only accessible through a Private Endpoint? 
        answer: 
          Yes, to access an Azure Database for MySQL that doesn't support public connectivity you can [create a virtual network data gateway](/data-integration/vnet/create-data-gateways).

      - question: |
          What steps does restarting the Mirroring include? 
        answer: 
           The data from source tables will be reinitialized. Each time you stop and start, the entire table is fetched again.

      - question: |
           What happens if I remove a table from Mirroring?
        answer: 
           The table is no longer replicated and its data is deleted from OneLake.

      - question: |
          If I delete the Mirror, does it affect the source Azure Database for MySQL? 
        answer: 
          No, we just remove the replication configuration.

      - question: |
          Can I mirror the same source database multiple times? 
        answer: 
          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.

      - question: |
          Can I mirror only specific tables from my Azure Database for MySQL databases? 
        answer: 
          Yes, specific tables can be selected during Mirroring configuration.

      - question: |
          What happens to Mirroring during an HA failover for my Azure Database for MySQL? 
        answer: 
          Mirroring will continue transparently after an HA failover, as MySQL binary log replication handles failover scenarios automatically.
  - name: Security
    questions:
      - question: |
          Is data ever leaving the customers Fabric tenant? 
        answer: 
          No. 
      - question: |
          Is data staged outside of a customer environment? 
        answer: 
          No. Data isn't staged outside of customer environment, only in the customer's OneLake.

  - name: Cost Management 
    questions:
      - question: |
          What are the costs associated with Mirroring?
        answer: 
          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](https://azure.microsoft.com/pricing/details/microsoft-fabric/).
      - question: |
          What do we recommend a customer do to avoid or reduce Azure Database for MySQL costs? 
        answer: 
          See [Plan and manage costs for Azure Database for MySQL](/azure/mysql/flexible-server/concept-monitoring-best-practices). Consider using a dedicated, smaller Azure Database for MySQL, based on requirements.
      - question: |
          How are ingress fees handled? 
        answer: 
          Fabric doesn't charge for Ingress fees into OneLake for Mirroring.
      - question: |
          How are egress fees handled?
        answer: 
          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.

  - name: Licensing
    questions:
      - question: |
          What are licensing options for Fabric Mirroring? 
        answer:
          A Power BI Premium, Fabric Capacity, or Trial Capacity is required. For more information on licensing, see [Microsoft Fabric licenses](../enterprise/licenses.md).

  - name: Stop or pause Fabric Mirroring
    questions:

      - question: |
          What are the results of stopping Mirroring?
        answer: 
          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.

      - question: | 
          What if I stop or pause my Fabric capacity?
        answer: |
          The Fabric capacity needs to be active and running. A paused or deleted capacity will impact Mirroring and no data are replicated.

additionalContent: |

  ## Related content

  - [What is Mirroring in Fabric?](overview.md)
  - [Azure Database for MySQL mirroring in Microsoft Fabric](azure-database-mysql.md)
  - [Troubleshoot Fabric mirrored databases from Azure Database for MySQL](azure-database-mysql-troubleshoot.md).