Study guide

8.2 Azure Bastion Architecture & Secure Remote Access

Designing and Implementing Microsoft Azure Networking Solutions AZ-700

Track your progress as you read

Finished sections get a check mark.

1 Introduction & AZ-700 Exam Overview

0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured

2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture

1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)

3 Chapter 2: Azure Name Resolution & Core Routing

2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange

4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway

3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter

5 Chapter 4: Azure ExpressRoute & Virtual WAN

4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

6 Chapter 5: Regional Load Balancing & Application Gateway

5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design

7 Chapter 6: Global Traffic Management & Azure Front Door

6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door

8 Chapter 7: Azure Private Link & Service Endpoints

7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions

9 Chapter 8: Network Security Groups & Azure Bastion

8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules

10 Chapter 9: Azure Firewall & Security Policies

9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection

11 Chapter 10: Azure Network Observability & Troubleshooting

10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture

8.2 Azure Bastion Architecture & Secure Remote Access

Key Takeaways Explain This Topic AI

Azure Bastion is a fully managed PaaS remote management proxy that provides secure, browser-based and native client RDP (3389) and SSH (22) connectivity to VMs without exposing public IP addresses on target workloads.

Azure Bastion requires a dedicated subnet named exactly 'AzureBastionSubnet' with a minimum prefix of /26 (64 IP addresses) to accommodate platform management, autoscaling, and maintenance upgrades.

Azure Bastion is offered across Developer, Basic, Standard, and Premium SKUs; Standard adds native client support, IP-based connection, shareable links, and manual/autoscaling (up to 50 scale units), while Premium introduces session recording and private-only deployment.

The AzureBastionSubnet enforces mandatory NSG rules: Inbound requires HTTPS 443 from Internet, HTTPS 443 from GatewayManager, HTTPS 443 from AzureLoadBalancer, and ports 5701/8080 from VirtualNetwork; Outbound requires ports 22/3389 to VirtualNetwork, port 443 to AzureCloud, ports 5701/8080 to VirtualNetwork, and port 80 to Internet for CRL/session validation.

IP-based connection enables Bastion Standard/Premium to target virtual machines across peered VNets or on-premises networks via private IP address, eliminating the need to deploy redundant Bastion hosts in every spoke VNet.

Last updated: August 2026

Azure Bastion Architecture & Secure Remote Access

Traditional remote administration of cloud infrastructure often relied on deploying public-facing "jump boxes" or assigning public IP addresses directly to virtual machines. This approach exposed critical management protocols— Remote Desktop Protocol (RDP / TCP 3389) and Secure Shell (SSH / TCP 22) —to automated port scanners, brute force dictionary attacks, credential stuffing, and zero-day protocol exploits.

Azure Bastion solves this security challenge by providing a fully managed, platform-as-a-service (PaaS) bastion proxy deployed directly inside your Virtual Network. Administrators establish an encrypted TLS (HTTPS port 443) connection from their web browser or native client to the Azure Bastion host. The Bastion host terminates the TLS session and proxies the RDP or SSH stream over the private Azure SDN fabric to the target VM's private IP address. +-----------------------------------------------------------------------------+

  • | AZURE BASTION ARCHITECTURE |
  • | |
  • | Administrator Workstation |
  • | | |
  • | | (1) Encrypted TLS / HTTPS (Port 443) |
  • | v |
  • | +---------------------------------------------------------------------+ |
  • | | Azure Virtual Network (Hub-VNet: 10.100.0.0/16) | |
  • | | |
  • | | +-------------------------------------------------------------+ |
  • | | | Subnet: AzureBastionSubnet (10.100.0.0/26) | |
  • | | | [ Azure Bastion PaaS Scale Units (Standard SKU: 2-50) ] | |
  • | | | - Public IP: 52.183.40.50 (TLS Ingress) | |
  • | | | - NSG: Mandatory Platform Inbound/Outbound Rules | |
  • | | +-------------------------------------------------------------+ |
  • | | | |
  • | | | (2) Private RDP (3389) / SSH (22)|
  • | | v |
  • | | +-------------------------------------------------------------+ |
  • | | | Subnet: Workload-Subnet (10.100.1.0/24) | |
  • | | | [ Target VM: 10.100.1.4 ] (NO Public IP Required!) | |
  • | | +-------------------------------------------------------------+ |
  • | +---------------------------------------------------------------------+ |
  • | | |
  • | | (3) Cross-Peered VNet Reachability |
  • | v |
  • | +---------------------------------------------------------------------+ |
  • | | Peered Spoke VNet (10.200.0.0/16) | |
  • | | [ Target VM: 10.200.1.4 ] (Accessible via IP-Based Connection) | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+
  • 1. Dedicated Subnet Architecture: AzureBastionSubnet

Azure Bastion requires a dedicated, specially configured subnet within the host Virtual Network. Sizing and naming rules are strictly enforced by Azure Resource Manager:

Subnet Name: Must be named exactly AzureBastionSubnet (case-sensitive). Any other name will cause deployment validation to fail.

Minimum Subnet Sizing: Sized at /26 or larger (e.g., /26 provides 64 total IP addresses, /25 provides 128). Deploying in a /27 (32 IPs) or /28 (16 IPs) is explicitly rejected by the platform.

Workload Isolation: No other resources (such as standard VMs, load balancers, or application gateways) can be deployed inside AzureBastionSubnet .

Route Table (UDR) Restrictions: You must not attach a User-Defined Route (UDR) to AzureBastionSubnet that directs 0.0.0.0/0 internet traffic to a firewall or Network Virtual Appliance (NVA). Forcing default route egress through an NVA breaks Azure Bastion control plane management and health probing.

2. Azure Bastion SKU Comparison Matrix

Azure Bastion is available in four feature tiers: Developer , Basic , Standard , and Premium .

Feature / Capability Developer SKU Basic SKU Standard SKU Premium SKU

Architecture / Tenancy Multi-tenant shared pool Dedicated PaaS instance Dedicated PaaS instance Dedicated PaaS instance

Subnet & Public IP No dedicated subnet/PIP Requires AzureBastionSubnet (/26) + Standard PIP Requires AzureBastionSubnet (/26) + Standard PIP Requires AzureBastionSubnet (/26) + Standard PIP (or Private-only)

Scale Units (Instances) 1 (Fixed) 2 (Fixed) 2 to 50 scale units (Manual / Autoscale) 2 to 50 scale units (Manual / Autoscale)

Concurrent Sessions 1 session Up to ~20 RDP / 40 SSH Up to ~500 RDP / 1000 SSH (at 50 units) Up to ~500 RDP / 1000 SSH (at 50 units)

Web Browser Access (HTML5) Supported Supported Supported Supported

Native Client Support Not supported Not supported Supported ( az network bastion rdp/ssh , mstsc , OpenSSH) Supported

  • IP-Based Connection Not supported Not supported Supported (Target VMs across peered VNets / on-prem) Supported
  • Shareable Links Not supported Not supported Supported (One-click access without portal) Supported
  • Custom Inbound Ports Not supported Not supported Supported (Non-standard RDP/SSH ports) Supported
  • Session Recording Not supported Not supported Not supported Supported (Video capture to Azure Blob Storage)

Private-Only Deployment Not supported Not supported Not supported Supported (No public IP; private access only)

Kerberos Authentication Not supported Not supported Supported Supported

Important

Scale Unit Capacity Planning: Each scale unit in Azure Bastion Standard and Premium supports approximately 10 concurrent RDP sessions or 20 concurrent SSH sessions . A deployment scaled to 10 scale units can handle ~100 concurrent RDP sessions or ~200 concurrent SSH sessions.

Loading diagram... Azure Bastion Hub-and-Spoke Deployment and Advanced Feature Topology

  • 3. Advanced Bastion Capabilities Deep-Dive
  • Native Client Support

Standard and Premium SKUs allow administrators to connect to target virtual machines using their preferred local desktop tools—such as Windows Remote Desktop Connection ( mstsc.exe ) , OpenSSH client , PuTTY, or Visual Studio Code Remote SSH —instead of being confined to a web browser tab.

Native client connectivity operates by leveraging the Azure CLI ( az network bastion ) to establish a secure local-to-remote TLS tunnel: # Connect to a Windows VM via native RDP client through Bastion:

  • az network bastion rdp \
  • -name "Production-Bastion" \
  • -resource-group "RG-Networking" \
  • -target-resource-id "/subscriptions/.../virtualMachines/Win-Server01"

# Connect to a Linux VM using native SSH client and SSH key:

  • az network bastion ssh \
  • -name "Production-Bastion" \
  • -resource-group "RG-Networking" \
  • -target-resource-id "/subscriptions/.../virtualMachines/Linux-Worker01" \
  • -auth-type "ssh-key" \
  • -username "azureuser" \
  • -ssh-key "~/.ssh/id_rsa"

