Merge pull request #219853 from v-jbasden/jbasden-update-private-link-screenshots

Update screenshots for Connect to a private endpoint

Author: BCS2022

articles/azure-monitor/logs/media/private-link-security/ampls-select-private-endpoint-connect-3.png

@@ -51,38 +51,38 @@ Now that you have resources connected to your AMPLS, create a private endpoint t
 
 1. In your scope resource, select **Private Endpoint connections** in the left-hand resource menu. Select **Private Endpoint** to start the endpoint create process. You can also approve connections that were started in the Private Link center here by selecting them and selecting **Approve**.
 
-    ![Screenshot of Private Endpoint Connections UX](./media/private-link-security/ampls-select-private-endpoint-connect-3.png)
+    :::image type="content" source="./media/private-link-security/ampls-select-private-endpoint-connect-3.png" alt-text="Screenshot of Private Endpoint Connections UX." lightbox="./media/private-link-security/ampls-select-private-endpoint-connect-3.png":::
 
 2. Pick the subscription, resource group, and name of the endpoint, and the region it should live in. The region needs to be the same region as the VNet you connect it to.
 
 3. Select **Next: Resource**. 
 
-4. In the Resource screen,
+4. In the Resource tab:
+   1. Pick the **Subscription** that contains your Azure Monitor Private Scope resource. 
+   1. For **resource type**, choose **Microsoft.insights/privateLinkScopes**. 
+   1. From the **resource** drop-down, choose your Private Link scope you created earlier. 
+   1. Select **Next: Virtual Network >**.
 
-   a. Pick the **Subscription** that contains your Azure Monitor Private Scope resource. 
+      :::image type="content" source="./media/private-link-security/ampls-select-private-endpoint-create-4.png" alt-text="Screenshot of the Create a private endpoint page in the Azure portal with the Resource tab selected." lightbox="./media/private-link-security/ampls-select-private-endpoint-create-4.png":::
 
-   b. For **resource type**, choose **Microsoft.insights/privateLinkScopes**. 
+5. On the Virtual Network tab:
+   1. Choose the **virtual network** and **subnet** that you want to connect to your Azure Monitor resources.
+   1. Select **Next: DNS >**.
+   
+      :::image type="content" source="./media/private-link-security/ampls-select-private-endpoint-create-5.png" alt-text="Screenshot of the Create a private endpoint page in the Azure portal with the Virtual Network tab selected." lightbox="./media/private-link-security/ampls-select-private-endpoint-create-5.png":::
 
-   c. From the **resource** drop-down, choose your Private Link scope you created earlier. 
-
-   d. Select **Next: Configuration >**.
-      ![Screenshot of select Create Private Endpoint](./media/private-link-security/ampls-select-private-endpoint-create-4.png)
-
-5. On the configuration pane,
-
-   a.    Choose the **virtual network** and **subnet** that you want to connect to your Azure Monitor resources. 
- 
-   b.    Choose **Yes** for **Integrate with private DNS zone**, and let it automatically create a new Private DNS Zone. The actual DNS zones may be different from what is shown in the screenshot below. 
-   > [!NOTE]
-   > If you choose **No** and prefer to manage DNS records manually, first complete setting up your Private Link - including this Private Endpoint and the AMPLS configuration. Then, configure your DNS according to the instructions in [Azure Private Endpoint DNS configuration](../../private-link/private-endpoint-dns.md). Make sure not to create empty records as preparation for your Private Link setup. The DNS records you create can override existing settings and impact your connectivity with Azure Monitor.
 
-   c.    Select **Review + create**.
- 
-   d.    Let validation pass. 
- 
-   e.    Select **Create**. 
+6. On the DNS tab:
+   1. Choose **Yes** for **Integrate with private DNS zone**, and let it automatically create a new Private DNS Zone. The actual DNS zones may be different from what is shown in the screenshot below. 
+       > [!NOTE]
+       > If you choose **No** and prefer to manage DNS records manually, first complete setting up your Private Link - including this Private Endpoint and the AMPLS configuration. Then, configure your DNS according to the instructions in [Azure Private Endpoint DNS configuration](../../private-link/private-endpoint-dns.md). Make sure not to create empty records as preparation for your Private Link setup. The DNS records you create can override existing settings and impact your connectivity with Azure Monitor.
+    1. Select **Review + create**.
+
+       :::image type="content" source="./media/private-link-security/ampls-select-private-endpoint-create-6.png" alt-text="Screenshot of the Create a private endpoint page in the Azure portal with the DNS tab selected." lightbox="./media/private-link-security/ampls-select-private-endpoint-create-6.png":::
 
-    ![Screenshot of select Private Endpoint details.](./media/private-link-security/ampls-select-private-endpoint-create-5.png)
+7. On the Review + create tab:
+   1. Let validation pass.
+   1. Select **Create**. 
 
 You've now created a new private endpoint that is connected to this AMPLS.
 
@@ -266,7 +266,7 @@ This zone covers the global endpoints used by Azure Monitor, meaning endpoints t
 * **live** - Application Insights live metrics endpoint
 * **profiler** - Application Insights profiler endpoint
 * **snapshot** - Application Insights snapshots endpoint
-* **diagservices-query** - Application Insights Profiler and Snapshot Debugger (used when accessing profiler/debugger results in the Azure Portal)
+* **diagservices-query** - Application Insights Profiler and Snapshot Debugger (used when accessing profiler/debugger results in the Azure portal)
 
 This zone also covers the resource specific endpoints for [Data Collection Endpoints](../essentials/data-collection-endpoint-overview.md):
 * `<unique-dce-identifier>.<regionname>.handler.control` - Private configuration endpoint, part of a Data Collection Endpoint (DCE) resource