Global Secure Access client for Windows

Learn how to install the Global Secure Access client for Windows.


  • The Global Secure Access client is supported on 64-bit versions of Windows 11 or Windows 10.
    • Azure Virtual Desktop single-session is supported.
    • Azure Virtual Desktop multi-session isn't supported.
    • Windows 365 is supported.
  • Devices must be either Microsoft Entra joined or Microsoft Entra hybrid joined.
    • Microsoft Entra registered devices aren't supported.
  • Local administrator credentials are required for installation.
  • The product requires licensing. For details, see the licensing section of What is Global Secure Access. If needed, you can purchase licenses or get trial licenses.

Known limitations

  • Multiple user sessions on the same device, like those from a Remote Desktop Server (RDP), aren't supported.
  • Networks that use a captive portal, like some guest wireless network solutions, might cause the client connection to fail. As a workaround you can pause the Global Secure Access client.
  • Virtual machines where both the host and guest Operating Systems have the Global Secure Access client installed aren't supported. Individual virtual machines with the client installed are supported.
  • The service bypasses the traffic if the Global Secure Access client isn't able to connect to the service (for example due to an authorization or Conditional Access failure). Traffic is sent direct-and-local instead of being blocked. In this scenario, you can create a Conditional Access policy for the compliant network check, to block traffic if the client isn't able to connect to the service.
  • The Global Secure Access client on ARM64 architecture isn't yet supported. However, ARM64 is on the roadmap.

There are several other limitations based on the traffic forwarding profile in use:

Traffic forwarding profile Limitation
Microsoft traffic profile Tunneling IPv6 traffic isn't currently supported.
Microsoft traffic profile and Private access To tunnel network traffic based on rules of FQDNs (in the forwarding profile), Domain Name System (DNS) over HTTPS (Secure DNS) needs to be disabled.
Microsoft and Private access If the end-user device is configured to use a proxy server, locations that you wish to tunnel using the Global Secure Access client must be excluded from that configuration. For examples, see Proxy configuration example.
Private access Single label domains, like https://contosohome for private apps aren't supported. Instead use a fully qualified domain name (FQDN), like Administrators can also choose to append DNS suffixes via Windows.

Download the client

The most current version of the Global Secure Access client can be downloaded from the Microsoft Entra admin center.

  1. Sign in to the Microsoft Entra admin center as a Global Secure Access Administrator.

  2. Browse to Global Secure Access > Connect > Client download.

  3. Select Download Client.

    Screenshot of the download Windows client button.

Install the client

Organizations can install the client interactively, silently with the /quiet switch, or use mobile device management platforms like Microsoft Intune to deploy it to their devices.

  1. Copy the Global Secure Access client setup file to your client machine.

  2. Run the GlobalSecureAccessClient.exe setup file. Accept the software license terms.

  3. The client is installed and users are prompted to sign in with their Microsoft Entra credentials.

    Screenshot showing the sign-in box appears after client installation completes.

  4. Users sign in and the connection icon turns green. Double-clicking on the connection icon opens a notification with client information showing a connected state.

    Screenshot showing the client is connected.


To troubleshoot the Global Secure Access client, right-click the client icon in the taskbar.

