You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-sql/database/network-security-perimeter.md
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Overview of Network Security Perimeter for Azure SQL Database
5
5
author: VanMSFT
6
6
ms.author: vanto
7
7
ms.reviewer: wiassaf, vanto, mathoma
8
-
ms.date: 11/19/2024
8
+
ms.date: 04/09/2025
9
9
ms.service: azure-sql-database
10
10
ms.subservice: security
11
11
ms.topic: how-to
@@ -20,15 +20,31 @@ Network Security Perimeter (preview) secures both inbound and outbound network t
20
20
> [!IMPORTANT]
21
21
> - 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.
22
22
23
-
## Associate SQL Database with a Network Security Perimeter in the Azure portal
23
+
## Getting Started
24
24
25
-
1. Search for **Network Security Perimeter** in the Azure portal search bar and then select the **Create** button and create the resource.
26
-
1. Provide a **Name** and **Region** and choose the subscription.
27
-
1. Under the **Resources** section, select the **Associate** button and navigate to the SQL Database you want to add.
25
+
1. In the Azure portal, search for **Network Security Perimeter** in the resource list and then select **Create**.
28
26
29
27
:::image type="content" source="media/network-security-perimeter/associate-sql-network-security-perimeter.png" alt-text="Screenshot of creating a network security perimeter in the Azure portal.":::
30
28
31
-
1. Go through the rest of the creation process without entering anything in **Inbound access rules** or **Outbound access rules**.
29
+
1. Provide a **Name** and **Region** and choose the subscription.
30
+
1. Under the **Resources** section, select the **Add** button and navigate to the SQL Database you want to associate with the perimeter.
31
+
1. Add an Inbound access rule. The source type can be either an IP address, a subscription, or other network security perimeters.
32
+
1. Add an Outbound access rule to allow resources inside the perimeter to connect to resources outside the perimeter
33
+
34
+
If you already have an existing Azure SQL Database and are looking to add security perimeter, use the following steps:
35
+
36
+
1. In the Azure portal, search for the existing Network Security Perimeter.
37
+
1. Select **Associated Resources** from the **Settings** menu.
38
+
1. Select the **Add** button and select **Associate resources with an existing profile**.
39
+
40
+
:::image type="content" source="media/network-security-perimeter/associated-resources-sql-network-security-perimeter.png" alt-text="Screenshot of associated resources for network security perimeter in the Azure portal.":::
41
+
42
+
1. Select your **Profile** from the dropdown and select **Add**.
43
+
44
+
:::image type="content" source="media/network-security-perimeter/select-associated-resources-sql-network-security-perimeter.png" alt-text="Screenshot of adding an associated resource for network security perimeter in the Azure portal.":::
45
+
46
+
1.**Search** for your SQL Database resource, **Select** the required resource, and select **Associate**.
47
+
32
48
33
49
## Using SQL Database with a Network Security Perimeter
34
50
@@ -41,6 +57,7 @@ Login failed because the network security perimeter denied inbound access.
41
57
42
58
## Related content
43
59
60
+
-[What is a network security perimeter?](/azure/private-link/network-security-perimeter-concepts)
44
61
-[Quickstart: Create a network security perimeter - Azure portal](/azure/private-link/create-network-security-perimeter-portal)
45
62
-[Quickstart: Create a network security perimeter - Azure PowerShell](/azure/private-link/create-network-security-perimeter-powershell)
46
63
-[Quickstart: Create a network security perimeter - Azure CLI](/azure/private-link/create-network-security-perimeter-cli)
0 commit comments