Merge pull request #177580 from noakup/master

Adding links and details on custom logs over Private Links

Author: PRMerger-2

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

@@ -299,5 +299,5 @@ This zone configures connectivity to the global agents' solution packs storage a
 
 ## Next steps
 
-- Learn about [private storage](private-storage.md)
+- Learn about [private storage](private-storage.md) for Custom Logs and Customer managed keys (CMK)
 - Learn about [Private Link for Automation](../../automation/how-to/private-link-security.md)

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

@@ -147,9 +147,9 @@ If your Private Link setup was created before April 19, 2021, it won't reach the
     |Azure China 21Vianet      | mceast2oicore.blob.core.chinacloudapi.cn| 443 | Outbound
 
 ### Collecting custom logs and IIS log over Private Link
-Storage accounts are used in the ingestion process of custom logs. By default, service-managed storage accounts are used. However to ingest custom logs on private links, you must use your own storage accounts and associate them with Log Analytics workspace(s). See more details on how to set up such accounts using the [command line](/cli/azure/monitor/log-analytics/workspace/linked-storage).
+Storage accounts are used in the ingestion process of custom logs. By default, service-managed storage accounts are used. However to ingest custom logs on private links, you must use your own storage accounts and associate them with Log Analytics workspace(s).
 
-For more information on connecting your own storage account, see [Customer-owned storage accounts for log ingestion](private-storage.md)
+For more information on connecting your own storage account, see [Customer-owned storage accounts for log ingestion](private-storage.md) and specifically [Using Private Links](private-storage.md#using-private-links) and [Link storage accounts to your Log Analytics workspace](private-storage.md#link-storage-accounts-to-your-log-analytics-workspace).
 
 ### Automation
 If you use Log Analytics solutions that require an Automation account (such as Update Management, Change Tracking, or Inventory) you should also create a Private Link for your Automation account. For more information, see [Use Azure Private Link to securely connect networks to Azure Automation](../../automation/how-to/private-link-security.md).
@@ -202,5 +202,5 @@ The [`externaldata` operator](/azure/data-explorer/kusto/query/externaldata-oper
 
 ## Next steps
 - Learn how to [configure your Private Link](private-link-configure.md)
-- Learn about [private storage](private-storage.md)
+- Learn about [private storage](private-storage.md) for Custom Logs and Customer managed keys (CMK)
 - Learn about [Private Link for Automation](../../automation/how-to/private-link-security.md)

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

@@ -78,5 +78,5 @@ Therefore, Private Links created starting September 2021 have new mandatory AMPL
 ## Next steps
 - [Design your Private Link setup](private-link-design.md)
 - Learn how to [configure your Private Link](private-link-configure.md)
-
+- Learn about [private storage](private-storage.md) for Custom Logs and Customer managed keys (CMK)
 <h3><a id="connect-to-a-private-endpoint"></a></h3>