Skip to content

Commit 98981f5

Browse files
committed
wi-515918-nsp-not-supported-sentinel
1 parent 90c8424 commit 98981f5

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

articles/sentinel/prerequisites.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about prerequisites to deploy Microsoft Sentinel.
44
author: batamig
55
ms.author: bagol
66
ms.topic: conceptual
7-
ms.date: 05/27/2025
7+
ms.date: 03/06/2026
88

99

1010
#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 +31,8 @@ A [Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace) is
3131

3232
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).
3333

34+
[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.
35+
3436
### Dedicated resource group (recommended)
3537

3638
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.

0 commit comments

Comments
 (0)