We are supporting a client with two separate Azure tenants and using Netskope SSE for secure access. Our configuration allows certain Azure base URLs via NPA for PaaS services, while the Azure portal routes through SWG. We use the same client and steering configuration for users accessing both tenants.
Observed Behavior:
When accessing via GUI/browser, traffic is correctly segregated per tenant.
When using CLI, traffic always routes to the primary tenant, even when attempting to access resources in the secondary tenant.
CLI-based operations cannot properly enforce tenant-specific routing.
Impact: CLI operations on the secondary tenant fail or incorrectly use the primary tenant context
