Using classic Outlook for Windows in business environments
Hi @User A:P
I'm just a fellow community user, so I don't have access to your organization's environment. Please treat the following as general suggestions.
You've narrowed this down very thoroughly. As far as I know, in classic Outlook both Automatic Replies and free/busy information go through Exchange Web Services (EWS), which is separate from the regular path for sending and receiving email. Since the same accounts work on the terminal server and in Outlook on the web, and your own account also fails on an affected PC, I think the cause is more likely on these PCs or their network path (for example a proxy, firewall, SSL inspection tool or TLS configuration) than on the mailboxes or your organization's EWS policy. However, I can't confirm this yet.
To compare a failed request with a successful one, you could try:
- Capture HTTPS traffic with Fiddler while opening Automatic Replies on both machines, to see which error code the EWS request returns, and whether it's blocked by a proxy or fails because of a certificate error.
- Open the EWS URL (from the Test E-mail AutoConfiguration results) in a browser on an affected PC, to check whether it connects and shows a sign-in prompt.
To help narrow down the cause, could you please share:
- Do the affected PCs and the terminal server go through the same proxy or network path? Do these PCs have a different proxy configuration (including WinHTTP proxy) or PAC file?
- Is there any security software, VPN or SSL inspection tool installed only on the affected PCs?
- Are the Outlook version and update channel the same on the affected PCs and the terminal server (File > Office Account)?
- When did the issue start, and did it coincide with any Windows or Office update or network change?
- Are any other PCs on the same network affected in the same way?
I agree with your approach of checking the PC side thoroughly before changing the EWS policy for the whole organization. Please update the information above.