Merge pull request #297840 from ChaithanyaRai/patch-95

Update network-security-perimeter-concepts.md

Author: prmerger-automator[bot]

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

@@ -113,12 +113,12 @@ Network security perimeter supports the following access rule types:
 
 ## Limitations of a network security perimeter
 
-### Regional limitations
+### Logging limitations
 
 Network security perimeter is currently available in all Azure public cloud regions. However, while enabling access logs for network security perimeter, the Log Analytics workspace to be associated with the network security perimeter needs to be located in one of the Azure Monitor supported regions.
 
 > [!NOTE]
-> For PaaS resource logs, use **Storage and Event Hub** as the log destination for any region associated to the same perimeter.
+> 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.
 
 [!INCLUDE [network-security-perimeter-limits](../../includes/network-security-perimeter-limits.md)]
 

articles/private-link/network-security-perimeter-diagnostic-logs.md

@@ -46,7 +46,7 @@ You can enable diagnostic logging for a network security perimeter by using the
 :::image type="content" source="media/network-security-perimeter-diagnostic-logs/network-security-perimeter-diagnostic-settings.png" alt-text="Screenshot of diagnostic settings options for a network security perimeter.":::
 
 > [!NOTE]
-> When using Azure Monitor with a network security perimeter, the Log Analytics workspace to be associated with the network security perimeter needs to be located in one of the Azure Monitor supported regions. For more information on available regions, see [Regional limits for Network Security Perimeter](./network-security-perimeter-concepts.md#regional-limitations).
+> When using Azure Monitor with a network security perimeter, the Log Analytics workspace to be associated with the network security perimeter needs to be located in one of the Azure Monitor supported regions.
 
 ## Next steps