The following figures provide examples of how you can access private apps using Prisma Access.

The following figure shows a mobile user accessing a private app at a branch location. The branch is connected to Prisma Access by a remote network connection. If your network uses IPv6, you can configure the Mobile User IP address pool (for mobile users), Infrastructure Subnet (for service connections), and static or BGP routing (for the remote network connections) to use IPv6 addressing to access the app.

The following figure shows a mobile user accessing a private app that is hosted at a data center connected to Prisma Access by a service connection. You can configure the Mobile User IP address pool (for mobile users) and Infrastructure Subnet (for service connections) to use IPv6 addressing to access the app.

The following figure shows an internal GlobalProtect user at a branch location connected to Prisma Access by a remote network accessing a private app that is hosted at a data center connected to Prisma Access by a service connection. You can configure the Infrastructure Subnet (for service connections) and static or BGP routing (for the service connections and remote network connections) to use IPv6 addressing to access the app.

The following figure shows a user at a branch location connected to Prisma Access by a remote network accessing a private app that is hosted at another branch location connected by a remote network connection. You can configure IPv6 addressing for static or BGP routing for the remote network connections to access the app.

The following figure shows a user at a branch location with IPv6 addressing accessing an external app. In this case, IPv4 routing is required to access the external app, regardless of your Prisma Access IPv6 configuration.

The same IPv4 requirement applies for external GlobalProtect users who access a public app.