Merge pull request #291695 from cherylmc/native3

freshness update - native client

Author: Stacyrch140

articles/bastion/media/native-client/standard.png

@@ -1,11 +1,11 @@
 ---
-title: 'Configure Bastion for native client connections'
+title: Configure Bastion for native client connections
 titleSuffix: Azure Bastion
 description: Learn how to configure Bastion for native client connections.
 author: cherylmc
 ms.service: azure-bastion
 ms.topic: how-to
-ms.date: 08/12/2024
+ms.date: 12/09/2024
 ms.author: cherylmc
 ---
 
@@ -26,7 +26,6 @@ If you haven't already deployed Bastion to your VNet, you can deploy with the na
 
 1. On the **Basics** tab, for **Instance Details -> Tier** select **Standard**. Native client support requires the Standard SKU.
 
-   :::image type="content" source="./media/native-client/standard.png" alt-text="Settings for a new bastion host with Standard SKU selected." lightbox="./media/native-client/standard.png":::
 1. Before you create the bastion host, go to the **Advanced** tab and check the box for **Native Client Support**, along with the checkboxes for any other features that you want to deploy.
 
    :::image type="content" source="./media/native-client/new-host.png" alt-text="Screenshot that shows settings for a new bastion host with Native Client Support box selected." lightbox="./media/native-client/new-host.png":::
@@ -40,8 +39,6 @@ If you've already deployed Bastion to your VNet, modify the following configurat
 1. Navigate to the **Configuration** page for your Bastion resource. Verify that the SKU Tier is **Standard**. If it isn't, select **Standard**.
 1. Select the box for **Native Client Support**, then apply your changes.
 
-    :::image type="content" source="./media/native-client/update-host.png" alt-text="Screenshot that shows settings for updating an existing host with Native Client Support box selected." lightbox="./media/native-client/update-host.png":::
-
 ## <a name="secure"></a>Secure your native client connection
 
 If you want to further secure your native client connection, you can limit port access by only providing access to port 22/3389. To restrict port access, you must deploy the following NSG rules on your AzureBastionSubnet to allow access to select ports and deny access from any other ports.

articles/bastion/media/native-client/update-host.png

@@ -1,12 +1,12 @@
 ---
-title: 'Deploy private-only Bastion'
+title: Deploy private-only Bastion
 description: Learn how to deploy Bastion for a private-only scenario.
 author: cherylmc
 ms.service: azure-bastion
 ms.custom:
   - ignite-2024
 ms.topic: how-to
-ms.date: 05/30/2024
+ms.date: 12/09/2024
 ms.author: cherylmc
 ---
 
@@ -77,9 +77,7 @@ This section helps you deploy Bastion as private-only to your virtual network.
 
 1. On the **Create a Bastion** pane, configure the settings for your bastion host. The **Project details** values are populated from your virtual network values.
 
-    Under **Instance details**, configure these values:
-
-   :::image type="content" source="./media/private-only-deployment/instance-values.png" alt-text="Screenshot of Azure Bastion instance details." lightbox="./media/private-only-deployment/instance-values.png":::
+   Under **Instance details**, configure these values:
 
    * **Name**: The name that you want to use for your Bastion resource.