Study guide
8.1 Microsoft Entra Private Access
Microsoft Certified: Cloud and AI Security Engineer Associate SC-500
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy
2 Microsoft Entra ID Secure Access
2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities
3 Azure Key Vault Secrets and Keys
3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault
4 Governance, Policy & RBAC
4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security
5 Secure Storage Accounts
5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage
6 Secure Databases
6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases
7 Network Security Groups & Virtual Network Manager
7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security
8 Private Access, Private Link & Azure Firewall
8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules
9 Security for AI Workloads
9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway
10 Secure Servers and Virtual Machines
10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration
11 Application Platform Security
11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection
12 Defender for Cloud Security Posture
12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM
13 Microsoft Sentinel Activity and Event Collection
13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks
14 Microsoft Security Copilot & Final Review
14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy
8.1 Microsoft Entra Private Access
Key Takeaways Explain This Topic AI
Microsoft Entra Private Access is Microsoft’s Zero Trust Network Access (ZTNA) product under Global Secure Access; it provides identity-aware, per-app access to private resources and is a modern alternative to full-tunnel corporate VPN.
Quick Access groups broad private FQDNs/IPs while Global Secure Access apps enable per-app segmentation with different Conditional Access policies—both create enterprise applications you assign users to.
Private network connectors (in connector groups) broker traffic to on-premises or private cloud resources; deploy at least two healthy connectors per group for high availability.
Conditional Access policies applied to Private Access apps enforce MFA, device compliance, and risk controls before users reach private TCP/UDP apps—this is the Zero Trust differentiator versus network-only VPN.
Enable the Private Access traffic forwarding profile and install the Global Secure Access client so enrolled devices can reach published private segments without a traditional VPN session.
Last updated: July 2026
Why Private Access Matters on SC-500
Under Secure storage, databases, and networking (25–30%) , Microsoft explicitly measures Implement and configure Microsoft Entra Private Access . SC-500 expects you to place Private Access correctly in a Zero Trust design: identity-aware, per-app access to private resources—not a traditional full-tunnel VPN that dumps remote users onto the entire corporate network.
Microsoft Entra Private Access is part of Microsoft’s Security Service Edge (SSE) solution. In the admin center and docs you will see the umbrella name Global Secure Access , which unifies:
- Product Role
- Microsoft Entra Private Access Zero Trust Network Access (ZTNA) to private/corporate apps and resources
- Microsoft Entra Internet Access Secure internet and SaaS egress (web filtering, threat protection)
Microsoft Entra Internet Access for Microsoft services Optimized, identity-aware path for Microsoft 365 / Microsoft traffic
Private Access is the piece that modernizes remote and hybrid access to internal apps —on-premises, hybrid, or private IP resources in cloud VNets—using Entra identity and Conditional Access instead of flat VPN connectivity.
Global Secure Access Overview
Global Secure Access is the control plane in the Microsoft Entra admin center where you:
Deploy and manage private network connectors (broker traffic to internal resources).
Define application segments (FQDNs, IPs, ports, protocols) that represent private resources.
Create enterprise applications that act as policy containers (Quick Access or per-app Global Secure Access apps).
Assign users and groups to those apps.
Enable the Private Access traffic forwarding profile so enrolled clients send private-app traffic through the service.
Install the Global Secure Access client on user devices so connectivity is seamless without a classic VPN client stack.
Private Access builds on the lineage of Microsoft Entra application proxy connectors and extends them: you are not limited to HTTP/S reverse-proxy web apps. You can publish any private resource, port, and protocol (TCP and UDP) that the connector can reach on the private network.
Zero Trust Network Access vs Traditional VPN
Dimension Traditional corporate VPN Microsoft Entra Private Access (ZTNA)
Access model Often full or broad network placement after tunnel up Per-app / segmented access to declared FQDNs, IPs, ports
Trust assumption “Inside the network” is trusted Never trust, always verify with Entra identity + Conditional Access
Lateral movement risk High if VPN grants broad subnet reach Reduced via macro- and micro-segmentation of app segments
Policy engine Network ACLs, split tunnel configs, gateway groups Conditional Access , MFA, device compliance, risk, PIM patterns
Client experience VPN connect/disconnect, often noisy Global Secure Access client steers private traffic quietly
Exam positioning Legacy remote access Preferred modern replacement for VPN-style private app access
Exam phrasing: When a scenario says remote users must reach internal apps without a VPN , with per-app Conditional Access and least privilege, choose Microsoft Entra Private Access / Global Secure Access —not “open RDP to the internet” or “always-on full-tunnel VPN only.”
- ZTNA still needs healthy connectors and correct DNS/app segment design. It is not “security by renaming VPN.”
- Quick Access vs Per-App Access
Private Access offers two complementary configuration patterns. Both create an enterprise application in Entra that you can assign users to and protect with Conditional Access.
Quick Access
Quick Access is the primary bag of private destinations you always want tunneled through the service—bulk FQDNs, IP addresses, and IP ranges that represent core private network resources. Use it when you are modernizing off VPN and need a broad private-access path quickly.
Security guidance from Microsoft is explicit: bind Quick Access to Conditional Access . If Quick Access exists without CA, a stolen password can become broad private-network reach. Treat Quick Access as a high-value app that must require MFA (often phishing-resistant), compliant devices, and risk-based controls.
Global Secure Access app (per-app access)
Create separate Global Secure Access apps when you need:
Different Conditional Access policies for a subset of resources (for example, domain controllers vs general file shares).
Time-bound or project-scoped private apps.
Stronger segmentation for privileged destinations (pair with PIM-eligible users and stronger auth contexts).
Pattern Granularity Typical CA story
Quick Access Broad private resource set One strong baseline CA policy for “all private network via Quick Access”
Per-app GSA app Narrow FQDN/IP/port segments Tighter CA (phishing-resistant MFA, compliant + privileged access workstation)
Both still use connectors to reach the private network; the difference is policy and assignment boundaries.
Connectors and Connector Groups
Private network connectors (the evolved App Proxy connector model) run on Windows servers in networks that can reach the private apps (on-premises, Azure VNet, multicloud). They broker connections from the Global Secure Access service to internal resources.
Connector groups
A connector group is the unit that apps are associated with for path selection.
Each group should have at least two healthy, active connectors for high availability. A single connector is a single point of failure for every app assigned to that group.
Keep connectors updated ; older connector versions can block Private Access capabilities.
Scale out connectors when concurrent private sessions or new app segments grow.
Exam trap: Connectors must be able to reach the private resource IPs/FQDNs on the internal network. Publishing an FQDN in Quick Access does nothing if DNS inside the connector network cannot resolve it or if firewalls block the path from connector host to app.
Relationship to Conditional Access
Private Access is deliberately identity-first:
User signs in with Microsoft Entra ID.
User (or device with GSA client) attempts a private resource that matches a published segment.
Access is mediated through the enterprise app (Quick Access or per-app).
Conditional Access evaluates grant controls (MFA, device compliance, location, sign-in risk, authentication strength, session controls).
Only after CA succeeds does traffic flow via connectors to the private resource.
This is why Private Access is stronger than IP-only VPN ACLs for Zero Trust: the same risk engine that protects SaaS can protect internal RDP, SMB, SQL, custom TCP services, and more.
Deployment checklist (exam + production)
Deploy connector group with ≥2 healthy connectors near the apps.
Configure Quick Access and/or per-app segments (FQDN/IP/port/protocol).
Assign users/groups to the enterprise apps (no assignment ⇒ no least-privilege CA path).
Create Conditional Access policies targeting those apps (MFA minimum; stronger for privileged apps).
Enable Private Access traffic forwarding profile .
Deploy Global Secure Access client to managed devices (waves of pilot users).
Add private DNS suffixes where needed so short names and internal zones resolve correctly through the service.
Pilot, monitor, then expand—do not flip the entire company off VPN on day one without support readiness.
How It Differs from Adjacent Controls
Control Relationship to Private Access
Azure VPN Gateway / Virtual WAN VPN Site or point-to-site network connectivity; still useful for some scenarios, but not identity-per-app ZTNA
Azure Bastion / JIT Admin access to Azure VMs; different problem than employee access to many private apps
Private Endpoints / Private Link Secure Azure PaaS (or custom services) from VNets; Private Access secures user-to-private-app paths with Entra
Application Proxy alone Web-oriented reverse proxy; Private Access generalizes beyond classic web publish
SC-500 often stacks them: Private Link locks storage/SQL to private IPs; Private Access lets remote identities reach internal apps with CA; Azure Firewall inspects hub egress. Know which layer answers which requirement.
- SC-500 Exam Traps (Private Access)
- Private Access replaces or reduces VPN for app access—it is not “just another VPN brand.”
Quick Access without Conditional Access is a documented anti-pattern.
One connector per group is a resilience fail.
Assigning users/groups is required for Zero Trust enforcement—not optional hygiene.
Connectors extend App Proxy concepts to any private port/protocol, not only HTTP.
GSA client + traffic forwarding profile are part of the access path, not optional cosmetics.
Scenario Walkthroughs
Scenario A: Remote finance users need SAP GUI (non-HTTP) without full VPN.
Answer path: Entra Private Access app segment for SAP host/port; connector group in datacenter; CA requiring MFA + compliant device; GSA client.
Scenario B: Privileged admins need domain controller ports; regular users must not.
Answer path: Separate per-app GSA application for DC segments; assign only PAM/admin groups; phishing-resistant MFA Conditional Access; keep Quick Access free of DC ranges.
Scenario C: Leadership says “we already have always-on VPN.” Requirement is Zero Trust microsegmentation.
Answer path: Migrate to Private Access segments + CA; shrink VPN surface; do not rely on flat VPN alone.