Focus

Changes to Default Behavior

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Activation & Onboarding
Administration
Version
- Prisma Access China
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Integrations
Incidents & Alerts
Release Notes
Version
- 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
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred

Features in Prisma Access 3.1

Upgrade the Cloud Services Plugin

Changes to Default Behavior

The following tables detail the changes in default behavior for the Cloud Services Plugin version 3.1 Preferred and Innovation.

Changes to Default Behavior—Prisma Access 3.1 Preferred

The following table details the changes in default behavior for the Cloud Services Plugin version 3.1 Preferred and Innovation.

Component	Change
QoS Profile Guidelines for Remote Networks that Migrate to an Aggregate Bandwidth Deployment	If you have implemented QoS policies and profiles in your Prisma Access remote network deployment, and you migrate from allocating bandwidth by location to allocating bandwidth by compute location (aggregate bandwidth), use the following guidelines for your QoS profiles. Because there can be multiple locations in a single compute location and all the locations share the same bandwidth, Palo Alto Networks recommends that you change the QoS profiles that use a Class Bandwidth Type of Mbps to a Class Bandwidth Type of Percentage. If you onboard a new location in a compute location that already have QoS profiles with a Class Bandwidth Type of Mbps, you can only create QoS profiles for the new locations that have a Class Bandwidth Type of Mbps until you change all the QoS profiles to a type of Percentage. You cannot mix class bandwidth types in a compute location. Any new compute locations you add after migration will only support a Class Bandwidth Type of Percentage.
Renamed Service Connections	If you have onboarded service connections in any of the following locations, those locations will change names to support cloud provider redundancy for service connections after you upgrade the Cloud Services plugin to 3.1. The service connection functionality is not affected and your service IP addresses do not change, only the location names change in the UI: Bahrain—Renamed to Bahrain PA-A France North—Renamed to France North PA-A Ireland—Renamed to Ireland PA-A South Africa West—Renamed to South Africa West PA-A South Korea—Renamed to South Korea PA-A

Component

Change

QoS Profile Guidelines for Remote Networks that Migrate to an Aggregate Bandwidth Deployment

If you have implemented QoS policies and profiles in your Prisma Access remote network deployment, and you migrate from allocating bandwidth by location to allocating bandwidth by compute location (aggregate bandwidth), use the following guidelines for your QoS profiles.

Because there can be multiple locations in a single compute location and all the locations share the same bandwidth, Palo Alto Networks recommends that you change the QoS profiles that use a Class Bandwidth Type of Mbps to a Class Bandwidth Type of Percentage.
If you onboard a new location in a compute location that already have QoS profiles with a Class Bandwidth Type of Mbps, you can only create QoS profiles for the new locations that have a Class Bandwidth Type of Mbps until you change all the QoS profiles to a type of Percentage. You cannot mix class bandwidth types in a compute location.
Any new compute locations you add after migration will only support a Class Bandwidth Type of Percentage.

Renamed Service Connections

If you have onboarded service connections in any of the following locations, those locations will change names to support cloud provider redundancy for service connections after you upgrade the Cloud Services plugin to 3.1. The service connection functionality is not affected and your service IP addresses do not change, only the location names change in the UI:

Bahrain—Renamed to Bahrain PA-A
France North—Renamed to France North PA-A
Ireland—Renamed to Ireland PA-A
South Africa West—Renamed to South Africa West PA-A
South Korea—Renamed to South Korea PA-A

Changes to Default Behavior—Prisma Access 3.1 Innovation

The following table details the changes in default behavior for the Cloud Services Plugin version 3.1 Preferred and Innovation.

Component	Change
Renamed Service Connections	If you have onboarded service connections in any of the following locations, those locations will change names to support cloud provider redundancy for service connections after you upgrade the Cloud Services plugin to 3.1. The service connection functionality is not affected and your service IP addresses do not change, only the location names change in the UI: Bahrain—Renamed to Bahrain PA-A France North—Renamed to France North PA-A Ireland—Renamed to Ireland PA-A South Africa West—Renamed to South Africa West PA-A South Korea—Renamed to South Korea PA-A For the new service location names to display, you must perform a Commit and Push operation after you upgrade your plugin to 3.1.

Component

Change

Renamed Service Connections

Bahrain—Renamed to Bahrain PA-A
France North—Renamed to France North PA-A
Ireland—Renamed to Ireland PA-A
South Africa West—Renamed to South Africa West PA-A
South Korea—Renamed to South Korea PA-A

For the new service location names to display, you must perform a Commit and Push operation after you upgrade your plugin to 3.1.

Features in Prisma Access 3.1

Upgrade the Cloud Services Plugin

Prisma Access Docs

Changes to Default Behavior

Prisma Access Docs

Changes to Default Behavior

Changes to Default Behavior—Prisma Access 3.1 Preferred

Changes to Default Behavior—Prisma Access 3.1 Innovation

Activation & Onboarding

SASE

Cloud-Delivered Security Services

Network Security

Endpoints

Visibility & Monitoring

Best Practices

Experts Corner