A robust email, calendaring, and collaboration platform developed by Microsoft, designed for enterprise-level communication and data management.Miscellaneous topics that do not fit into specific categories.
The existing answer already covers the browser, OWA virtual directory and application pool checks.
If those look normal, I would trace one failed OWA request through the Exchange logs before changing anything else.
Check the same timestamp in:
- Frontend IIS log
- HttpProxy\Owa log
- Backend IIS log
Also use the browser Network tab to identify the request that remains pending or returns 4xx/5xx, then correlate that request with the Exchange logs.
This helps identify whether the request reaches the backend and where it starts failing.
I documented this troubleshooting method here: https://ceyhunkirmizitas.net/exchange-owa-authentication-troubleshooting-iis-logs-part-4/