>
    Strata Copilot
    Upgrade Considerations for Panorama Managed Prisma Access (Managed by Panorama)
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma Access
    3. Prisma Access Release Notes
    4. Panorama Support for Prisma Access 5.2, 5.2.1, and 5.2.2
    5. Upgrade Considerations for Panorama Managed Prisma Access (Managed by Panorama)
    Download PDF
    Prisma Access

    Upgrade Considerations for Panorama Managed Prisma Access (Managed by Panorama)

    Table of Contents

    Upgrade Considerations for Panorama Managed Prisma Access (Managed by Panorama)

    If you're using Panorama to manage Prisma Access, here's what to consider when upgrading to Prisma Access 5.2, 5.2.1, or 5.2.2.
    Where Can I Use This?What Do I Need?
    • Prisma Access (Managed by Panorama)
    • Prisma Access license
    • Minimum Required Prisma Access Version 5.2, 5.2.1, or 5.2.2 Preferred or Innovation
    To upgrade your Cloud Services plugin to Prisma Access 5.2, 5.2.1, or 5.2.2, 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
    5.15.2, 5.2.1, or 5.2.2
    Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.
    5.05.2, 5.2.1, or 5.2.2
    1. Upgrade your plugin from Prisma Access 5.0 to Prisma Access 5.1 and commit and push your changes.
    2. Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.
    4.1 and 4.25.2, 5.2.1, or 5.2.2
    1. Upgrade your plugin from Prisma Access 4.1 to Prisma Access 5.0 and commit and push your changes.
    2. Upgrade your plugin from Prisma Access 5.0 to Prisma Access 5.1 and commit and push your changes.
    3. Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.
    4.05.2, 5.2.1, or 5.2.2
    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. Upgrade your plugin from Prisma Access 5.0 to Prisma Access 5.1 and commit and push your changes.
    4. Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.
    3.0, 3.1, and 3.2 Preferred5.2, 5.2.1, or 5.2.2
    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.
    7. Upgrade your plugin from Prisma Access 5.0 to Prisma Access 5.1 and commit and push your changes.
    8. Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.
    2.2 Preferred5.2, 5.2.1, or 5.2.2
    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.
    7. Upgrade your plugin from Prisma Access 5.0 to Prisma Access 5.1 and commit and push your changes.
    8. Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.
    Releases earlier than 2.2 Preferred5.2, 5.2.1, or 5.2.2
    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.
    8. Upgrade your plugin from Prisma Access 5.0 to Prisma Access 5.1 and commit and push your changes.
    9. Upgrade your plugin from Prisma Access 5.1 to Prisma Access 5.2 and commit and push your changes.

    © 2026 Palo Alto Networks, Inc. All rights reserved.