Skip to content

Commit 3532430

Browse files
authored
Update network-security-perimeter-delete-resources.md
1 parent 4e1c8d4 commit 3532430

File tree

1 file changed

+1
-13
lines changed

1 file changed

+1
-13
lines changed
Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,3 @@
1-
---
2-
title: include file
3-
description: include file
4-
services: private-link
5-
author: mbender
6-
ms.service: azure-private-link
7-
ms.topic: include
8-
ms.date: 11/05/2024
9-
ms.author: mbender> -ms
10-
ms.custom: include file
11-
---
12-
131
---
142
title: include file
153
description: include file
@@ -23,4 +11,4 @@ ms.custom: include file
2311
---
2412

2513
> [!NOTE]
26-
> Removing your resource association from the network security perimeter results in access control falling back to the existing resource firewall configuration. This may result in access being allowed/denied as per the resource firewall configuration. If PublicNetworkAccess is set to SecuredByPerimeter and the association has been deleted, the resource will enter a locked down state. For more information, see [Transition to a network security perimeter in Azure](../articles/private-link/network-security-perimeter-transition.md#transition-to-a-network-security-perimeter-in-azure).
14+
> Removing your resource association from the network security perimeter results in access control falling back to the existing resource firewall configuration. This may result in access being allowed/denied as per the resource firewall configuration. If PublicNetworkAccess is set to SecuredByPerimeter and the association has been deleted, the resource will enter a locked down state. For more information, see [Transition to a network security perimeter in Azure](../articles/private-link/network-security-perimeter-transition.md#transition-to-a-network-security-perimeter-in-azure).

0 commit comments

Comments
 (0)