Reason: An instance-specific error occurred while establishing a connection to SQL Server. Connection was denied because Deny Public Network Access is set to Yes. For more information,

Hi Gunti GUNTI •

Greetings!!

Reason: An instance-specific error occurred while establishing a connection to SQL Server. Connection was denied because Deny Public Network Access is set to Yes. For more information,

Azure SQL Database has a “Deny Public Network Access” setting. When this is set to Yes, it blocks all connections that are not from:

• A private endpoint (via Azure Private Link), or
• A virtual network rule (if using VNet service endpoints)

Option 1: Enable Public Network Access

If you want to allow public access (e.g., from your local machine or a public IP):

1. Go to the Azure Portal.
2. Navigate to your SQL Server (not the database).
3. Under Networking, set Public network access to “Selected networks” or “All networks”.
4. Add your client IP address to the Firewall rules.
5. Save the changes and try connecting again.

Option 1: Use Private Endpoint or VNet Integration.

If you want to keep public access disabled (recommended for production):

1. Create a Private Endpoint for your SQL Server in the same VNet as your client or application.
2. Ensure DNS resolution is configured to resolve the SQL Server name to the private IP.
3. Connect from a VM or service within the same VNet or peered VNet.

The issue occurs if the application can't connect to the server.

To resolve this issue, try the steps (in the order presented) in the Steps to fix common connection issues section.

I hope this information helps. Please do let us know if you have any further queries.