Skip to content

Commit feaa366

Browse files
authored
pencil edit
1 parent ae6da44 commit feaa366

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ When a storage account is associated with a network security perimeter, all stan
3838

3939
| Feature | Support status| Recommendations |
4040
|----------|----------|----------|
41-
| [Object replication](../blobs/object-replication-overview.md) for Azure Blob Storage | Not Supported. Object Replication between storage accounts fail if either the source or destination account is associated with a network security perimeter | Don't configure network security perimeter on storage accounts that need object replication. Similarly, don't enable object replication on accounts associated with network security perimeter until support is available. If object replication is already enabled, you cannot associate a network security perimeter. Similarly, if a network security perimeter is already associated, you cannot enable object replication. This restriction prevents you from configuring an unsupported scenario. |
41+
| [Object replication](../blobs/object-replication-overview.md) for Azure Blob Storage | Not Supported. Object Replication between storage accounts fails if either the source or destination account is associated with a network security perimeter | Don't configure network security perimeter on storage accounts that need object replication. Similarly, don't enable object replication on accounts associated with network security perimeter until support is available. If object replication is already enabled, you cannot associate a network security perimeter. Similarly, if a network security perimeter is already associated, you cannot enable object replication. This restriction prevents you from configuring an unsupported scenario. |
4242
| Network file system (NFS) access over [Azure Blobs](../blobs/network-file-system-protocol-support.md) and [Azure Files](../files/files-nfs-protocol.md), Server message block (SMB) access over Azure Files and [SSH File transfer protocol (SFTP)](../blobs/secure-file-transfer-protocol-support.md) over Azure Blobs | All protocols other than HTTPS based access are blocked when storage account is associated with a network security perimeter | If you need to use any of these protocols to access your storage account, don't associate the account with a network security perimeter |
4343
| Azure Backup | Not supported. Azure Backup as a service is not onboarded to network security perimeter yet. | We recommend not associating an account with network security perimeter if you have backups enabled or if you plan to use Azure Backup. Once Azure Backup onboards to network security perimeter, you can start using both these features together |
4444
| Unmanaged disks | [Unmanaged disks](/azure/virtual-machines/unmanaged-disks-deprecation) don't honor network security perimeter rules. | Avoid using unmanaged disks on storage accounts protected by network security perimeter |

0 commit comments

Comments
 (0)