azureblog.co.uk
← SC-500 study plan
SC-500 · Secure storage, databases, and networking

Secure Azure network services

NSGs and ASGs, Azure Virtual Network Manager admin rules, Virtual WAN security, VPN security, Entra Private Access, private endpoints, Private Link services, Azure Firewall and Network Watcher diagnostics.

  • 24 min
  • 9 concepts
  • Try it yourself
  • 4-question check

Learn

Network security in Azure is layered: segment with NSGs, enforce organisation-wide rules centrally, inspect traffic at a firewall, keep PaaS off the internet with Private Link, and replace broad VPN access with identity-aware access.

  1. 1

    Implement and manage network security groups (NSGs) and application security groups (ASGs)

    Use NSGs on subnets (and NICs where needed) with deny-by-default thinking: rules by priority, service tags (Internet, VirtualNetwork, Storage.UKSouth) and ASGs to group VMs by role. Enable VNet flow logs (NSG flow logs are being retired) with Traffic Analytics to see what's actually flowing.

    Remember: VNet flow logs replace NSG flow logs.

  2. 2

    Implement and configure network access policies by using Azure Virtual Network Manager

    Security admin rules in Azure Virtual Network Manager apply across many VNets in management groups or subscriptions and are evaluated before NSGs. Actions: Allow (NSG still evaluates), Deny (NSG can't override) and Always allow (bypasses NSG). Use them to block high-risk ports organisation-wide.

    Remember: Admin rules beat NSGs: Deny can't be overridden locally.

  3. 3

    Configure security for an Azure Virtual WAN

    A secured virtual hub adds Azure Firewall (or a supported third-party security provider) to a Virtual WAN hub, managed by Azure Firewall Manager policy. Routing intent sends internet and private (branch, VNet-to-VNet) traffic through the hub firewall.

    Remember: Secured hub + routing intent = inspect everything.

  4. 4

    Implement and configure security for virtual private network (VPN) connections

    Site-to-site: use custom IPsec/IKE policies with strong algorithms (for example AES256, SHA256, DH group 14+), BGP where needed, and active-active gateways. Point-to-site: use Microsoft Entra ID authentication (with Conditional Access and MFA) or certificates, OpenVPN or IKEv2, and limit address pools.

    Remember: P2S with Entra auth gets Conditional Access and MFA.

  5. 5

    Implement and configure Microsoft Entra Private Access

    Entra Private Access gives identity-centric, per-app access to private resources through the Global Secure Access client and private network connectors, with Conditional Access (MFA, compliant device) on each app, instead of network-wide VPN access.

    Remember: Zero Trust replacement for broad VPN access.

  6. 6

    Configure Azure private endpoints to secure access to Azure platform as a service (PaaS) resources

    A private endpoint gives a PaaS resource a private IP in your VNet via Private Link. Configure the matching private DNS zone (for example privatelink.blob.core.windows.net) linked to VNets or used by DNS forwarders, then disable public network access. Use network policies on the subnet so NSGs and UDRs apply to private endpoints.

    Remember: Private endpoint + private DNS zone + public access off.

  7. 7

    Configure Azure Private Link services to secure access to network resources

    A Private Link service exposes your own service, behind a Standard internal load balancer, to consumers in other VNets or tenants through their private endpoints, with no peering and no public exposure. You approve or reject connection requests and can use visibility and auto-approval lists.

    Remember: Publish your own service privately: Private Link service.

  8. 8

    Implement and configure Azure Firewall

    Tiers: Basic, Standard (threat intelligence, FQDN filtering, DNS proxy) and Premium (TLS inspection, IDPS, URL filtering, web categories). Manage with Firewall Policy (rule collection groups: DNAT, network, application). Force traffic through it with UDRs, and send logs to Log Analytics (resource-specific tables).

    Remember: TLS inspection and IDPS: Premium.

  9. 9

    Evaluate effective security rules by using Azure Network Watcher diagnostics

    Use effective security rules on a NIC to see the combined NSG and admin rules, IP flow verify to test a packet, NSG diagnostics to see which rules apply along a path, next hop and effective routes to check routing through the firewall, and connection troubleshoot.

    Remember: Which rule allowed it? Effective security rules or NSG diagnostics.

Rule evaluation order for inbound traffic

  1. Network Manager admin rulesAllow, Deny or Always allow.
  2. Subnet NSGEvaluated if admin rules allow.
  3. NIC NSGMust also allow.
  4. WorkloadTraffic reaches the VM.

Try it

Test traffic against an NSG and see which rule decides.

This interactive part needs JavaScript.

In the portal

  • Network ManagerAzure portal: Network managers > your manager > Settings > Security admin configurations
  • Firewall PolicyAzure portal: Firewall Policies > Create
  • Private Link CenterAzure portal: Private Link > Private endpoints
  • NSG diagnosticsAzure portal: Network Watcher > Network diagnostic tools > NSG diagnostics

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your SC-500 study plan.

  1. An AVNM security admin rule denies port 3389. Can a local NSG allow it?

  2. Which Azure Firewall tier includes TLS inspection?

  3. How do you expose your own service privately to another tenant?

  4. Which P2S authentication enables Conditional Access?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.