# Open a local tunnel for arbitrary tooling (e.g., custom RDP port mapping):

  • az network bastion tunnel \
  • -name "Production-Bastion" \
  • -resource-group "RG-Networking" \
  • -target-resource-id "/subscriptions/.../virtualMachines/Linux-Worker01" \
  • -resource-port 22 \
  • -port 50022
  • IP-Based Connection

In multi-VNet hub-and-spoke topologies, deploying an Azure Bastion host in every spoke VNet is cost-prohibitive. IP-Based Connection allows a centralized Azure Bastion Standard or Premium host deployed in the Hub VNet to connect to target VMs located across:

  • Peered Spoke VNets (via Regional or Global VNet Peering)
  • On-Premises Datacenters (reachable across ExpressRoute or Site-to-Site VPN)
  • Non-Azure endpoints with routable private IP addresses

Instead of specifying an Azure Resource ID, the administrator enters the target's private IPv4 address (e.g., 10.200.1.10 ) directly in the Azure Portal or CLI.

Shareable Links

Shareable Links enable frictionless, secure remote access for third-party vendors, external contractors, or auditors who do not possess user accounts in your Microsoft Entra ID tenant or Azure RBAC permissions on the subscription:

An administrator generates a unique Shareable Link for a specific target VM.

The external user opens the URL in any standard web browser.

The user authenticates directly against the target operating system (using local VM credentials or domain credentials) over an encrypted HTTPS session without accessing the Azure Portal.

Administrators can view, audit, and revoke shareable links instantly at any time from the Azure Bastion management blade.

Session Recording (Premium SKU)

For highly regulated industries (such as banking, healthcare, and defense), Azure Bastion Premium provides built-in Session Recording :

Automatically records all graphical RDP sessions and terminal SSH sessions.

Stores recordings as append blobs directly into a designated Azure Blob Storage container in your subscription.

Captures rich metadata (start time, session duration, username, source IP, target VM, protocol).

Enables forensic security investigations, compliance audits, and non-repudiation verification.

4. Mandatory NSG Rules on AzureBastionSubnet

To ensure platform security, cluster synchronization, and control plane management, Azure enforces strict Network Security Group (NSG) rules on AzureBastionSubnet . If an associated NSG omits any required rule or blocks platform traffic, deployment will fail with a NetworkIntentPolicyValidationFailed error.

Inbound NSG Requirements

Priority Rule Name Source Port Destination Port Protocol Access Technical Purpose

100 AllowHttpsInbound Internet (or Admin Public IPs) * * 443 TCP Allow Ingress HTTPS traffic from administrators connecting to Bastion.

110 AllowGatewayManagerInbound GatewayManager * * 443 TCP Allow Azure control plane management and health monitoring.

120 AllowAzureLoadBalancerInbound AzureLoadBalancer * * 443 TCP Allow Infrastructure health probing ( 168.63.129.16 ).

130 AllowBastionHostCommunication VirtualNetwork * VirtualNetwork 5701, 8080 TCP Allow Data plane clustering and session synchronization between Bastion scale units.

65500 DenyAllInBound * * * * * Deny Default fallback deny.

Outbound NSG Requirements

Priority Rule Name Source Port Destination Port Protocol Access Technical Purpose

100 AllowSshRdpOutbound * * VirtualNetwork 22, 3389 TCP Allow Egress RDP and SSH traffic to target workload VMs in local or peered VNets.

110 AllowAzureCloudOutbound * * AzureCloud 443 TCP Allow Egress to Azure platform services (diagnostics, logging, metrics, telemetry).

120 AllowBastionCommunication VirtualNetwork * VirtualNetwork 5701, 8080 TCP Allow Internal inter-node clustering communication across scale units.

130 AllowGetSessionInformation * * Internet 80 TCP Allow Session token validation and Certificate Revocation List (CRL) PKI checks.

65500 DenyAllOutBound * * * * * Deny Default fallback deny.

Caution

The Port 80 Outbound Requirement: Administrators frequently attempt to block outbound TCP Port 80 to the Internet on AzureBastionSubnet , believing HTTP is insecure. However, Azure Bastion requires outbound Port 80 for Certificate Revocation List (CRL) validation and session authentication. Blocking outbound Port 80 causes TLS handshakes to fail, completely disabling Bastion remote access.