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-transition.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,23 +85,23 @@ In special cases when `publicNetworkAccess` is set to `SecuredByPerimeter`
85
85
86
86
|**publicNetworkAccess**|**SecuredByPerimeter (new value)**|
87
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 |
88
+
| Perimeter access | Denied |
89
+
| Public inbound | Denied |
90
+
| Public outbound | Denied |
91
+
| Trusted access | Denied |
92
+
| Trusted access | Denied |
93
+
| Private access | Allowed |
94
94
95
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.
96
96
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:
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:
0 commit comments