"Unexpected Error" on Mirrored DB for PostgreSQL UI When Creating VNET Gateway Connection

[dg321]

Hi Team, I'm following the tutorial here to set up a connection from my Azure PostgreSQL DB to a Fabric Mirrored DB: Connect to Azure Database for PostgreSQL – Flexible Server

When I try to create a new connection using a VNET gateway via the Mirrored DB for PostgreSQL UI, I encounter an "unexpected error" and the connection fails. 

As a workaround, I’m able to create the same connection with identical parameters via the Manage Connections page, and then use that connection to successfully create the Mirrored DB. This suggests the issue is specific to the Mirrored DB for PostgreSQL UI. Please advise if this is a known issue or if there’s a fix planned.

[dg321]

I am trying to replicate the same using an Azure SQL Database. I get the same unexpected error on the Mirrored Azure SQL Database UI so I tried using the Manage Connections pane as you'll mentioned. But I am unable to find the connection type: "Azure SQL Database" in the list provided there. Could someone please help me with the correct connection type I should be using?

[v-menakakota]

Hi @dg321 ,

You won’t see a separate Azure SQL Database option in Manage Connections. Please select SQL Server as the connection type and enter your Azure SQL server name (e.g. servername.database.windows.net) with the right authentication.

Please go through the below documents which may help you in resolving the issue:
Tutorial: Configure Microsoft Fabric Mirrored Databases From Azure SQL Database - Microsoft Fabric |...

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Community Support Team  

[v-menakakota]

Hi @dg321  ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.

Best Regards, 
Community Support Team 

[v-menakakota]

Hi @dg321  , 

Thanks for reaching out to the Microsoft fabric community forum. 

I would also take a moment to thank @Vinodh247 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference. 

You can create the VNET gateway connection through the Manage Connections page and then use it for your Mirrored DB. At present, there’s no official documentation that calls out the Mirrored DB UI issue, so the Manage Connections path is the recommended approach until updates are available

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Community Support Team.

[v-menakakota]

Hi @dg321  ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.

Best Regards, 
Community Support Team 

[Vinodh247]

Continue using the Manage Connections page to configure your VNET gateway connection and proceed to create the Mirrored DB using that. That's a valid and effective stopgap i believe. There’s no official documentation calling out this bug, and no public roadmap confirmation yet. It’s not in the Learn docs or the tutorial itself, and there’s no acknowledgment in the Fabric mirroring troubleshooting guidance that specifically addresses UI failure in the Mirrored DB for PostgreSQL UI.