Configure up to 40 domain name exclusions when Enforce GlobalProtect for Network Access
is enabled. Improve user experience by allowing access to specific resources when
GlobalProtect is disconnected.
Software Support: Starting with GlobalProtect™
app 5.2 with Content Release version 8284-6139 or later.
OS
Support: Windows and macOS running macOS Catalina 10.15.4 or
later
You can now configure exclusions for specific fully qualified domain names when the Enforce
GlobalProtect for Network Access feature is enabled. With the Allow
traffic to specified FQDN when Enforce GlobalProtect Connection for Network
Access is enabled and GlobalProtect Connection is not established
option that is available as an app setting in the App
Configurations area of your GlobalProtect portal, you can now
specify the fully qualified domain names for which you allow access when you enforce
GlobalProtect connections for network access. You can configure up to 40 fully
qualified domain names for which you want to allow access when you enforce
GlobalProtect connections for network access and GlobalProtect cannot establish a
connection. By configuring FQDN exclusions, you can improve the user experience by
allowing end users to access specific resources when GlobalProtect is disconnected.
For example, the endpoint can communicate with a cloud-hosted identity provider
(ldP) for authentication purposes or a remote device management server even when the
Enforce GlobalProtect for Network Access feature is enabled.
Due to a recent change in macOS, enforcing
GlobalProtect connections with FQDN exclusions for multiple network extensions being
loaded at a time does not work in certain situations, such as in environments where
DnsClient.Net, GlobalProtect with the Allow traffic to specified FQDN
when Enforce GlobalProtect Connection for Network Access is enabled and
GlobalProtect Connection is not established option enabled, and
Cortex XDR are running.