You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/bastion/quickstart-host-portal.md
+22-19Lines changed: 22 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
-
title: 'Quickstart: Deploy Bastion from VM settings'
2
+
title: 'Quickstart: Deploy Bastion with default settings'
3
3
titleSuffix: Azure Bastion
4
-
description: Learn how to create an Azure Bastion host from virtual machine settings and connect to the VM securely through your browser via private IP address.
4
+
description: Learn how to deploy Bastion with default settings from the Azure portal.
#Customer intent: As someone with a networking background, I want to connect to a virtual machine securely via RDP/SSH using a private IP address through my browser.
13
13
---
14
14
15
-
# Quickstart: Deploy Azure Bastion from VM settings
15
+
# Quickstart: Deploy Azure Bastion with default settings
16
16
17
-
This quickstart article shows youhow to deploy Azure Bastion to your virtual network from the Azure portal based on settings from an existing virtual machine. After you deploy Bastion, the RDP/SSH experience is available to all of the virtual machines in the virtual network. Azure Bastion is a PaaS service that is maintained for you. For more information about Azure Bastion, see [What is Azure Bastion?](bastion-overview.md)
17
+
In this quickstart, you'll learn how to deploy Azure Bastion with default settings to your virtual network using the Azure portal. After Bastion is deployed, you can connect (SSH/RDP) to virtual machines in the virtual network via Bastion using the private IP address of the VM. When you connect to a VM, it doesn't need a public IP address, client software, agent, or a special configuration.
18
18
19
-
In this quickstart, after you deploy Bastion, you connect to your VM via private IP address using the Azure portal. When you connect to the VM, it doesn't need a public IP address, client software, agent, or a special configuration. If your VM has a public IP address that you don't need for anything else, you can remove it.
19
+
In this quickstart, you deploy Bastion from your VM resource using the Azure portal. Bastion is deployed using default settings that are based on the virtual network in which your VM is located. You then connect to your VM 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.
20
+
21
+
Azure Bastion is a PaaS service that's maintained for you, not a bastion host that you install on one of your VMs and maintain yourself. For more information about Azure Bastion, see [What is Azure Bastion?](bastion-overview.md)
20
22
21
23
## <aname="prereq"></a>Prerequisites
22
24
23
25
***An Azure account with an active subscription**. If you don't have one, [create one for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
24
26
25
-
***A VM in a VNet**. This quickstart lets you quickly deploy Bastion to a VNet using settings from the virtual machine to which you want to connect. Bastion pulls the required values from the VM and deploys to the VNet based on these values. The virtual machine itself doesn't become a bastion host.
27
+
***A VM in a VNet**.
28
+
29
+
When you deploy Bastion using default values, the values are pulled from the VNet in which your VM resides. This VM doesn't become a part of the Bastion deployment itself, but you do connect to it later in the exercise.
26
30
27
-
* If you don't already have a VM in a VNet, create one using [Quickstart: Create a VM](../virtual-machines/windows/quick-create-portal.md).
28
-
* If you need example values, see the provided [Example values](#values).
29
-
* If you already have a virtual network, make sure to select it on the Networking tab when you create your VM.
30
-
* If you don't already have a virtual network, you can create one at the same time you create your VM.
31
-
* You don't need to have a public IP address for this VM in order to connect via Azure Bastion.
31
+
* If you don't already have a VM in a VNet, 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).
32
+
* If you need example values, see the [Example values](#values) section.
33
+
* If you already have a virtual network, make sure it's selected on the Networking tab when you create your VM.
34
+
* If you don't have a virtual network, you can create one at the same time you create your VM.
32
35
33
36
***Required VM roles:**
34
37
@@ -61,23 +64,23 @@ You can use the following example values when creating this configuration, or yo
61
64
62
65
**Bastion values:**
63
66
64
-
When you deploy from VM settings, Bastion is automatically configured with default values. You don't need to specify any additional values for this exercise. However, once Bastion deploys, you can later modify [configuration settings](configuration-settings.md). For example, the SKU that is automatically configured is the Basic SKU. To support more Bastion features, you can easily [upgrade the SKU](upgrade-sku.md) after the deployment completes.
67
+
When you deploy from VM settings, Bastion is automatically configured with default values.
65
68
66
-
After completing this configuration, you'll have an Azure Bastion deployment with the values listed in the following table:
69
+
You can't modify or specify additional values for a default deployment. However, once Bastion deploys, you can later modify [settings](configuration-settings.md). For example, the default SKU is the Basic SKU. You can later upgrade to the Standard SKU to support more features.
67
70
68
-
|**Name**|**Value**|
71
+
|**Name**|**Default value**|
69
72
|---|---|
70
73
|AzureBastionSubnet | This subnet is created within the VNet as a /26 |
71
74
|SKU | Basic |
72
75
| Name | Based on the virtual network name |
73
76
| Public IP address name | Based on the virtual network name |
74
77
75
-
## <aname="createvmset"></a>Deploy Bastion to a VNet
78
+
## <aname="createvmset"></a>Deploy Bastion
76
79
77
-
There are a few different ways to deploy Bastion to a virtual network. In this quickstart, you deploy Bastion from your virtual machine settings in the Azure portal (you don't sign in and deploy from your VM directly).
80
+
In this quickstart, you deploy Bastion from your virtual machine settings in the Azure portal. You don't connect and sign in to your virtual machine or deploy Bastion from your VM directly.
78
81
79
82
1. Sign in to the [Azure portal](https://portal.azure.com).
80
-
1. In the portal, navigate 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.
83
+
1. In the portal, navigate 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.
81
84
1. Select **Bastion** in the left menu. You can view some of the values that will be used when creating the bastion host for your virtual network. Select **Deploy Bastion**.
82
85
83
86
:::image type="content" source="./media/quickstart-host-portal/deploy-bastion.png" alt-text="Screenshot of Deploy Bastion." lightbox="./media/quickstart-host-portal/deploy-bastion.png":::
@@ -115,7 +118,7 @@ When you're done using the virtual network and the virtual machines, delete the
115
118
116
119
## Next steps
117
120
118
-
In this quickstart, you created a bastion host for your virtual network, and then connected to a virtual machine securely via Bastion. Next, you can continue with the following step if you want to connect to a virtual machine scale set.
121
+
In this quickstart, you deployed Bastion to your virtual network, and then connected to a virtual machine securely via Bastion. Next, you can continue with the following step if you want to connect to a virtual machine scale set.
119
122
120
123
> [!div class="nextstepaction"]
121
-
> [Connect to a virtual machine scale set using Azure Bastion](bastion-connect-vm-scale-set.md)
124
+
> [Connect to a virtual machine scale set using Azure Bastion](bastion-connect-vm-scale-set.md)
0 commit comments