Microsoftchhopkin Hi, back in May 2021 you responded to someone's question about user impersonation & proxy support with:
"the updates to support WinINET were released for SAEC Version 2008 (Build 13127.21064) released on Jan 12. This functionality is available to clients in all update channels if their version is > 13127.21064."
Just to confirm, we shouldn't need to configure anything for OCPS to attempt to use WinInet, right? If connection via WinInet fails, does it still attempt to connect via the SYSTEM local account too? I'm having difficulty getting the policy check working within our network environment (it works fine outside of it), and I suspect it's because our network security service (Zscaler) isn't compatible with WinInet for non-interactive applications/services.
On a related note, the list of URLs Microsoft recommend we allow to bypass proxy are pretty broad and we're having difficulty convincing our network team to allow them (especially *.msocdn.com, *.office.com, *.office.net). Are you able to suggest a 'bare minimum' set of URLs used by OCPS?
Thanks in advance for your help! 🙂
