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
1. Sign in to the [Azure portal](https://portal.azure.com).
64
+
65
+
1. In the search box at the top of the portal, enter **Resource group**. Select **Resource groups** in the search results.
66
+
67
+
1. Select **+ Create**.
68
+
69
+
1. In the **Basics** tab of **Create a resource group**, enter or select the following information:
70
+
71
+
| Setting | Value |
72
+
| ------- | ----- |
73
+
| Subscription | Select your subscription. |
74
+
| Resource group | Enter **test-rg**. |
75
+
| Region | Select **East US 2**. |
76
+
77
+
1. Select **Review + create**.
78
+
79
+
1. Select **Create**.
80
+
81
+
## Create a virtual network
82
+
83
+
1. In the search box at the top of the portal, enter **Virtual network**. Select **Virtual networks** in the search results.
84
+
85
+
1. Select **+ Create**.
86
+
87
+
1. On the **Basics** tab of **Create virtual network**, enter or select the following information:
88
+
89
+
| Setting | Value |
90
+
|---|---|
91
+
|**Project details**||
92
+
| Subscription | Select your subscription. |
93
+
| Resource group | Select **test-rg**. |
94
+
|**Instance details**||
95
+
| Name | Enter **vnet-1**. |
96
+
| Region | Select **East US 2**. |
97
+
98
+
1. Select **Next** to proceed to the **Security** tab.
99
+
100
+
1. Select **Next** to proceed to the **IP Addresses** tab.
101
+
102
+
1. In the address space box in **Subnets**, select the **default** subnet.
103
+
104
+
1. In **Edit subnet**, enter or select the following information:
105
+
106
+
| Setting | Value |
107
+
|---|---|
108
+
|**Subnet details**||
109
+
| Subnet template | Leave the default **Default**. |
110
+
| Name | Enter **subnet-1**. |
111
+
| Starting address | Leave the default of **10.0.0.0**. |
112
+
| Subnet size | Leave the default of **/24 (256 addresses)**. |
113
+
114
+
1. Select **Save**.
115
+
116
+
1. Select **Review + create** at the bottom of the screen, and when validation passes, select **Create**.
117
+
118
+
## Deploy Azure Bastion
119
+
120
+
Azure Bastion uses your browser to connect to VMs in your virtual network over secure shell (SSH) or remote desktop protocol (RDP) by using their private IP addresses. The VMs don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see [Azure Bastion](/azure/bastion/bastion-overview).
1. In the search box at the top of the portal, enter **Bastion**. Select **Bastions** in the search results.
126
+
127
+
1. Select **+ Create**.
128
+
129
+
1. In the **Basics** tab of **Create a Bastion**, enter or select the following information:
130
+
131
+
| Setting | Value |
132
+
|---|---|
133
+
|**Project details**||
134
+
| Subscription | Select your subscription. |
135
+
| Resource group | Select **test-rg**. |
136
+
|**Instance details**||
137
+
| Name | Enter **bastion**. |
138
+
| Region | Select **East US 2**. |
139
+
| Tier | Select **Developer**. |
140
+
|**Configure virtual networks**||
141
+
| Virtual network | Select **vnet-1**. |
142
+
| Subnet | The **AzureBastionSubnet** is created automatically with an address space of **/26** or larger. |
143
+
144
+
1. Select **Review + create**.
145
+
146
+
1. Select **Create**.
147
+
148
+
## Create a second virtual network
62
149
63
150
Repeat the previous steps to create a second virtual network with the following values:
64
151
65
152
>[!NOTE]
66
-
>The second virtual network can be in the same region as the first virtual network or in a different region. You can skip the **Security** tab and the Bastion deployment for the second virtual network. After the virtual network peering is established, you can connect to both virtual machines with the same Bastion deployment.
153
+
>The second virtual network can be in the same region as the first virtual network or in a different region. You can skip the Bastion deployment for the second virtual network. After the virtual network peering is established, you can connect to both virtual machines with the same Bastion deployment.
67
154
68
155
| Setting | Value |
69
156
| --- | --- |
@@ -150,6 +237,7 @@ $bastionParams = @{
150
237
PublicIpAddressName = "public-ip-bastion"
151
238
PublicIpAddressRgName = "test-rg"
152
239
VirtualNetworkRgName = "test-rg"
240
+
Sku = "Basic"
153
241
}
154
242
New-AzBastion @bastionParams -AsJob
155
243
```
@@ -242,6 +330,7 @@ az network bastion create \
242
330
--vnet-name vnet-1 \
243
331
--public-ip-address public-ip-bastion \
244
332
--location eastus2 \
333
+
--sku Basic \
245
334
--no-wait
246
335
```
247
336
@@ -370,14 +459,60 @@ Test the communication between the virtual machines by creating a virtual machin
0 commit comments