>
    GCP-NCC CloudBlade Version Beta
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma
    3. Prisma SD-WAN
    4. CloudBlades Integration and Deployment
    5. Prisma SD-WAN CloudBlades Release Notes
    6. GCP-NCC CloudBlade Integration
    7. GCP-NCC CloudBlade Version Beta
    Download PDF

    GCP-NCC CloudBlade Version Beta

    Table of Contents

    GCP-NCC CloudBlade Version Beta

    This section contains important features and caveats of the Prisma SD-WAN GCP-NCC CloudBlade. The default virtual ION version for this CloudBlade is 5.5.3-b4.

    New/Updated Features

    According to Google, Network Connectivity Center is a hub-and-spoke model for network connectivity management in Google Cloud. Its hub resource reduces operational complexity through a simple, centralized connectivity management model. The hub, combined with Google's network, delivers reliable connectivity on demand.
    In Prisma SD-WAN, as per Google, NCC would serve as a vantage point to seamlessly connect VPNs, partner dedicated interconnects, as well as third-party routers and Software-Defined WANs, helping you optimize connectivity, reduce operational burden, and lower costs—wherever your applications or users may be.
    Cloud Router is a fully distributed and managed Google Cloud service that programs custom dynamic routes and scales with network traffic. It dynamically exchanges routes between Virtual Private Cloud (VPC) and on-premise networks using Border Gateway Protocol (BGP).
    This release supports both new / existing GCP deployments and multi-region GCP deployments.

    Caveats/Limitations

    The following caveats are observed with the GCP-NCC Integration CloudBlade:
    1. Upon disabling the GCP-NCC CloudBlade, it may take up to 15 minutes to delete all the resources in GCP and the Prisma SD-WAN Controller. It is recommended to use the Monitor tab within the CloudBlade to ensure all resources are deleted before uninstalling the CloudBlade.
    2. It is not recommended to uninstall the GCP-NCC CloudBlade without disabling the CloudBlade prior and waiting for the cleanup to complete. If an uninstall is done without disabling then all control of the CloudBlade's resources is disabled. Resources cannot be deleted by the CloudBlade even after reinstalling it, cleanup of the resources must be done manually.
    3. When the Transit VPC in a Brownfield deployment is an existing Transit VPC, created with routing mode as regional, the GCP-NCC CloudBlade deployment will fail. The routing mode must be created (or modified) as Global to avoid any errors in the deployment.
    4. The Project ID value should not be changed while the GCP-NCC CloudBlade is in an Enabled state. It is recommended to disable the CloudBlade and ensure the resources are deleted in both the GCP and the Prisma SD-WAN Controller before changing the Project ID.

    Compatibility Matrix

    GCP NCC Hubs are only available in specific compute locations. Refer to Network Connectivity Center Locations for an up-to-date list of supported regions.

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