0

Suppose I have an Azure SQL Database Elastic Pool and I am accessing it from an Azure Web App via Firewall rules and everything is working fine.

Now suppose I want to add a new Private Endpoint to the Azure SQL Database Elastic Pool. This would NOT block access via the existing Firewall rules / access outside of the newly created Private Endpoint - is that right?

In other words, adding a Private Endpoint is not saying that access should now be Exclusive through the Private Endpoint but that the Private Endpoint is accessible and existing access channels are also still accessible - is that right?

Improve this question
2
  • 1
    I'm missing a bit of info: Does the web app have a public endpoint at the moment? Does the SQL Database have a public endpoint at the moment? Am I correct in assuming that the connection string in the webapp connects to the public endpoint of the SQL Database?
    – Dresse
    Oct 21, 2021 at 13:29
  • @Dresse Yes, and yes. Yes. So the question really is, does adding a Private Endpoint, but not removing the public one, cause downtime on the public endpoint?
    – A X
    Oct 25, 2021 at 0:39

1 Answer 1

Reset to default
1

I would suggest to carefully read the following article which basically answers your question. By default, adding a private endpoint would not block access to the public endpoint but it all depends on the connectivity settings that are configured.

https://docs.microsoft.com/en-us/azure/azure-sql/database/connectivity-settings

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .