This issue occurred due to a behavior change in Pulse Secure Desktop client (Windows) 5.2R8 and 5.3R2 to evaluate the proxy first before attempting to connect direct.
This issue is applicable when the following conditions are met:
- Pulse Secure Desktop client (Windows) 5.2R8 and 5.3R2 only
- Credential Provider is configured