Screenshot showing the context menu of the Global Secure Access client.

  • Login as different user
    • Forces sign-in screen to change user or reauthenticate the existing user.
  • Pause
    • This option can be used to temporarily disable traffic tunneling. As this client is part of your organization's security posture we recommend leaving it running always.
    • This option stops the Windows services related to client. When these services are stopped, traffic is no longer tunneled from the client machine to the cloud service. Network traffic behaves as if the client isn't installed while the client is paused. If the client machine is restarted, the services automatically restart with it.
  • Resume
    • This option starts the underlying services related to the Global Secure Access client. This option would be used to resume after temporarily pausing the client for troubleshooting. Traffic resumes tunneling from the client to the cloud service.
  • Restart
    • This option stops and starts the Windows services related to client.
  • Collect logs
    • Collect logs for support and further troubleshooting. These logs are collected and stored in C:\Program Files\Global Secure Access Client\Logs by default.
      • These logs include information about the client machine, the related event logs for the services, and registry values including the traffic forwarding profiles applied.
  • Client Checker
    • Runs a script to test client components ensuring the client is configured and working as expected.
  • Connection Diagnostics provides a live display of client status and connections tunneled by the client to the Global Secure Access service
    • Summary tab shows general information about the client configuration including: policy version in use, last policy update date and time, and the ID of the tenant the client is configured to work with.
      • Hostname acquisition state changes to green when new traffic acquired by FQDN is tunneled successfully based on a match of the destination FQDN in a traffic forwarding profile.
    • Flows show a live list of connections initiated by the end-user device and tunneled by the client to the Global Secure Access edge. Each connection is new row.
      • Timestamp is the time when the connection was first established.
      • Fully Qualified Domain Name (FQDN) of the destination of the connection. If the decision to tunnel the connection was made based on an IP rule in the forwarding policy not by an FQDN rule, the FQDN column shows N/A.
      • Source port of the end-user device for this connection.
      • Destination IP is the destination of the connection.
      • Protocol only TCP is supported currently.
      • Process name that initiated the connection.
      • Flow active provides a status of whether the connection is still open.
      • Sent data provides the number of bytes sent by the end-user device over the connection.
      • Received data provides the number of bytes received by the end-user device over the connection.
      • Correlation ID is provided to each connection tunneled by the client. This ID allows tracing of the connection in the client logs. The client logs consist of event viewer, event trace (ETL), and the Global Secure Access traffic logs (preview).
      • Flow ID is the internal ID of the connection used by the client shown in the ETL file.
      • Channel name identifies the traffic forwarding profile to which the connection is tunneled. This decision is taken according to the rules in the forwarding profile.
    • HostNameAcquisition provides a list of hostnames that the client acquired based on the FQDN rules in the forwarding profile. Each hostname is shown in a new row. Future acquisition of the same hostname creates another row if DNS resolves the hostname (FQDN) to a different IP address.
      • Timestamp is the time when the connection was first established.
      • FQDN that is resolved.
      • Generated IP address is an IP address generated by the client for internal purposes. This IP is shown in flows tab for connections that are established to the relative FQDN.
      • Original IP address is the first IPv4 address in the DNS response when querying the FQDN. If the DNS server that the end-user device points to doesn’t return an IPv4 address for the query, the original IP address shows
    • Services shows the status of the Windows services related to the Global Secure Access client. Services that are started have a green status icon, services that are stopped show a red status icon. All three Windows services must be started for the client to function.
    • Channels list the traffic forwarding profiles assigned to the client and the state of the connection to the Global Secure Access edge.

Event logs

Event logs related to the Global Secure Access client can be found in the Event Viewer under Applications and Services/Microsoft/Windows/Global Secure Access Client/Operational. These events provide useful detail regarding the state, policies, and connections made by the client.

Disable IPv6 and secure DNS

If you need assistance disabling IPv6 or secure DNS on Windows devices, the following script provides assistance.

function CreateIfNotExists
    if (-NOT (Test-Path $Path))
        New-Item -Path $Path -Force | Out-Null

$disableBuiltInDNS = 0x00

# Prefer IPv4 over IPv6 with 0x20, disable  IPv6 with 0xff, revert to default with 0x00. 
# This change takes effect after reboot. 
$setIpv6Value = 0x20
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" -Name "DisabledComponents" -Type DWord -Value $setIpv6Value

# This section disables browser based secure DNS lookup.
# For the Microsoft Edge browser.
CreateIfNotExists "HKLM:\SOFTWARE\Policies\Microsoft"
CreateIfNotExists "HKLM:\SOFTWARE\Policies\Microsoft\Edge"

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "DnsOverHttpsMode" -Value "off"

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "BuiltInDnsClientEnabled" -Type DWord -Value $disableBuiltInDNS

# For the Google Chrome browser.

CreateIfNotExists "HKLM:\SOFTWARE\Policies\Google"
CreateIfNotExists "HKLM:\SOFTWARE\Policies\Google\Chrome"

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome" -Name "DnsOverHttpsMode" -Value "off"

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome" -Name "BuiltInDnsClientEnabled" -Type DWord -Value $disableBuiltInDNS

Proxy configuration example

Example proxy PAC file containing exclusions:

function FindProxyForURL(url, host) {  // basic function; do not change
   if (isPlainHostName(host) ||
      dnsDomainIs(host, "") || //tunneled
      dnsDomainIs(host, ""))  // tunneled
      return "DIRECT";                     // If true, sets "DIRECT" connection
      else                                 // for all other destinations  
      return "PROXY";  // transfer the traffic to the proxy. 

Organizations must then create a system variable named grpc_proxy with a value like that matches your proxy server's configuration on end-user machines to allow the Global Secure Access client services to use the proxy.

Next steps

The next step for getting started with Microsoft Entra Internet Access is to enable universal tenant restrictions.