Merge pull request #312699 from sbreingold-ms/wi-515918-nsp-not-supported-sentinel

wi-515918-nsp-not-supported-sentinel

Author: prmerger-automator[bot]

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

@@ -6,7 +6,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: azure-private-link
 ms.topic: overview
-ms.date: 08/01/2025
+ms.date: 03/22/2026
 ms.custom:
   - references_regions, ignite-2024
   - ai-gen-docs-bap
@@ -141,8 +141,11 @@ Network security perimeter is currently available in all Azure public cloud regi
 > [!NOTE]
 > For PaaS resource logs, use **Log Analytics Workspace, Storage or Event Hub** as the log destination associated to the same perimeter as the PaaS resource.
 
-> [!NOTE]
-> Azure Backup is not supported for Storage Accounts enabled with network security perimeter. We recommend not associating a storage account with network security perimeter if you have backups enabled or if you plan to use Azure Backup.
+### Microsoft Sentinel limitations
+
+The following are known limitations:
+* Network security perimeters aren't supported for Log Analytics workspaces enabled for Microsoft Sentinel. If a network security perimeter is enabled on the workspace, analytic rules are automatically disabled. For more information, see [Prerequisites for deploying Microsoft Sentinel](/azure/sentinel/prerequisites).
+* Azure Backup is not supported for Storage Accounts enabled with network security perimeter. We recommend not associating a storage account with network security perimeter if you have backups enabled or if you plan to use Azure Backup.
 
 [!INCLUDE [network-security-perimeter-limits](../../includes/network-security-perimeter-limits.md)]
 

articles/sentinel/prerequisites.md

@@ -3,9 +3,8 @@ title: Prerequisites for deploying Microsoft Sentinel
 description: Learn about prerequisites to deploy Microsoft Sentinel.
 author: guywi-ms
 ms.author: guywild
-ms.topic: install-set-up-deploy
-ms.date: 05/27/2025
-
+ms.topic: conceptual
+ms.date: 03/06/2026
 
 #Customer intent: As a security administrator, I want to understand the prerequisites for deploying Microsoft Sentinel so that I can ensure my environment is properly configured and compliant.
 
@@ -31,6 +30,8 @@ A [Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace) is
 
 The Log Analytics workspace must not have a resource lock applied, and the workspace pricing tier must be pay-as-you-go or a commitment tier. Log Analytics legacy pricing tiers and resource locks aren't supported when enabling Microsoft Sentinel. For more information about pricing tiers, see [Simplified pricing tiers for Microsoft Sentinel](enroll-simplified-pricing-tier.md#prerequisites).
 
+[Network security perimeters](../private-link/network-security-perimeter-concepts.md) aren't supported for Log Analytics workspaces enabled for Microsoft Sentinel. If a network security perimeter is enabled on the workspace, analytic rules are automatically disabled.
+
 ### Dedicated resource group (recommended)
 
 To reduce complexity, we recommend a dedicated [resource group](../azure-resource-manager/management/manage-resource-groups-portal.md) for your Log Analytics workspace enabled for Microsoft Sentinel. This resource group should only contain the resources that Microsoft Sentinel uses, including the Log Analytics workspace, any playbooks, workbooks, and so on.