Merge pull request #34523 from MicrosoftDocs/VanMSFT-patch-1

remove Azure Synapse

Author: prmerger-automator[bot]

azure-sql/database/network-security-perimeter.md

@@ -1,25 +1,22 @@
 ---
 title: Network Security Perimeter
-titleSuffix: Azure SQL Database & Azure Synapse Analytics
+titleSuffix: Azure SQL Database
 description: Overview of Network Security Perimeter for Azure SQL Database
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: wiassaf, vanto, mathoma
-ms.date: 04/09/2025
+ms.date: 06/24/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: how-to
 ---
 
-# Network Security Perimeter for Azure SQL Database and Azure Synapse Analytics
+# Network Security Perimeter for Azure SQL Database
 
 [!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
 Network Security Perimeter (preview) secures both inbound and outbound network traffic between Azure SQL Database and other Platform as a Service (PaaS) resources (for example, Azure Storage and Azure Key Vault). Any attempts made to communicate with Azure resources that aren't inside the perimeter is blocked.
 
-> [!IMPORTANT]  
-> - This article applies to both Azure SQL Database and [dedicated SQL pool (formerly SQL DW)](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) in Azure Synapse Analytics. These settings apply to all SQL Database and dedicated SQL pool (formerly SQL DW) databases associated with the server. For simplicity, the term 'database' refers to both databases in Azure SQL Database and Azure Synapse Analytics. Likewise, any references to 'server' is referring to the [logical SQL server](logical-servers.md) that hosts Azure SQL Database and dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics. This article does *not* apply to Azure SQL Managed Instance or dedicated SQL pools in Azure Synapse Analytics workspaces.
-
 ## Getting Started
 
 1. In the Azure portal, search for **Network Security Perimeter** in the resource list and then select **Create**.