Skip to content

Commit 37675bb

Browse files
authored
Merge pull request #177982 from dagiro/Freshness15
Freshness15 - Enable browser connection on Azure DevTest Labs virtual machines
2 parents 1166b3b + af0f9eb commit 37675bb

File tree

9 files changed

+37
-37
lines changed

9 files changed

+37
-37
lines changed

articles/devtest-labs/enable-browser-connection-lab-virtual-machines.md

Lines changed: 37 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -2,61 +2,61 @@
22
title: Enable browser connection on Azure DevTest Labs virtual machines
33
description: DevTest Labs now integrates with Azure Bastion, as an owner of the lab you can enable accessing all lab virtual machines through a browser.
44
ms.topic: how-to
5-
ms.date: 06/26/2020
5+
ms.date: 10/28/2021
66
---
77

88
# Enable browser connection on Azure DevTest Labs virtual machines
9-
DevTest Labs integrates with [Azure Bastion](../bastion/index.yml), which enables you to connect to your virtual machines through a browser. You first need to enable browser connection on lab virtual machines.
109

11-
As an owner of a lab you can enable accessing all lab virtual machines through a browser. You don't need an additional client, agent, or piece of software. Azure Bastion provides secure and seamless RDP/SSH connectivity to your virtual machines directly in the Azure portal over TLS. When you connect via Azure Bastion, your virtual machines don't need a public IP address. For more information, see [What is Azure Bastion?](../bastion/bastion-overview.md)
10+
DevTest Labs integrates with [Azure Bastion](../bastion/index.yml), which enables you to connect to your virtual machines through a browser. You first need to enable browser connections to lab virtual machines.
1211

12+
As an owner of a lab, you can enable accessing all lab virtual machines through a browser. You don't need another client, agent, or piece of software. Azure Bastion provides secure and seamless RDP/SSH connectivity to your virtual machines directly in the Azure portal over TLS. When you connect via Azure Bastion, your virtual machines don't need a public IP address. For more information, see [What is Azure Bastion?](../bastion/bastion-overview.md)
1313

14-
This article shows how to enable browser connection on lab virtual machines.
14+
In this guide, you'll enable browser connections to lab virtual machines.
1515

16-
## Prerequisites
17-
- Either deploy a Bastion host in your existing lab's virtual network **(OR)** connect your lab with a Bastion configured virtual network.
18-
To learn how to deploy a Bastion host in a virtual network, see [Create an Azure Bastion host](../bastion/tutorial-create-host-portal.md). When creating the Bastion host, select the lab's virtual network.
19-
- Lab user needs to have a **Reader** role on the Bastion host and the virtual network that has the Bastion configured.
16+
## Prerequisites
2017

21-
## Create a second sub net in the Bastion virtual network
22-
First, you need to create a second subnet in the Bastion virtual network because the AzureBastionSubnet doesn't allow creation of non-Bastion resources in it.
23-
Create another subnet within the Bastion virtual network as shown in the following image:
18+
- A lab in [Azure DevTest Labs](./devtest-lab-overview.md).
2419

25-
![Second subnet in Azure Bastion virtual network](./media/connect-virtual-machine-through-browser/second-subnet.png)
20+
- Your lab's virtual network configured with Bastion. See [Create an Azure Bastion host](../bastion/tutorial-create-host-portal.md) for steps on adding Bastion.
2621

27-
## Enable VM creation in the subnet
28-
Now, enable the creation of VMs in this subnet by following these steps:
22+
- The lab user needs to be a member of the **Reader** role on the Bastion host and the virtual network that has Bastion configured.
23+
24+
## Add virtual network to lab
2925

3026
1. Sign in to the [Azure portal](https://portal.azure.com).
31-
1. Select **All Services** on the left navigational menu.
32-
1. Select **DevTest Labs** from the list.
33-
1. From the list of labs, select *your lab*.
34-
35-
> [!NOTE]
36-
> Azure Bastion is now generally available in the following regions: West US, East US, West Europe, South Central US, Australia East, and Japan East. So, create a lab in one of these regions if your lab isn't in one of them.
37-
38-
1. Select **Configuration and policies** in the **Settings** section on the left menu.
39-
1. Select **Virtual networks**.
40-
1. Select **Add** from the toolbar.
41-
1. Select the **virtual network** that has the Bastion host deployed.
42-
1. Select the subnet for VMs, not the **AzureBastionSubnet**, the other one you created earlier. Close the page and reopen it if you don't see the subnet in the list at the bottom.
43-
44-
![Enable VM creation in the subnet](./media/connect-virtual-machine-through-browser/enable-vm-creation-subnet.png)
45-
1. Select **Use in virtual machine creation** option.
46-
1. Select **Save** on the toolbar.
47-
1. If you have an old virtual network for the lab, remove it by selecting **...* and **Remove**.
27+
28+
1. Navigate to your lab in **DevTest Labs**.
29+
30+
1. Under **Settings**, select **Configuration and policies**.
31+
32+
:::image type="content" source="./media/enable-browser-connection-lab-virtual-machines/portal-lab-configurations-policies.png" alt-text="Screenshot of configurations and policies.":::
33+
34+
1. On the **Configuration and policies** page, under **External resources**, select **Virtual networks**.
35+
36+
1. Select your Bastion configured virtual network.
37+
38+
:::image type="content" source="./media/enable-browser-connection-lab-virtual-machines/virtual-network-added.png" alt-text="Screenshot of added virtual network.":::
39+
40+
1. On the **Virtual network** page, select the subnet for VMs, not **AzureBastionSubnet**.
41+
42+
1. On the **Lab Subnet** section, for the **Use in virtual machine creation** option, select **Yes**. Then select **Save**.
43+
44+
:::image type="content" source="./media/enable-browser-connection-lab-virtual-machines/allow-subnet-use.png" alt-text="Screenshot of selection for allow subnet use option.":::
45+
46+
1. On the **Virtual network** page, select **Save**. You'll then be returned to the **Virtual networks** section of **Configuration and policies**.
4847

4948
## Enable browser connection
5049

51-
Once you have a Bastion configured virtual network inside the lab, as a lab owner, you can enable browser connect on lab virtual machines.
50+
Once you have a Bastion configured virtual network inside the lab, as a lab owner, you can enable browser connect to lab virtual machines.
51+
52+
These steps continue immediately from the prior section.
5253

53-
To enable browser connect on lab virtual machines, follow these steps:
54+
1. Under **Settings**, select **Browser connect**.
5455

55-
1. In the Azure portal, navigate to *your lab*.
56-
1. Select **Configuration and policies**.
57-
1. In **Settings**, select **Browser connect**. If you don't see this option, close the **Configuration policies** page, and reopen it.
56+
1. Under the **Browser access to virtual machines** section, select **Yes** for **Browser connect**. Then select **Save**.
5857

59-
![Enable browser connection](./media/enable-browser-connection-lab-virtual-machines/browser-connect.png)
58+
:::image type="content" source="./media/enable-browser-connection-lab-virtual-machines/enable-browser-connect.png" alt-text="Screenshot of enabling browser connect option.":::
6059

6160
## Next Steps
61+
6262
See the following article to learn how to connect to your VMs using a browser: [Connect to your virtual machines through a browser](connect-virtual-machine-through-browser.md)
31.5 KB
Loading
38.6 KB
Loading
Loading
14.3 KB
Loading
27.5 KB
Loading
25.2 KB
Loading

0 commit comments

Comments
 (0)