Study guide

Azure Networking: Private Link, Service Endpoints, and Bastion

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

Azure Networking: Private Link, Service Endpoints, and Bastion

Key Takeaways Explain This Topic AI

Azure Private Link projects a PaaS service into your VNet as a private endpoint with a private IP, so traffic never touches the public internet.

Service Endpoints keep the service's public IP but restrict access to traffic originating from your VNet, and they are free.

Azure Bastion gives browser-based RDP and SSH over TLS to VMs with no public IP and no open inbound 3389/22 ports.

Private Link offers data-exfiltration protection and on-premises reachability over VPN or ExpressRoute; Service Endpoints do not.

Bastion must be deployed into a dedicated subnet named AzureBastionSubnet within the target VNet.

Last updated: October 2026

Quick Answer: Private Link = a PaaS service gets a private IP inside your VNet (a private endpoint); traffic stays on the Microsoft backbone. Service Endpoint = the service keeps its public IP but only accepts traffic from your VNet (and it is free). Azure Bastion = browser-based RDP/SSH over TLS to VMs with no public IP and no open management ports.

Azure Private Link and private endpoints

By default an Azure PaaS service such as Storage or SQL Database has a public endpoint. Azure Private Link removes that exposure by creating a private endpoint — a network interface card with a private IP from your subnet that maps to a specific resource.

How it works

The private endpoint gets a private IP from your VNet's address space.

Traffic from your VNet to the service stays entirely on the Microsoft backbone network — it never traverses the public internet.

The service is no longer reachable from the public internet through that endpoint, so there is data-exfiltration protection : the endpoint maps to one specific resource, not the whole service.

Private DNS resolves the service FQDN to the private IP, so existing connection strings keep working.

On-premises systems can reach the private endpoint over VPN Gateway or ExpressRoute .

VNet Service Endpoints

A Service Endpoint extends your VNet identity to an Azure service over an optimized route. The service still uses its public IP , but its firewall can be configured to accept traffic only from your chosen subnets. There is no per-hour or per-GB charge.

Private Link vs. Service Endpoints

  • Feature Private Link (private endpoint) Service Endpoint
  • Service IP Private IP in your VNet Service keeps its public IP
  • Internet exposure None through the endpoint Service remains internet-facing
  • On-premises access Yes, via VPN/ExpressRoute Not directly
  • Exfiltration protection Yes, scoped to one resource Limited
  • Granularity Per resource Per service type
  • Cost Per-hour + per-GB Free
  • Best for Production, strict isolation Cost-sensitive dev/test

Worked example: A healthcare app stores patient records in Azure SQL Database and must guarantee that the database is unreachable from the public internet. A Service Endpoint still leaves the database on a public IP (just firewalled), which auditors may reject. A private endpoint gives the database a private IP inside the VNet and is the correct, audit-friendly choice.

Azure Bastion

The classic way to administer a VM is to give it a public IP and open RDP (3389) or SSH (22). That is a large attack surface and a common breach vector. Azure Bastion is a fully managed, platform-as-a-service jump host that you deploy into the VNet.

How it works

Deploy Bastion into a dedicated subnet named AzureBastionSubnet (the name is required, minimum /26).

From the Azure portal, click Connect on any VM in that VNet or a peered VNet.

RDP/SSH runs over TLS inside your browser — no client install, no public IP on the VM.

Inbound 3389/22 stay closed to the internet; Bastion is hardened and patched by Microsoft.

  • Benefit Why it matters
  • No public IP on VMs Removes the most common internet attack surface
  • No open RDP/SSH ports NSGs can deny inbound management ports
  • TLS in the browser No VPN or local RDP/SSH client needed
  • Microsoft-managed hardening Protected against port-scanning and zero-days
  • Where these fit in defense in depth

These three features each remove a different attack surface and solve a different problem. Think of them as layers:

  • Concern Right feature
  • Stop a PaaS service from being internet-reachable at all Private Link / private endpoint
  • Allow a PaaS service but only from my VNet, at no cost Service Endpoint
  • Administer VMs without exposing 3389/22 to the internet Azure Bastion
  • Filter and inspect outbound traffic centrally Azure Firewall (managed, stateful)
  • Filter traffic at the subnet or NIC level Network Security Group (NSG) rules

Decision flow for a PaaS access question: If the requirement is "the service must have no public exposure" or "on-premises clients must reach it privately over ExpressRoute," the answer is Private Link . If the requirement is merely "lock the service down to our VNet" and cost is a concern, a Service Endpoint is sufficient and free. If the wording mentions data-exfiltration protection or a specific single resource, that strongly signals Private Link , because a private endpoint maps to one resource while a Service Endpoint opens the whole service type.

Bastion versus a public IP: Before Bastion, admins gave VMs public IPs and opened RDP or SSH, which exposed them to constant internet port scanning and brute-force attacks. Bastion lets you delete the public IP and keep inbound 3389/22 closed entirely; the only path in is an authenticated portal session over TLS. That dramatically shrinks the attack surface while keeping day-to-day administration simple.

On the Exam: "Reach a PaaS service over a private IP, no internet" = Private Link / private endpoint . "Restrict a service to my VNet but keep its public IP, no cost" = Service Endpoint . "RDP/SSH to a VM without a public IP or open ports" = Azure Bastion . "Data-exfiltration protection to one resource" = Private Link .