From c34f847a92bb3087c7343d8759b48a0ba4790c64 Mon Sep 17 00:00:00 2001
From: Iceman3900 <110161896+Iceman3900@users.noreply.github.com>
Date: Mon, 13 Jul 2026 09:41:25 +0200
Subject: [PATCH] Update Azure SQL Server Network access details

Added information about firewall bypass for Azure SQL Server when allowing Azure services access.
---
 src/pentesting-cloud/azure-security/az-services/az-sql.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/pentesting-cloud/azure-security/az-services/az-sql.md b/src/pentesting-cloud/azure-security/az-services/az-sql.md
index 53e505835..1edb52f4f 100644
--- a/src/pentesting-cloud/azure-security/az-services/az-sql.md
+++ b/src/pentesting-cloud/azure-security/az-services/az-sql.md
@@ -21,6 +21,8 @@ Azure SQL consists of four main offerings:
 - Private endpoints.
 - It’s also possible to restrict connections based on domain names.
 - It’s also possible to allow Azure services to access it (like to use the Query editor in the portal or to allow an Azure VM to connect).
+  - If an SQL Server has *Allow Azure services and resources to access this server* set to "Enabled", Azure will automatically create a hidden firewall rule that allows all network traffic originating from Azure to connect to the SQL Server — including resources from any tenant.
+  - This means that if you obtain valid SQL credentials, you can connect to the victim Azure SQL Server from an Azure VM inside your own attacker‑controlled tenant. [The MS docs explains this](https://learn.microsoft.com/en-us/azure/azure-sql/database/network-access-controls-overview?view=azuresql#allow-azure-services)
 
 **Authentication Methods:**