Three tickets before lunch
Same dummy company, Apex Freight. Do not disable Zscaler. Split ZIA / ZPA / ZDX, quote one evidence field, then change one thing on a pilot user.

Open with ZCC colour, IdP user, exact URL or FQDN. If it is SaaS, open Web Insights. If it is private, open User Activity Diagnostics. If it is slow, open ZDX and name the hop.
Split the ticket
Never mix the three in one guess. Outlook web = ZIA. SAP on an internal FQDN = ZPA. “Everything slow” = ZDX hop before any disable.

Live desk — order you speak
Open
“Share ZCC icon colour, logged-in user, and the exact URL or app name.”
Classify
outlook.office.com → ZIA. sap.apexfreight.internal → ZPA. “Everything slow since morning” → ZDX first.
Quote evidence
One Web Insights row or one Diagnostics status code or one ZDX hop. Then change.
Pilot
Fix Priya. Then a change window for the site. Never org-wide on a P1 guess.
Ticket 1 — ZIA · Outlook spins
Priya, ZCC green, Teams OK, OWA spins. This is ZIA.
- Analytics → Web Insights → user + outlook.office.com. Empty log? Forwarding / Trusted Network, not URL policy.
- Log exists, action Blocked? Quote the rule (URL vs Firewall vs SSL).
- Cert warning? Inspect CA missing on the laptop — Side A.
- IdP loop? Exempt login.microsoftonline.com from PAC/tunnel hairpin.
Web Insights: action, policy name, location, SSL inspected yes/no.
Ticket 2 — ZPA · SAP cannot connect
Aditya, ZCC green, SAP dead. This is ZPA.
Analytics / Diagnostics / Log Type: User Activity
User Activity · priya@apexfreight.in
Empty Connector + Close means ZPA never selected a connector. Status BRK_MT_SETUP_FAIL_NO_POLICY_FOUND means allow policy is missing or the segment/group is disabled. Source: help.zscaler.com session status codes.
- Empty Connector + Close → mapping/policy, not connector ping.
NO_POLICY_FOUND→ add/enable allow, or enable the segment.REJECTED_BY_POLICY→ a deny matched; do not add a second allow above it without reading order.- Named connector + fail → connector LAN DNS/port to SAP.
Ticket 3 — slowness
Never start with disable. Who / which app / wired or Wi-Fi / one user vs site vs org.
- ZDX: device, Wi-Fi, ISP, Zscaler hop, app hop. Quote the hop.
- ZIA slow after GRE: MTU/MSS.
- ZIA slow on one SaaS after inspect: exemption on the pilot, then a named inspect-exception.
- ZPA slow: connector CPU, path to app, one connector vs group.

Unsafe vs safe
| Unsafe | Safe |
|---|---|
| Disable ZCC for the company | Collect ZCC support tool from Priya only |
| Reinstall ZCC because SAP is down | Read Connector field on Diagnostics |
| Org-wide Decrypt off | Pilot exemption + inspect CA check |
| New GRE because one user is slow | ZDX hop; if device Wi-Fi, stop |
What you proved, what you did not change, next window if a change is needed.
Back to path hub · Deep: ZIA command center · ZPA command center
Knowledge check
You are on the phone. Pick the first safe move.
Sources
Related: Path hub · ZIA path · ZPA path · ZIA command center · ZPA command center