Learn what’s new and exciting in the Cloud Services plugin versions.
The following table describes the new features introduced
in the Cloud Services plugin version 1.2.0. For additional information
on how to use the new features in this release, refer to the Prisma Access Administrator’s
Gateway Selection Improvements
To allow mobile users to use the best gateway for
your organization, the following gateway improvements have been
Mobile users now automatically connect
more reliably to a Prisma Access gateway that is inside the country
from which they are connecting.
Mobile users can manually select a gateway (either a gateway
in Prisma Access or an on-premise gateway) using the GlobalProtect
app on their endpoint.
button and hover over any of the circled locations on the map to
get a detailed view of the number of service connections, remote
network tunnels, or remote users that are configured and their status.
shows the current data retention settings and log quotas for Infrastructure
and Audit Logs, Detailed Logs, and Summary Logs.
has been divided into four areas with radio buttons that allow you
to see the network details divided by
Internal DNS domains for mobile users
increased to 1,024
Prisma Access can now support up to 1,024 internal
FQDNs of all Prisma Access gateways now
You can now view the full FQDNs of all gateways
that are available in Prisma Access. To view the FQDNs, select
radio button. The
FQDNs display in the
gateways replace the primary and secondary gateways.
paloalto-shared-services App-ID released
To make sure that Panorama can communicate
with Prisma Access and Cortex Data Lake, configure internet gateway
firewall security policies to allow the App-ID
in addition to the App-ID
as part of content version 8067, and you can review the Customer
Resources article Palo Alto Shared Services App-ID for
more information. Before the release of this App-ID, administrators
needed to add a security policy that contained the
on the internet gateway
firewall to allow communication between the services, which was
less secure than using the new App-ID.