Prisma Access
Changes to Default Behavior for Prisma Access 6.1 and 6.1.1
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
- 6.1 Preferred and Innovation
- 6.0 Preferred and Innovation
- 5.2 Preferred and Innovation
- 5.1 Preferred and Innovation
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
-
-
- 4.0 & Later
- Prisma Access China
-
-
Changes to Default Behavior for Prisma Access 6.1 and 6.1.1
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
Changes to Default Behavior for Prisma Access 6.1.1
The following table details the changes in default behavior for Prisma Access version 6.1.1.
| Component | Change |
|---|---|
| Potential IP Address Changes During Location Reboarding |
Starting March 20, 2026, if you remove (deboard)
and then re-add (onboard) the same location, Prisma Access
might assign a different public IP address to that
location. This behavior applies to the following location types
in a subset of Prisma Access locations:
Affected deployments—This potential IP address
change affects Prisma Access deployments where:
Affected locations—This change only affects the following
locations:
Required actions:
For mobile user locations: After deboarding the
new location, we recommend that you run the API with an
action_type of
preallocate or use the IP Capacity Planning
feature to check the IP addresses for your locations against
your existing allow lists.
For remote network, service connection, or explicit
proxy locations: Verify the IP address by running the
API script or
navigating to the Strata Cloud Manager or Panorama UI, locating
the reboarded location, and verifying the assigned IP address
against your existing allow lists.
|
Changes to Default Behavior for Prisma Access 6.1
The following table details the changes in default behavior for Prisma Access version 6.1.
| Component | Change |
|---|---|
| Locations added to New and Existing Prisma Access Deployments | The following locations Prisma Access are supported starting
with Prisma Access 6.1. New deployments have these
locations added automatically; for existing deployments, each out to
your Palo Alto Networks account representative to add them, who will
contact the Site Reliability Engineering (SRE) team and submit a
request. The following functionality is not supported for
these locations: If you require additional functionality, we
recommend that you onboard alternate locations.
|
| Location Groups Changing for the Mexico Central and Mexico West Mobile User Locations |
The Mexico Central and Mexico West locations are
changing their IP pool location group starting with the Prisma
Access 6.1 release. If you have enabled the Prisma AccessMexico Central or Mexico West mobile user locations, and have
created mobile user IP address
pools based on location groups, be
aware that the location groups have changed:
To align with the updated Private IP allocation
structure, if you are affected, you must perform the following
steps immediately:
|