Skip to content

Commit 58c1f6b

Browse files
author
Michael Bender
committed
minor updates
1 parent 498a096 commit 58c1f6b

6 files changed

+47
-35
lines changed

articles/private-link/create-network-security-perimeter-cli.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -18,19 +18,16 @@ Get started with network security perimeter by creating a network security perim
1818
## Prerequisites
1919

2020
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
21+
22+
[!INCLUDE [network-security-perimeter-add-preview](../../includes/network-security-perimeter-add-preview.md)]
23+
2124
- The [latest Azure CLI](/cli/azure/install-azure-cli), or you can use Azure Cloud Shell in the portal.
2225
- This article **requires version 2.38.0 or later** of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
2326
- After upgrading to the latest version of Azure CLI, import the network security perimeter commands using `az extension add --name nsp`.
24-
- Re-register the `Microsoft.Network` resource provider with the following command:
25-
26-
```azure
27-
az provider register --namespace Microsoft.Network
28-
```
2927

3028
[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
3129

3230

33-
[!INCLUDE [network-security-perimeter-add-preview](../../includes/network-security-perimeter-add-preview.md)]
3431

3532

3633
## Connect to your Azure account and select your subscription

articles/private-link/create-network-security-perimeter-powershell.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,14 +34,6 @@ Get started with network security perimeter by creating a network security perim
3434
Install-AzModule -Name Az.Network -AllowPrerelease -Force
3535
Install-AzModule -Path https://azposhpreview.blob.core.windows.net/public/Az.Network.5.6.1-preview.nupkg
3636
```
37-
38-
- Register the Microsoft.Network resource provider:
39-
40-
```azurepowershell-interactive
41-
# Register the Microsoft.Network resource provider
42-
Register-AzResourceProvider -ProviderNamespace Microsoft.Network
43-
```
44-
4537
* If you choose to use Azure PowerShell locally:
4638
* [Install the latest version of the Az PowerShell module](/powershell/azure/install-azure-powershell).
4739
* Connect to your Azure account using the
@@ -66,7 +58,6 @@ Set-AzContext -Subscription <subscriptionId>
6658
6759
# Register the Microsoft.Network resource provider
6860
Register-AzResourceProvider -ProviderNamespace Microsoft.Network
69-
7061
```
7162

7263
## Create a resource group and key vault

articles/private-link/network-security-perimeter-concepts.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,12 @@ Azure Network Security Perimeter allows organizations to define a logical networ
1717
For access patterns involving traffic from virtual networks to PaaS resources, see [What is Azure Private Link?](private-link-overview.md).
1818

1919
Features of Network Security Perimeter include:
20-
- Service to service communication to prevent data exfiltration.
20+
21+
- Service to service communication within perimeter members, preventing data exfiltration to non-authorized destinations.
2122
- Public network access control for PaaS resources.
2223
- Access logs for audit and compliance.
23-
- Manage access rules for all the PaaS resources within the perimeter.
24+
- Manage external public access with explicit rules for PaaS resources associated with the perimeter.
25+
2426

2527

2628
:::image type="content" source="media/network-security-perimeter-concepts/network-security-perimeter-overview.png" alt-text="Diagram of securing a service with network security perimeter." lightbox="media/network-security-perimeter-concepts/network-security-perimeter-overview-large.png":::

articles/private-link/network-security-perimeter-transition.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,11 @@ ms.date: 11/04/2024
1313

1414
In this article, you learn about the different access modes and how to transition to a [network security perimeter](./network-security-perimeter-concepts.md) in Azure. Access modes control the resource's access and logging behavior.
1515

16-
## Configuration points for access modes
17-
18-
### Access mode configuration point on resource associations
16+
## Access mode configuration point on resource associations
1917

2018
The **access mode** configuration point is part of a resource association on the perimeter and therefore can be set by the perimeter's administrator.
2119

22-
The property `accessMode` can be set in a resource association to control the resource's connectivity and logging behavior.
20+
The property `accessMode` can be set in a resource association to control the resource's public network access and logging behavior.
2321

2422
The possible values of `accessMode` are currently Enforced and Learning.
2523

@@ -85,23 +83,25 @@ When associated with a perimeter and configured in *Learning* mode with `p
8583
8684
In special cases when `publicNetworkAccess` is set to `SecuredByPerimeter` but the resource is still not associated with a perimeter, no network security perimeter access rules can allow access. Therefore the resource becomes locked down for public access. The following table summarizes the behavior with this configuration:
8785

88-
| **publicNetworkAccess** | **Disabled (existing value)** | **Enabled (existing value)** | **SecuredByPerimeter (new value)** |
89-
|-----------------|---------------|----------------|------------|
90-
| **Perimeter access** | Denied | Denied | Denied |
91-
| **Public inbound** | Denied | Allowed only by resource rules | Denied |
92-
| **Public outbound** | Allowed only by resource rules | Allowed only by resource rules | Denied |
93-
| **Trusted access** | Allowed | Allowed | Denied |
94-
| **Private access** | Allowed | Allowed | Allowed |
86+
| **publicNetworkAccess** | **SecuredByPerimeter (new value)** |
87+
|-----------------|-----------------|
88+
| **Perimeter access** | Denied |
89+
| **Public inbound** | Denied |
90+
| **Public outbound** | Denied |
91+
| **Trusted access** | Denied |
92+
| **Trusted access** | Denied |
93+
| **Private access** | Allowed |
9594

9695
The **locked down for public access** mode exists by-design and helps prevent PaaS resources not yet associated with a perimeter from being temporarily exposed to public networks or to other PaaS resources. Administrators can apply Azure Policy to ensure publicNetworkAccess is set to SecuredByPerimeter from the moment a resource is created.
9796

9897
The behavior of public network access on PaaS resources according to the association's accessMode value and the resource's `publicNetworkAccess` value can be summarized as follows:
9998

99+
| **Association access mode** | | | |
100+
|-----------------|-------------------|-----------------|-----------------|
100101
| **Public network access** | **Not associated** | **Learning mode** | **Enforced mode** |
101-
|-------------|-----------|-------------|-----------|
102-
| **Enabled** | Inbound: Resource rules </br> Outbound: Allowed | Inbound: Network security perimeter + Resource rules </br> Outbound: Network security perimeter rules + Allowed | Inbound: Network security perimeter rules </br> Outbound: Network security perimeter rules |
103-
| **Disabled** | Inbound: Denied </br> Outbound: Allowed | Inbound: Network security perimeter rules </br> Outbound: Network security perimeter rules + Allowed | Inbound: Network security perimeter rules </br> Outbound: Network security perimeter rules |
104-
| **SecuredByPerimeter** | Inbound: Denied </br> Outbound: Denied | Inbound: Network security perimeter rules </br> Outbound: Network security perimeter rules | Inbound: Network security perimeter rules </br> Outbound: Network security perimeter rules |
102+
| **Enabled** | Inbound: Resource rules</br>Outbound: Allowed | Inbound: Network security perimeter + Resource rules</br> Outbound: Network security perimeter rules + Allowed | Inbound: Network security perimeter rules</br>Outbound: Network security perimeter rules |
103+
| **Disabled** | Inbound: Denied</br>Outbound: Allowed | Inbound: Network security perimeter rules</br>Outbound: Network security perimeter rules + Allowed | Inbound: Network security perimeter rules</br>Outbound: Network security perimeter rules |
104+
| **SecuredByPerimeter** | Inbound: Denied</br>Outbound: Denied | Inbound: Network security perimeter rules</br>Outbound: Network security perimeter rules | Inbound: Network security perimeter rules</br>Outbound: Network security perimeter rules |
105105

106106
## Next steps
107107

75.3 KB
Loading

includes/network-security-perimeter-add-preview.md

Lines changed: 25 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,34 @@
55
author: mbender
66
ms.service: azure-private-link
77
ms.topic: include
8-
ms.date: 04/19/2024
8+
ms.date: 11/04/2024
99
ms.author: mbender> -ms
1010
ms.custom: include file
1111
---
1212

1313
- Registration for the Azure Network Security Perimeter public preview is required. To register, add the `AllowNSPInPublicPreview` feature flag to your subscription.
1414
:::image type="content" source="media/network-security-perimeter-add-preview/network-security-perimeter-add-preview-feature.png" alt-text="Screenshot of addition of network security perimeter feature flag to Azure subscription.":::
15-
16-
For more information on adding feature flags, see [Set up preview features in Azure subscription](../articles/azure-resource-manager/management/preview-features.md).
15+
16+
For more information on adding feature flags, see [Set up preview features in Azure subscription](../articles/azure-resource-manager/management/preview-features.md).
17+
18+
- After the feature flag is added, you need to re-register the `Microsoft.Network` resource provider in your subscription.
19+
- To re-register the `Microsoft.Network` resource provider in the Azure portal, select your subscription, and then select **Resource providers**. Search for `Microsoft.Network` and select **Re-register**.
20+
21+
:::image type="content" source="media/network-security-perimeter-add-preview/re-register-microsoft-network-provider.png" alt-text="Screenshot of re-registration of Microsoft.Network resource provider in subscription.":::
22+
23+
- To re-register the `Microsoft.Network` resource provider, use the following Azure PowerShell command:
24+
25+
```azurepowershell-interactive
26+
# Register the Microsoft.Network resource provider
27+
Register-AzResourceProvider -ProviderNamespace Microsoft.Network
28+
```
29+
30+
- To re-register the `Microsoft.Network` resource provider, use the following Azure CLI command:
31+
32+
```azurecli-interactive
33+
# Register the Microsoft.Network resource provider
34+
az provider register --namespace Microsoft.Network
35+
```
36+
37+
38+
For more information on re-registering resource providers, see [Azure resource providers and types](/azure/azure-resource-manager/management/resource-providers-and-types).

0 commit comments

Comments
 (0)