Merge pull request #273403 from cherylmc/dev-sku-ui

rewrite - new UI

Author: JamesJBarnett

articles/bastion/media/deploy-host-developer-sku/deploy-bastion-developer.png

@@ -4,14 +4,14 @@ description: Learn how to deploy Bastion using the Developer SKU.
 author: cherylmc
 ms.service: bastion
 ms.topic: quickstart
-ms.date: 01/31/2024
+ms.date: 04/25/2024
 ms.author: cherylmc
 ms.custom: references_regions
 ---
 
 # Quickstart: Deploy Azure Bastion - Developer SKU (Preview)
 
-In this quickstart, you'll learn how to deploy Azure Bastion using the Developer SKU. After Bastion is deployed, you can connect to virtual machines (VM) in the virtual network via Bastion using the private IP address of the VM. The VMs you connect to don't need a public IP address, client software, agent, or a special configuration. For more information about Azure Bastion, see [What is Azure Bastion?](bastion-overview.md)
+In this quickstart, you learn how to deploy Azure Bastion using the Developer SKU. After Bastion is deployed, you can connect to virtual machines (VM) in the virtual network via Bastion using the private IP address of the VM. The VMs you connect to don't need a public IP address, client software, agent, or a special configuration. For more information about Azure Bastion, see [What is Azure Bastion?](bastion-overview.md)
 
 The following diagram shows the architecture for Azure Bastion and the Developer SKU.
 
@@ -39,7 +39,7 @@ Because the Developer SKU bastion resource isn't dedicated, the features for the
 
 * **A VM in a VNet**.
 
-  When you deploy Bastion using default values, the values are pulled from the virtual network in which your VM resides. Within the context of this exercise, we use this VM both as the starting point to deploy Bastion, and also to demonstrate how to connect to a VM via Bastion.
+  When you deploy Bastion using default values, the values are pulled from the virtual network in which your VM resides. Make sure the VM resides in a resource group that's in a region where the Developer SKU is supported.
 
   * If you don't already have a VM in a virtual network, create one using [Quickstart: Create a Windows VM](../virtual-machines/windows/quick-create-portal.md), or [Quickstart: Create a Linux VM](../virtual-machines/linux/quick-create-portal.md).
   * If you need example values, see the [Example values](#values) section.
@@ -74,42 +74,25 @@ You can use the following example values when creating this configuration as an
 | Address space | 10.1.0.0/16 |
 | Subnets | FrontEnd: 10.1.0.0/24 |
 
-### Workflow
+## <a name="createvmset"></a>Deploy Bastion and connect to VM
 
-* Deploy Bastion automatically using the Developer SKU.
-* After you deploy Bastion, you'll then connect to your VM via the portal using RDP/SSH connectivity and the VM's private IP address.
-* If your VM has a public IP address that you don't need for anything else, you can remove it.
-
-## <a name="createvmset"></a>Deploy Bastion
-
-When you create Azure Bastion using default settings, the settings are configured for you. You can't modify or specify values for a default deployment.
+These steps help you deploy Bastion using the developer SKU and auotmatically connect to your VM via the portal. To connect to a VM, your NSG rules must allow traffic to ports 22 and 3389 from the private IP address 168.63.129.16.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-1. In the portal, go to the VM to which you want to connect. The values from the virtual network in which this VM resides will be used to create the Bastion deployment.
-1. On the page for your VM, in the **Operations** section on the left menu, select **Bastion**. You can also get to this page via your **Virtual Network/Bastion** in the portal.
-1. On the **Bastion** page, select **Deploy Bastion Developer**.
-
-   :::image type="content" source="./media/deploy-host-developer-sku/deploy-bastion-developer.png" alt-text="Screenshot of the Bastion page showing Deploy Bastion." lightbox="./media/deploy-host-developer-sku/deploy-bastion-developer.png":::
-
-1. Bastion begins deploying. This can take around 10 minutes to complete.
-
-## <a name="connect"></a>Connect to a VM
-
-> [!NOTE]
-> Before connecting to a VM, verify that your NSG rules allow traffic to ports 22 and 3389 from the private IP address 168.63.129.16.
-
-When the Bastion deployment is complete, the screen changes to the **Connect** page.
-
-1. Type your authentication credentials. Then, select **Connect**.
+1. In the portal, go to the VM to which you want to connect. The values from the virtual network in which this VM resides are used to create the Bastion deployment. The VM must be located in a region that supports the Developer SKU.
+1. On the page for your VM, in the **Operations** section on the left menu, select **Bastion**.
+1. On the **Bastion** page, select the **Authentication Type** you want to use, input the required credential values, and click **Connect**.
 
-   :::image type="content" source="./media/quickstart-host-portal/connect-vm.png" alt-text="Screenshot shows the Connect using Azure Bastion dialog." lightbox="./media/quickstart-host-portal/connect-vm.png":::
+   :::image type="content" source="./media/quickstart-developer-sku/deploy-bastion-developer.png" alt-text="Screenshot of the Bastion page showing Deploy Bastion." lightbox="./media/quickstart-developer-sku/deploy-bastion-developer.png":::
 
+1. Bastion deploys using the Developer SKU. 
 1. The connection to this virtual machine via Bastion will open directly in the Azure portal (over HTML5) using port 443 and the Bastion service. Select **Allow** when asked for permissions to the clipboard. This lets you use the remote clipboard arrows on the left of the screen.
 
    * When you connect, the desktop of the VM might look different than the example screenshot.
    * Using keyboard shortcut keys while connected to a VM might not result in the same behavior as shortcut keys on a local computer. For example, when connected to a Windows VM from a Windows client, CTRL+ALT+END is the keyboard shortcut for CTRL+ALT+Delete on a local computer. To do this from a Mac while connected to a Windows VM, the keyboard shortcut is Fn+CTRL+ALT+Backspace.
 
      :::image type="content" source="./media/quickstart-host-portal/connected.png" alt-text="Screenshot showing a Bastion RDP connection selected." lightbox="./media/quickstart-host-portal/connected.png":::
+1. When you disconnect from the VM, Bastion remains deployed to the virtual network. You can reconnect to the VM from the virtual machine page in the Azure portal by selecting **Bastion -> Connect**.
 
 ### <a name="audio"></a>To enable audio output