Merge pull request #284293 from bwren/docs-editor/kubernetes-monitoring-private-1723385885

Update kubernetes-monitoring-private-link.md

Author: prmerger-automator[bot]

articles/azure-monitor/containers/kubernetes-monitoring-private-link.md

@@ -32,7 +32,7 @@ If your AKS cluster isn't in the same region as your Azure Monitor workspace, th
 :::image type="content" source="media/kubernetes-monitoring-private-link/azure-monitor-workspace-data-collection-rule.png" alt-text="A screenshot show the data collection rules page for an Azure Monitor workspace." lightbox="media/kubernetes-monitoring-private-link/azure-monitor-workspace-data-collection-rule.png" :::
 
 
-## Ingestion from a private AKS cluster
+### Ingestion from a private AKS cluster
 By default, a private AKS cluster can send data to Managed Prometheus and your Azure Monitor workspace over the public network using a public Data Collection Endpoint.
 
 If you choose to use an Azure Firewall to limit the egress from your cluster, you can implement one of the following:
@@ -42,7 +42,7 @@ If you choose to use an Azure Firewall to limit the egress from your cluster, yo
   - `*.ingest.monitor.azure.com`
 - Enable the Azure Firewall to access the Azure Monitor Private Link scope and DCE that's used for data ingestion.
 
-## Private link ingestion for remote write
+### Private link ingestion for remote write
 Use the following steps to set up remote write for a Kubernetes cluster over a private link virtual network and an Azure Monitor Private Link scope.
 
 1. Create your Azure virtual network.
@@ -63,10 +63,7 @@ Data for Container insights, is stored in a [Log Analytics workspace](../logs/lo
 
 ### Cluster using managed identity authentication
 
-
-### Existing AKS Cluster 
-
-**Use default Log Analytics workspace**
+**Existing AKS cluster with default Log Analytics workspace**
 
 ```azurecli
 az aks enable-addons --addon monitoring --name <cluster-name> --resource-group <cluster-resource-group-name> --ampls-resource-id "<azure-monitor-private-link-scope-resource-id>"
@@ -78,7 +75,7 @@ Example:
 az aks enable-addons --addon monitoring --name "my-cluster" --resource-group "my-resource-group" --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace" --ampls-resource-id "/subscriptions/my-subscription /resourceGroups/my-resource-group/providers/microsoft.insights/privatelinkscopes/my-ampls-resource"
 ```
 
-**Use existing Log Analytics workspace**
+**Existing AKS cluster with existing Log Analytics workspace**
 
 ```azurecli
 az aks enable-addons --addon monitoring --name <cluster-name> --resource-group <cluster-resource-group-name> --workspace-resource-id <workspace-resource-id> --ampls-resource-id "<azure-monitor-private-link-scope-resource-id>"
@@ -90,7 +87,7 @@ Example:
 az aks enable-addons --addon monitoring --name "my-cluster" --resource-group "my-resource-group" --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace" --ampls-resource-id "/subscriptions/my-subscription /resourceGroups/ my-resource-group/providers/microsoft.insights/privatelinkscopes/my-ampls-resource"
 ```
 
-### New AKS cluster
+**New AKS cluster**
 
 ```azurecli
 az aks create --resource-group rgName --name clusterName --enable-addons monitoring --workspace-resource-id "workspaceResourceId" --ampls-resource-id "azure-monitor-private-link-scope-resource-id"
@@ -103,7 +100,7 @@ az aks create --resource-group "my-resource-group"  --name "my-cluster"  --enabl
 ```
 
 
-## Cluster using legacy authentication
+### Cluster using legacy authentication
 Use the following procedures to enable network isolation by connecting your cluster to the Log Analytics workspace using [Azure Private Link](../logs/private-link-security.md) if your cluster is not using managed identity authentication. This requires a [private AKS cluster](/azure/aks/private-clusters).
 
 1. Create a private AKS cluster following the guidance in [Create a private Azure Kubernetes Service cluster](/azure/aks/private-clusters).