Upgrade Considerations for Panorama Managed Prisma Access
Focus
Focus
Prisma Access

Upgrade Considerations for Panorama Managed Prisma Access

Table of Contents

Upgrade Considerations for Panorama Managed Prisma Access

If you're using Panorama to manage Prisma Access, here's what to consider when upgrading to Prisma Access 5.0.
Where Can I Use This?What Do I Need?
  • Prisma Access (Managed by Panorama)
  • Minimum Required Prisma Access Version 5.0 Preferred or Innovation
Palo Alto Networks will perform an infrastructure upgrade for 5.0 and 5.0.1 Preferred. Optionally, you can choose to upgrade your dataplane to 10.2.8 to unlock the 5.0 and 5.0.1 Innovation features. The 5.0 and 5.0.1 releases use the 5.0 Cloud Services plugin. After you download and install the Cloud Services plugin 5.0, you receive all 5.0 and 5.0.1 Preferred features and all other Prisma Access features to date, including all previous Innovation and Preferred features; however, a dataplane upgrade to PAN-OS 10.2.8 is required to unlock the 5.0 and 5.0.1 Innovation features.
To upgrade your Cloud Services plugin to Prisma Access 5.0, use one of the following upgrade paths. To find your current plugin version in Panorama, select PanoramaCloud ServicesConfigurationService Setup and check the plugin version in the Plugin Alert area.
Be sure to follow the minimum Panorama versions for each plugin version during the upgrade.
Installed Cloud Services Plugin VersionTargeted VersionPlugin Upgrade Path
4.1 and 4.2 Preferred5.0 Preferred
Upgrade your plugin from Prisma Access 4.1 to Prisma Access 5.0 and commit and push your changes.
4.0 Preferred5.0 Preferred
  1. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
  2. Upgrade your plugin to Prisma Access 5.0 and commit and push your changes.
3.0, 3.1, and 3.2 Preferred4.1 Preferred
  1. (3.0 plugins only) Upgrade your plugin to Prisma Access 3.1 and commit and push your changes.
  2. (3.1 plugins only) Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
  3. Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
  4. Upgrade your plugin to Prisma Access 4.0 and commit and push your changes.
  5. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
  6. Upgrade your plugin to Prisma Access 5.0 and commit and push your changes.
2.2 Preferred4.1 Preferred
  1. Upgrade your plugin to Prisma Access 3.0 and commit and push your changes.
  2. Upgrade your plugin to Prisma Access 3.1 and commit and push your changes.
  3. Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
  4. Upgrade your plugin to Prisma Access 4.0 and commit and push your changes.
  5. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
  6. Upgrade your plugin to Prisma Access 5.0 and commit and push your changes.
Releases earlier than 2.2 Preferred4.1 Preferred
  1. Upgrade your plugin to Prisma Access 2.2 and commit and push your changes.
    If your deployment is on a version of Prisma Access that is earlier than 2.2 Preferred, you must first upgrade to 2.2 before you can upgrade to 3.2. Upgrades from 2.0 or 2.1 versions of Prisma Access are not supported.
  2. Upgrade your plugin to Prisma Access 3.0 and commit and push your changes.
  3. Upgrade your plugin to Prisma Access 3.1 and commit and push your changes.
  4. Upgrade your plugin to either Prisma Access 3.2 or 3.2.1 and commit and push your changes.
  5. Upgrade your plugin to Prisma Access 4.0 and commit and push your changes.
  6. Upgrade your plugin to Prisma Access 4.1 and commit and push your changes.
  7. Upgrade your plugin to Prisma Access 5.0 and commit and push your changes.