Unable to access to server through public endpoint while server id created as private access

Question

Unable to access to server through public endpoint while server id created as private access

Haseeb Ahmad 0

I am facing an issue with my Azure MySQL Flexible Server. I created the server with private access, and because of that, I am unable to access it through a public endpoint. I am also unable to establish a connection from Azure Data Factory (ADF) pipelines and Power BI.

How can I resolve this issue? I need access to the server.

Kalyani Kondavaradala 4,595 Reputation points Microsoft External Staff Moderator

2025-11-28T12:37:20.27+00:00

Hi Haseeb Ahmad

Just checking to see if you have a chance to check latest response from Vinod helpful, do let me know if you have any further questions on this.

1 answer

Your answer

Kalyani Kondavaradala 4,595 Reputation points Microsoft External Staff Moderator

2025-11-28T12:37:20.27+00:00

Hi Haseeb Ahmad

Just checking to see if you have a chance to check latest response from Vinod helpful, do let me know if you have any further questions on this.

Answer 1

Vinodh247 40,031 MVP Volunteer Moderator

If the server was created with private access, it has no public endpoint, so anything outside the private network cannot reach it. ADF and PBI will fail unless they are inside the same virtual network.

To fix it, you have only two options:

Use private networking end to end
- Place ADF inside a Managed VNet and use an IR that can reach the MySQL private endpoint.
- For PBI, use PBI Gateway installed on a machine that has network access to the VNet.
Recreate the server with public access Azure MySQL Flexible Server does not allow switching from private to public after creation.
```
  If you need a public endpoint, you must create a new server with public access and migrate the data.
```

There is no workaround. The server’s network mode is fixed after creation.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Haseeb Ahmad 0 Reputation points

2025-11-26T08:15:08.66+00:00

Thank you for the detailed explanation.

I have one follow-up question:
Can this issue be resolved by moving the server to “Private Link”?
Since the server is currently created with private access, I want to understand whether enabling or configuring Private Link can help in allowing access from services like Azure Data Factory and Power BI.

Also, could you please explain clearly:

What exactly is Azure Private Link and how does it work in the context of Azure MySQL Flexible Server?

I want to understand whether Private Link can expose the server in any controlled way, or if it still requires the same virtual network constraints.
Vinodh247 40,031 Reputation points MVP Volunteer Moderator

2025-11-27T04:26:32.0633333+00:00
No, Private Link will not fix your issue. Your MySQL Flexible Server is already in VNet-integrated (private access) mode, and you cannot convert it to public access or expose it through Private Link.

Private Link gives you a private IP inside your VNet that connects to a public PaaS service through an internal Microsoft backbone route.

You normally use it when a service has a public endpoint, but you want to access it privately. Examples: Storage, SQL Database, MySQL Flexible Server (only when created in public access mode).

Share via

Unable to access to server through public endpoint while server id created as private access

1 answer

Your answer