Why does the Private application access via Prisma Browser stops working after enabling GlobalProtect Agent.

Why has Private Application Access through Prisma Browser stopped working after the GlobalProtect Agent enabled?

• Prisma Browser
• Private Application Access (PAA)
• GlobalProtect (GP) Agent

1. When 'Agent detection' is enabled under Prisma Browser Setup > Routing, or in the Browser Customization rule, the system initiates a check for network path determination.
2.  The system detects if either the GlobalProtect or Prisma Access agent is currently running on the device.
3. All device traffic is then routed through the available active agent identified in the previous step.
4. If the required private application traffic cannot be successfully accessed through the active agent, the application will fail to load.

Note:

• Agent detection detects GlobalProtect(GP)  or Prisma Access agent (PAA) when their service is running irrespective of the GP/PAA connection state.
• In other words, if the GP or PAA is running on the system PB (Prisma Browser) will mark the network as internal and will not connect to Prisma Access Explicit proxy.