You may find that the new Outlook for Windows cannot connect to your company’s on-premises Exchange server. This is a known limitation of the application’s current architecture. The new Outlook is built primarily for cloud-based Microsoft 365 and consumer email services. This article explains the technical reasons behind this restriction and details the available workarounds.
Key Takeaways: New Outlook and On-Premises Exchange Access
- Account setup via Microsoft 365 work or school account: This method only connects to Exchange Online and cannot be redirected to an on-premises server.
- Toggle back to classic Outlook: Use the toggle switch in the new Outlook’s settings to immediately return to the full-featured desktop application.
- Outlook for Windows desktop application: This version supports all connection types including MAPI/HTTP and RPC over HTTP for on-premises Exchange.
Why the New Outlook Does Not Support On-Premises Exchange
The new Outlook for Windows is a progressive web app built on a different codebase than the classic desktop application. It uses modern authentication protocols and APIs designed for cloud services like Microsoft 365, Outlook.com, and Google Gmail. Its architecture does not include the legacy connectivity components required to talk directly to an on-premises Exchange server.
These legacy components include MAPI over HTTP and RPC over HTTP, which are essential for the desktop Outlook client to communicate with an Exchange server inside a corporate network. The new Outlook relies on the Microsoft Cloud for its backend services, so it cannot establish a direct line to a server that exists solely within your organization’s data center. This is a fundamental design choice, not a temporary bug.
Primary Supported Account Types
The new Outlook is optimized for the following account types: Microsoft 365 or Office 365 work or school accounts, Outlook.com, Hotmail, Live.com, and Google Gmail accounts via IMAP. If your organization uses a hybrid Exchange setup where some mailboxes are on-premises and some are in the cloud, the new Outlook will only be able to add accounts for mailboxes that have been migrated to Exchange Online.
Steps to Continue Using On-Premises Exchange
If your mailbox is hosted on an on-premises Exchange server, you must use the classic Outlook for Windows desktop application. Here is how to ensure you are using it.
- Switch back from the new Outlook preview
If you are currently in the new Outlook, look for the toggle switch in the top-right corner of the window. It typically looks like a slider or says “Try the new Outlook” or “New Outlook.” Click this toggle to turn it off and revert to the classic Outlook application immediately. - Open the classic Outlook desktop app directly
Close the new Outlook window. Search for “Outlook” in the Windows 11 Start menu and select the application named simply “Outlook” without the “New” prefix. This is the full desktop client. - Add your Exchange account in classic Outlook
Go to File > Account Settings > Account Settings. Click New, enter your name, email address, and password. Classic Outlook will automatically detect your on-premises Exchange server settings if it is configured for Autodiscover. - Verify your connection type
After adding the account, go to File > Account Settings > Account Settings again. Select your Exchange account and click Change. On the Server Settings screen, you can see the server name, which will be your internal Exchange server address, not outlook.office365.com.
If You Cannot Add an On-Premises Account in Classic Outlook
Classic Outlook Fails to Autodiscover the Server
If the classic Outlook desktop app cannot find your server, your IT department may need to verify the Autodiscover service DNS records are correctly configured for your domain. You can manually specify the server name and your username in the account setup dialog. Contact your system administrator for the correct internal server name and any required connection settings.
Your Organization Only Offers Outlook on the Web
Some companies with on-premises Exchange deploy only Outlook on the Web for client access. In this case, you can use any modern web browser to access your mailbox by navigating to the URL provided by your IT team. This is a supported method that does not require any local client installation.
New Outlook vs Classic Outlook: Exchange Connectivity
| Item | New Outlook for Windows | Classic Outlook Desktop App |
|---|---|---|
| On-Premises Exchange Support | No | Yes |
| Primary Connection Method | Microsoft Cloud APIs | MAPI/HTTP, RPC over HTTP |
| Account Auto-Detection | For Microsoft 365 and consumer services | For Exchange via Autodiscover service |
| Offline Access to Mail | Limited, depends on browser cache | Full, via local OST cache file |
| Required Infrastructure | Internet access to Microsoft services | Network access to your Exchange server |
You must use the classic Outlook desktop application to connect to an on-premises Exchange server. The toggle switch in the new Outlook provides a quick way to return to the full-featured client. For the foreseeable future, organizations relying on local Exchange servers should plan to keep the desktop app deployed. An advanced tip is to check your Outlook version under File > Office Account to ensure you are on a current build that receives security updates for Exchange connectivity.