'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Outlook Cannot Connect to Exchange Online on Windows Server
Question details
Users are unable to open Outlook or connect to Exchange Online from a Windows Server 2019 terminal server.
- Product
- Microsoft Outlook
- Device & OS
- Windows Server 2019
- Scenario
- Accessing Exchange Online via Outlook on a hosted terminal server.
- Observed behavior
- Outlook fails to connect or open due to an autodiscover problem, despite local computers connecting successfully.
Verify that your local computers can successfully connect to Exchange Online to confirm the issue is isolated strictly to the terminal server environment.
Seek Specialized Support from the Microsoft Q&A Community
Since this is an advanced server-specific autodiscover issue, escalating to Exchange specialists is the most effective approach.
When standard troubleshooting steps like profile recreation, Office reinstallation, DNS flushing, and firewall checks fail on a hosted terminal server, the problem often lies in complex Autodiscover routing or Active Directory configurations. The Microsoft Q&A community has dedicated engineers who can analyze your specific server setup.
Navigate to the official Microsoft Q&A community website in your web browser.
When creating your post, apply both the 'Outlook' and 'Exchange Online' tags to ensure it reaches the right specialists.
Include your diagnostic results, server configuration (e.g., OVH hosted), affected user count, and state clearly that local computers can connect without issues.
Exclude SCP Lookup in the Registry
Force Outlook to bypass the Service Connection Point (SCP) lookup to speed up or fix Autodiscover resolution.
Switch to WPS Office for a Hassle-Free Desktop Experience
Dealing with complex Windows Server and Exchange configurations can be frustrating. Try WPS Office as a free, lightweight alternative. It offers powerful document creation capabilities without the heavy backend connectivity requirements.
- 1. Download: Visit the official WPS Office website and download the installation file.
- 2. Install: Run the installer and follow the straightforward on-screen instructions.
- 3. Start Creating: Launch WPS Office and immediately begin working on your documents, spreadsheets, and presentations.
Frequently Asked Questions
Why does Outlook connect on local computers but not on the Windows terminal server?
Terminal servers often have distinct DNS routing, stricter firewall rules, or Active Directory Service Connection Point (SCP) configurations that can misdirect or block Exchange Online autodiscover requests, whereas local computers usually rely on standard DNS.
Can I use the Microsoft Support and Recovery Assistant (SaRA) on Windows Server?
Yes, running the SaRA tool on the affected Windows Server can help diagnose specific Outlook profile failures and provide detailed logs for connectivity issues.
What is an Autodiscover problem in Outlook?
Autodiscover is an Exchange service that automatically configures user profiles. When it fails, Outlook cannot locate the server settings required to connect to the mailbox, leading to connection and login errors.
