Skip to content

Commit 188abac

Browse files
committed
docs: Remove duplicate sections and fix heading structure
- Remove duplicate 'Deploy Azure Bastion' section - Remove duplicate 'Create a second virtual network' section - Remove incorrect H2 headings from inside PowerShell and CLI tab sections - Clean document structure now has proper H2 sections with H3 tabs
1 parent e725b67 commit 188abac

1 file changed

Lines changed: 1 addition & 117 deletions

File tree

articles/virtual-network/tutorial-connect-virtual-networks.md

Lines changed: 1 addition & 117 deletions
Original file line numberDiff line numberDiff line change
@@ -427,119 +427,7 @@ az network vnet create \
427427

428428
---
429429

430-
## Deploy Azure Bastion
431-
432-
### [Portal](#tab/portal)
433-
434-
Azure Bastion uses your browser to connect to virtual machines (VMs) in your virtual network over secure shell (SSH) or remote desktop protocol (RDP) by using their private IP addresses. The virtual machines don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see [Azure Bastion](/azure/bastion/bastion-overview).
435-
436-
>[!NOTE]
437-
>[!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
438-
439-
1. In the search box at the top of the portal, enter **Bastion**. Select **Bastions** in the search results.
440-
441-
1. Select **+ Create**.
442-
443-
1. In the **Basics** tab of **Create a Bastion**, enter, or select the following information:
444-
445-
| Setting | Value |
446-
|---|---|
447-
| **Project details** | |
448-
| Subscription | Select your subscription. |
449-
| Resource group | Select **test-rg**. |
450-
| **Instance details** | |
451-
| Name | Enter **bastion**. |
452-
| Region | Select **East US 2**. |
453-
| Tier | Select **Developer**. |
454-
| **Configure virtual networks** | |
455-
| Virtual network | Select **vnet-1**. |
456-
| Subnet | The **AzureBastionSubnet** is created automatically with an address space of **/26** or larger. |
457-
458-
1. Select **Review + create**.
459-
460-
1. Select **Create**.
461-
462-
### [PowerShell](#tab/powershell)
463-
464-
Create a public IP address for the Azure Bastion host with [New-AzPublicIpAddress](/powershell/module/az.network/new-azpublicipaddress). The following example creates a public IP address named *public-ip-bastion* in the *vnet-1* virtual network.
465-
466-
```azurepowershell-interactive
467-
$publicIpParams = @{
468-
ResourceGroupName = "test-rg"
469-
Name = "public-ip-bastion"
470-
Location = "EastUS2"
471-
AllocationMethod = "Static"
472-
Sku = "Standard"
473-
}
474-
New-AzPublicIpAddress @publicIpParams
475-
```
476-
477-
Create an Azure Bastion host with [New-AzBastion](/powershell/module/az.network/new-azbastion). The following example creates an Azure Bastion host named *bastion* in the *AzureBastionSubnet* subnet of the *vnet-1* virtual network. Azure Bastion is used to securely connect Azure virtual machines without exposing them to the public internet.
478-
479-
```azurepowershell-interactive
480-
$bastionParams = @{
481-
ResourceGroupName = "test-rg"
482-
Name = "bastion"
483-
VirtualNetworkName = "vnet-1"
484-
PublicIpAddressName = "public-ip-bastion"
485-
PublicIpAddressRgName = "test-rg"
486-
VirtualNetworkRgName = "test-rg"
487-
Sku = "Basic"
488-
}
489-
New-AzBastion @bastionParams -AsJob
490-
```
491-
492-
### [CLI](#tab/cli)
493-
494-
Create a public IP address for the Azure Bastion host with [az network public-ip create](/cli/azure/network/public-ip). The following example creates a public IP address named *public-ip-bastion* in the *vnet-1* virtual network.
495-
496-
```azurecli-interactive
497-
az network public-ip create \
498-
--resource-group test-rg \
499-
--name public-ip-bastion \
500-
--location eastus2 \
501-
--allocation-method Static \
502-
--sku Standard
503-
```
504-
505-
Create an Azure Bastion host with [az network bastion create](/cli/azure/network/bastion). The following example creates an Azure Bastion host named *bastion* in the *AzureBastionSubnet* subnet of the *vnet-1* virtual network. Azure Bastion is used to securely connect Azure virtual machines without exposing them to the public internet.
506-
507-
```azurecli-interactive
508-
az network bastion create \
509-
--resource-group test-rg \
510-
--name bastion \
511-
--vnet-name vnet-1 \
512-
--public-ip-address public-ip-bastion \
513-
--location eastus2 \
514-
--sku Basic \
515-
--no-wait
516-
```
517-
518-
---
519-
520-
## Create a second virtual network
521-
522-
### [Portal](#tab/portal)
523-
524-
Repeat the previous steps to create a second virtual network with the following values:
525-
526-
>[!NOTE]
527-
>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.
528-
529-
| Setting | Value |
530-
| --- | --- |
531-
| Name | **vnet-2** |
532-
| Address space | **10.1.0.0/16** |
533-
| Resource group | **test-rg** |
534-
| Subnet name | **subnet-1** |
535-
| Subnet address range | **10.1.0.0/24** |
536-
537-
### [PowerShell](#tab/powershell)
538-
539-
Create a second virtual network with [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork). The following example creates a virtual network named **vnet-2** with the address prefix **10.1.0.0/16**.
540-
541-
>[!NOTE]
542-
>The second virtual network can be in the same region as the first virtual network or in a different region. You don't need a 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.
430+
## Peer virtual networks
543431

544432
### [Portal](#tab/portal)
545433

@@ -549,8 +437,6 @@ Create a second virtual network with [New-AzVirtualNetwork](/powershell/module/a
549437

550438
### [PowerShell](#tab/powershell)
551439

552-
## Peer virtual networks
553-
554440
Create a peering with [Add-AzVirtualNetworkPeering](/powershell/module/az.network/add-azvirtualnetworkpeering). The following example peers **vnet-1** to **vnet-2**.
555441

556442
```azurepowershell-interactive
@@ -587,8 +473,6 @@ Resources in one virtual network can't communicate with resources in the other v
587473

588474
### [CLI](#tab/cli)
589475

590-
## Peer virtual networks
591-
592476
Peerings are established between virtual network resource IDs. Obtain the ID of each virtual network with [az network vnet show](/cli/azure/network/vnet#az-network-vnet-show) and store the resource IDs in their respective variables.
593477

594478
```azurecli-interactive

0 commit comments

Comments
 (0)