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: articles/private-link/network-security-perimeter-concepts.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,10 +17,12 @@ Azure Network Security Perimeter allows organizations to define a logical networ
17
17
For access patterns involving traffic from virtual networks to PaaS resources, see [What is Azure Private Link?](private-link-overview.md).
18
18
19
19
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.
21
22
- Public network access control for PaaS resources.
22
23
- 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
+
24
26
25
27
26
28
:::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":::
Copy file name to clipboardExpand all lines: articles/private-link/network-security-perimeter-transition.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,11 @@ ms.date: 11/04/2024
13
13
14
14
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.
15
15
16
-
## Configuration points for access modes
17
-
18
-
### Access mode configuration point on resource associations
16
+
## Access mode configuration point on resource associations
19
17
20
18
The **access mode** configuration point is part of a resource association on the perimeter and therefore can be set by the perimeter's administrator.
21
19
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.
23
21
24
22
The possible values of `accessMode` are currently Enforced and Learning.
25
23
@@ -85,23 +83,25 @@ When associated with a perimeter and configured in *Learning* mode with `p
85
83
86
84
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:
87
85
88
-
|**publicNetworkAccess**|**Disabled (existing value)**|**Enabled (existing value)**|**SecuredByPerimeter (new value)**|
|**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 |
95
94
96
95
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.
97
96
98
97
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:
Copy file name to clipboardExpand all lines: includes/network-security-perimeter-add-preview.md
+25-3Lines changed: 25 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,34 @@
5
5
author: mbender
6
6
ms.service: azure-private-link
7
7
ms.topic: include
8
-
ms.date: 04/19/2024
8
+
ms.date: 11/04/2024
9
9
ms.author: mbender> -ms
10
10
ms.custom: include file
11
11
---
12
12
13
13
- Registration for the Azure Network Security Perimeter public preview is required. To register, add the `AllowNSPInPublicPreview` feature flag to your subscription.
14
14
:::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
- 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