Merge pull request #221453 from guywi-ms/patch-32

Update private-link-design.md

Author: prmerger-automator[bot]

articles/azure-monitor/logs/private-link-design.md

@@ -4,7 +4,7 @@ description: Design your Private Link setup
 author: noakup
 ms.author: noakuper
 ms.topic: conceptual
-ms.date: 1/5/2022
+ms.date: 12/14/2022
 ---
 
 # Design your Private Link setup
@@ -54,9 +54,9 @@ To test Private Links locally without affecting other clients on your network, m
 That approach isn't recommended for production environments.
 
 ## Control how Private Links apply to your networks
-Private Link access modes (introduced in September 2021) allow you to control how Private Links affect your network traffic. These settings can apply to your AMPLS object (to affect all connected networks) or to specific networks connected to it.
+Private Link access modes allow you to control how Private Links affect your network traffic. These settings can apply to your AMPLS object (to affect all connected networks) or to specific networks connected to it.
 
-Choosing the proper access mode has detrimental effects on your network traffic. Each of these modes can be set for ingestion and queries, separately:
+Choosing the proper access mode is critical to ensuring continuous, uninterrupted network traffic. Each of these modes can be set for ingestion and queries, separately:
 
 * Private Only - allows the VNet to reach only Private Link resources (resources in the AMPLS). That's the most secure mode of work, preventing data exfiltration. To achieve that, traffic to Azure Monitor resources out of the AMPLS is blocked.
 ![Diagram of AMPLS Private Only access mode](./media/private-link-security/ampls-private-only-access-mode.png)