Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
I have an Azure SQL Service database that is set up with a private endpoint. The public network access is disabled. When I used Mirrored Azure SQL Database and entered credential (Organization account) it displayed an error message related to the public network access being disabled.
I can connect to my private Azure SQL Service if I use another task (e.g., copy). I've already set up a managed private endpoint, also deployed an on-premises data gateway. But this mirrored Azure SQL doesn't seem to be supported as I don't see the Gateway option in the configuaration page.
Your suggestion would be greatly appreciated.
Solved! Go to Solution.
Hi @thuanss,
Thanks for reaching out to the Microsoft fabric community forum.
Currently, Azure SQL Database mirroring does not support logical servers that are behind an Azure Virtual Network or private networking. If your Azure SQL Database instance is configured within a private network, you will not be able to enable mirroring.
To use Azure SQL Database mirroring, you need to update your Azure SQL logical server firewall rules to allow public network access. Additionally, you must enable the "Allow Azure services" option to permit connections to your Azure SQL Database logical server.
Please refer the below link for better understanding:
https://learn.microsoft.com/en-us/fabric/release-plan/data-factory#open-mirroring
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
This is a big limitation as public network access is not an option for enterprises from security point. Is the support for private network access in the roadmap and any ETA when it will be available?
Hi @thuanss,
Thanks for reaching out to the Microsoft fabric community forum.
Currently, Azure SQL Database mirroring does not support logical servers that are behind an Azure Virtual Network or private networking. If your Azure SQL Database instance is configured within a private network, you will not be able to enable mirroring.
To use Azure SQL Database mirroring, you need to update your Azure SQL logical server firewall rules to allow public network access. Additionally, you must enable the "Allow Azure services" option to permit connections to your Azure SQL Database logical server.
Please refer the below link for better understanding:
https://learn.microsoft.com/en-us/fabric/release-plan/data-factory#open-mirroring
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Thanks for the information. I hope to hear more from Microsoft on when this is supported.
Hello @thuanss
Hope you are doing good.
I have consulted with our internal experts regarding this matter. Currently, Microsoft has not announced a release date. However, based on expert insights and documentation, it is clear that Microsoft is actively working on it.
As per the documentation below, private endpoints in mirroring are not supported at this time. However, if you require support for items such as notebooks, lakehouses, and Spark job definitions, these are supported. Please refer to the document below for additional information.
Overview of managed private endpoints for Microsoft Fabric - Microsoft Fabric | Microsoft Learn
We appreciate your patience and understanding.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Hi @thuanss,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
User | Count |
---|---|
33 | |
14 | |
6 | |
3 | |
2 |
User | Count |
---|---|
39 | |
22 | |
11 | |
7 | |
6 |