Merge pull request #304981 from tjvishnu/patch-21

Update storage network security perimeter documentation

Author: prmerger-automator[bot]

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

@@ -42,6 +42,7 @@ When a storage account is associated with a network security perimeter, all stan
 | 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 |
 | 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 |
 | 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 |
+| [Static Website](../blobs/storage-blob-static-website.md)| Not supported | Static website, being open in nature cannot be used with network security perimeter. If static website is already enabled, you cannot associate a network security perimeter. Similarly, if a network security perimeter is already associated, you cannot enable static website. This restriction prevents you from configuring an unsupported scenario. |
 
 
 > [!WARNING]