Skip to content

Commit 8935a5f

Browse files
committed
fixes to nsp
1 parent eb59480 commit 8935a5f

File tree

3 files changed

+12
-16
lines changed

3 files changed

+12
-16
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: references_regions
1212

1313
# What is Network Security Perimeter?
1414

15-
Azure Network Security Perimeter allows organizations to define a logical network isolation boundary for PaaS resources (for example, Azure Storage and SQL Database) that are deployed outside your organization’s virtual networks. It restricts public network access to PaaS resources outside of the perimeter, access can be exempted by using explicit access rules for public inbound and outbound.
15+
Azure Network Security Perimeter allows organizations to define a logical network isolation boundary for PaaS resources (for example, Azure Storage and SQL Database) that are deployed outside your organization’s virtual networks. It restricts public network access to PaaS resources outside of the perimeter; access can be exempted by using explicit access rules for public inbound and outbound.
1616

1717
For access patterns involving traffic from virtual networks to PaaS resources, see [What is Azure Private Link?](private-link-overview.md).
1818

articles/storage/common/storage-network-security.md

Lines changed: 11 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,12 @@ After you apply network rules, they're enforced for all requests. SAS tokens tha
8888

8989
### Network Security Perimeter (preview)
9090

91-
[Network Security Perimeter](../../private-link/network-security-perimeter-concepts.md) (preview) allows organizations to define a logical network isolation boundary for PaaS resources (for example, Azure Blob Storage and SQL Database) that are deployed outside their virtual networks. The feature restricts public network access to PaaS resources outside the perimeter. However, you can exempt access by using explicit access rules for public inbound and outbound traffic. By design, access to a storage account from within a Network Security Perimeter takes the highest precedence over other network access restrictions. Currently, Network Security Perimeter is in public preview for Azure Blobs, Azure Files (SMB only), Azure Tables, and Azure Queues.
91+
[Network Security Perimeter](../../private-link/network-security-perimeter-concepts.md) (preview) allows organizations to define a logical network isolation boundary for PaaS resources (for example, Azure Blob Storage and SQL Database) that are deployed outside their virtual networks. The feature restricts public network access to PaaS resources outside the perimeter. However, you can exempt access by using explicit access rules for public inbound and outbound traffic. By design, access to a storage account from within a Network Security Perimeter takes the highest precedence over other network access restrictions.
92+
93+
Currently, Network Security Perimeter is in public preview for Azure Blobs, Azure Files (REST), Azure Tables, and Azure Queues. See [Transition to a Network Security Perimeter](../../private-link/network-security-perimeter-transition.md).
94+
95+
> [!IMPORTANT]
96+
> Private endpoint traffic is considered highly secure and therefore isn't subject to Network Security Perimeter rules. All other traffic, including trusted services, will be subject to Network Security Perimeter rules if the storage account is associated with a perimeter.
9297
9398
#### Limitations
9499

@@ -97,27 +102,18 @@ This preview doesn't support the following services, operations, and protocols o
97102
- [Object replication](../blobs/object-replication-overview.md) for Azure Blob Storage
98103
- [Lifecycle management](../blobs/lifecycle-management-overview.md) for Azure Blob Storage
99104
- [SSH File transfer protocol (SFTP)](../blobs/secure-file-transfer-protocol-support.md) over Azure Blob Storage
100-
- Network file system (NFS) protocol over [Azure Blob Storage](../blobs/network-file-system-protocol-support.md) and [Azure Files](../files/files-nfs-protocol.md).
101-
- [Azure Storage Blob Inventory](../blobs/blob-inventory.md)
105+
- Network file system (NFS) protocol with [Azure Blob Storage](../blobs/network-file-system-protocol-support.md) and [Azure Files](../files/files-nfs-protocol.md).
106+
- Server message block (SMB) protocol with Azure Files can only be achieved thru IP allowlisting at this time.
107+
- [Azure Blob Inventory](../blobs/blob-inventory.md)
102108

103109
We recommend you don't enable Network Security Perimeter if you need to use any of these services, operations, or protocols. This is to prevent any potential data loss or data exfiltration risk.
104110

105111
> [!WARNING]
106-
> If you set **Public network access** to **Disabled** after previously setting it to **Enabled from selected virtual networks and IP addresses**, any [resource instances](#grant-access-from-azure-resource-instances) and [exceptions](#manage-exceptions) that you previously configured, including [Allow Azure services on the trusted services list to access this storage account](#grant-access-to-trusted-azure-services), will remain in effect. As a result, those resources and services might still have access to the storage account.
112+
> For storage accounts that are associated with a Network Security Perimeter, in order for customer managed keys (CMK) scenarios to work, ensure that the Azure Key Vault is accessible from within the perimeter to which the storage account has been associated.
107113
108114
#### Associate a Network Security Perimeter with a storage account
109115

110-
To associate a Network Security Perimeter with a storage account, follow these instructions.
111-
112-
1. Sign in to the Azure portal and navigate to the storage account.
113-
1. In the service menu, under **Security + networking**, select **Networking**.
114-
1. Under **Network Security Perimeter**, select **Associate**.
115-
116-
:::image type="content" source="media/storage-network-security/associate-network-security-perimeter.png" alt-text="Screenshot showing how to associate a Network Security Perimeter with a storage account in the Azure portal." lightbox="media/storage-network-security/associate-network-security-perimeter.png":::
117-
118-
1. Search for and select a Network Security Perimeter, select a profile, and then select **Associate**.
119-
120-
The Network Security Perimeter is now associated with your storage account.
116+
To associate a Network Security Perimeter with a storage account, follow these [common instructions](../../private-link/network-security-perimeter-concepts.md) for all PaaS resources.
121117

122118
## Restrictions and considerations
123119

0 commit comments

Comments
 (0)