Entra Global Secure Access Compliant Network Check and Confidential Computing Sovereignty
Halting stolen cookie/token replay across untrusted external networks using Global Secure Access Compliant Network Conditional Access combined with hardware-encrypted Azure Confidential Computing.
Executive Summary and Network Access Context
Static corporate allowlist IPs fail cleanly whenever attackers spin up cloud relays inside shared ISPs, while browser-level session cookies still occasionally leave endpoints exposed outside desktop token-binding coverage. Pairing Entra Global Secure Access Compliant Network Check (All Compliant Network Locations)—verifying cryptographically that traffic traverses your authorized Microsoft SSE tunnel—with Azure Confidential Computing (AMD SEV-SNP / Intel TDX) encryption-in-use shields data continuously from browser ingress through RAM.
From an architectural evolution standpoint, this foundational design connects directly to modern platform controls. Uniting 2023’s Global Secure Access SSE and 2024’s Token Protection into unified hardware-plus-network isolation directly reinforces Microsoft Sovereign Cloud Digital Sovereignty.
Trust Boundaries, Traffic Flows, and Design Principles
All Compliant Network Locationsevaluates cryptographic SSE tunnel provenance directly inside Conditional Access, blocking stolen session cookies replayed from rogue external machines.- Maintains full end-to-end fidelity with
Source IP Restorationso SigninLogs and SIEM analytics reflect real originating user endpoints. Azure Confidential Computing (DCasv5/ECasv5 SEV-SNP & Confidential AKS)enforces hardware-rooted Trusted Execution Environments (TEE) keeping AI inference data encrypted inside CPU RAM away from cloud operators or hypervisors.- Management and application ingress must avoid raw public ports (
RDP 3389,SSH 22) by routing throughPrivate Endpoints,Azure Bastion, orSSEtunnels backed by symmetricUDRegress inspection.
Prerequisites, Network Dependencies, and RBAC Requirements
- Licensing: Compliant Network signaling operates atop Global Secure Access for Microsoft 365 included in Entra ID P1 (M365 E3/E5); Confidential VMs/AKS utilize standard Azure Confidential VM SKUs.
- Network & RBAC: Enable Microsoft 365 Forwarding Profile + Compliant Network Signaling under
Global Secure Access Administratorpaired withConditional Access Administrator. - App Exceptions: Explicitly partition cloud-to-cloud APIs and BYOD contractor flows away from workstation-only Compliant Network block rules.
Technical Verification, Access Controls, and Telemetry
PowerShell Network Posture and Configuration Check
Auditing Compliant Network Conditional Access rules via Microsoft Graph and verifying Confidential Compute VMs via Az PowerShell:
- Execution Environment and Prerequisites: Requires Microsoft.Graph, Az.*.
- Least Privilege and Operation Separation: Run with scoped Azure Reader (audit) / Contributor (state changes) privileges. All statements above are **read-only (
Get-*/Test-*/Search-*)** verification checks making no direct configuration edits; still validate module/network prerequisites in a test cohort first. - Security Control Mapped and Boundary Note: Verifies active policy state and guards against silent drift or mis-scoped rollouts without blind production changes.
# 1. Query Conditional Access policies leveraging AllCompliantNetworkLocations
Connect-MgGraph -Scopes "Policy.Read.All"
Get-MgIdentityConditionalAccessPolicy |
Where-Object { $_.Conditions.Locations.ExcludeLocations -contains "AllCompliantNetworkLocations" -or $_.DisplayName -like "*Compliant*" } |
Select-Object DisplayName, State
# 2. Verify Azure Confidential Computing VMs (DCasv5 / ECasv5 SEV-SNP SecurityType)
Connect-AzAccount
Get-AzVM | Where-Object { $_.HardwareProfile.VmSize -match "DC.*v5|EC.*v5" } |
Select-Object Name, ResourceGroupName, @{N="VmSize";E={$_.HardwareProfile.VmSize}}, @{N="SecurityType";E={$_.SecurityProfile.SecurityType}}Network Traffic Telemetry and KQL Verification Query
KQL query inspecting Global Secure Access signal adoption (IsThroughGlobalSecureAccess) and blocked off-network attempts:
// Execution Scope: Read-only hunting/audit query (Log Analytics Reader / Security Reader)
// Data Source: Microsoft Entra ID Diagnostic Settings -> Log Analytics / Microsoft Sentinel (SigninLogs / AuditLogs)
SigninLogs
| where TimeGenerated > ago(14d)
| project TimeGenerated, UserPrincipalName, AppDisplayName, IPAddress, IsThroughGlobalSecureAccess, ResultType, ConditionalAccessStatus
| summarize Total = count(), ViaGSA = countif(IsThroughGlobalSecureAccess == true), BlockedOutsideNetwork = countif(IsThroughGlobalSecureAccess == false and ResultType == 53003) by AppDisplayName
| order by Total descCritical Architectural Assessment, Outage Risks, and Rollback Strategy
- Forgetting to Enable GSA Global Secure Access Signaling & Source IP Restoration: Conditional Access cannot detect Compliant Network status until GSA Signaling is explicitly toggled inside Session Management.
- Locking Out Unmanaged Contractor Web Sessions Unintentionally: Scope strict Compliant Network enforcement cleanly around corporate-managed device groups or paired Intune App Protection tiers.
- Risks Mitigated vs. Residual Limitations:
Private Endpoints,Azure Bastion,Azure Firewall, andEntra Global Secure Accesseliminate direct publicRDP/SSHexposure, lateral L3 VPN traversal, and unrestricted internet egress; they do not mitigate application-layer exploits (SQLi,SSRF) traversing authorized tunnels, compromised local endpoint binaries, or overly permissive spoke-to-spokeNSGrules. - New Dependencies and Production Failure Modes: Connectivity relies on consistent
Private DNS Zonelinking, symmetricUDRpaths, and healthy endpoint SSE clients/connectors. Misconfigured0.0.0.0/0routing loops or missing private DNS zones instantly sever VM and hybrid application traffic in production. - Rollback and Pilot Validation Procedure: Validate firewall rules,
NSGpriorities, andSSEforwarding profiles against a canary VNet or pilot cohort first; maintain scriptedAz.NetworkUDR/NSGsnapshots and SSE bypass toggles to restore routing swiftly.
Verified Primary Sources & Open-Source Repositories
This architectural guide was cross-corroborated against the official advisories, Microsoft Learn docs, and open-source PowerShell / KQL repositories below.
Multi-Channel Distribution Summary (X & LinkedIn Draft)
Toggle X (Twitter) & LinkedIn sharing drafts
Multi-Channel Distribution Summary (X & LinkedIn Draft)
Toggle X (Twitter) & LinkedIn sharing draftsClosing stolen cookie replay with GSA Compliant Network Checks and memory-encrypted Azure Confidential Computing. #GlobalSecureAccess #ConfidentialCompute
Network-to-Silicon Sovereignty: Enforcing All Compliant Network Locations in Conditional Access alongside AMD SEV-SNP hardware memory encryption.