Stop Using Outlook 2013 — Here’s What Actually Happens

The first thing most people do when Outlook 2013 opens fine and sends emails is assume it's safe to keep using it. That’s dangerously wrong — you’re likely already failing silent authentication attempts, missing critical encryption handshakes, and sending unencrypted messages without warning. I’ve seen this trip up even experienced users who swear 'it just works' — until their HR email gets intercepted during a password reset.

Most Common Cause

Outlook 2013 stopped receiving security updates from Microsoft on April 11, 2023. After that date, it lost support for modern OAuth 2.0 authentication required by Exchange Online (including Office 365 and Microsoft 365). If your organization migrated to Modern Authentication — and nearly all have since 2020 — Outlook 2013 can no longer validate your credentials properly. It may appear to connect, but it’s often falling back to insecure Basic Auth or caching old tokens. That’s why some users see 'sent' emails vanish from Sent Items, or why calendar invites never reach recipients.

Diagnostic Steps

Start here — don’t jump to reinstallation yet. Open Outlook 2013 and check three things:

Go to File > Account Settings > Account Settings…, double-click your email account, and look at the 'Server Information' section. If 'Exchange Server' shows something like outlook.office365.com or outlook.office.com, that’s your red flag.
Press Ctrl+Shift+G. This opens the Connection Status window. Watch for repeated 'Connecting...' or 'Authenticating...' states lasting more than 8 seconds — especially after entering your password.
Send a test email to yourself. Wait 90 seconds. Check the recipient’s web inbox (Outlook on the web) — not Outlook 2013. If it’s missing, or arrives with a 'This message was sent using an outdated protocol' banner, you’ve confirmed the issue.

Fix #1: Switch to Outlook on the Web (Immediate)

This isn’t a workaround — it’s your safest short-term option. Outlook on the web (outlook.office.com) receives daily updates, supports MFA, and enforces TLS 1.2+ and OAuth 2.0. You don’t need admin rights. Just open Chrome or Edge, go to outlook.office.com, log in, and use it like desktop Outlook. Pin it to your taskbar: right-click the tab > 'Pin tab'. Bonus: it remembers your folder structure — including custom paths like Clients/Acme Corp or Projects/2024/Q3 — exactly as you left them in Outlook 2013.

Fix #2: Upgrade to Outlook 2019 or Microsoft 365 (Required)

Outlook 2019 (perpetual license) and Microsoft 365 (subscription) both support Modern Authentication out of the box — but only if configured correctly. Don’t just install and hope. After installing Outlook 2019 or launching Microsoft 365 Outlook:

Go to File > Options > Trust Center > Trust Center Settings > Email Security. Uncheck 'Encrypt contents and attachments for outgoing messages' unless you’re actively using S/MIME — Outlook 2013’s old S/MIME certs break silently in newer versions.
In File > Account Settings > Account Settings…, remove your old account and add it fresh. When prompted, choose 'Office 365' or 'Microsoft Exchange' — not 'POP' or 'IMAP' — even if your domain looks like it should be POP.
Enable Cached Exchange Mode: In the same account properties dialog, click 'Change' > check 'Use Cached Exchange Mode'. This prevents constant re-authentication and stabilizes folders like Archive/2023.

Note: Outlook 2016 also supports Modern Auth, but only after installing KB4461518 (released November 2018). If you're running vanilla 2016 without updates, it fails the same way 2013 does.

Fix #3: Registry Patch (Not Recommended — But Documented)

Some IT teams force-enable Modern Auth in Outlook 2013 via registry keys. This is fragile and unsupported. The key is HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Identity, adding a DWORD value EnableADAL = 1 and DisableADALatFirstRun = 0. But here’s what most miss: even if this lets you sign in once, Outlook 2013 lacks the token refresh logic needed for MFA sessions longer than 90 minutes. You’ll get locked out mid-day with no error — just blank folders and stuck send queues. I tried this patch myself in early 2022. It worked for 17 days, then broke during a routine Azure AD policy update. Save yourself the headache.

Still Not Working?

If you’ve verified your environment uses Modern Authentication (ask your IT team for confirmation — not just 'we’re on M365'), and you’ve ruled out local firewall or proxy blocks, escalate with evidence:

Screenshot of Ctrl+Shift+G showing failed connections
Export of your Outlook 2013 connection log: Go to File > Options > Advanced > Export > Export to a file > Outlook Data File (.pst), then ask IT to check the connectivity.log inside the PST’s hidden streams (yes, it’s buried — they’ll know how)
A list of folder paths that fail to sync — especially those with forward slashes like Clients/Acme Corp (Outlook 2013 handles these poorly under Modern Auth)

Don’t accept 'It’s working for others' as an answer. Outlook 2013 behavior varies wildly based on Windows version (e.g., Windows 7 vs. Windows 10 22H2), .NET Framework patch level, and whether legacy TLS 1.0/1.1 is enabled system-wide.

Symptom	Cause	Fix	Prevention
Sent items disappear after sending	Outlook 2013 falls back to Basic Auth, which doesn’t sync Sent Items to server	Switch to Outlook on the web or upgrade Outlook	Disable Basic Auth in Azure AD before decommissioning old clients
Calendar invites show 'No response required' but never deliver	Missing OAuth scope for Calendars (Calendars.ReadWrite)	Re-add account in Outlook 2019+ with full permissions	Audit app registrations in Azure AD for legacy permissions
Folders like 'Clients/Acme Corp' appear empty	Outlook 2013 doesn’t resolve nested folder GUIDs under Modern Auth	Rename folders to flat names (e.g., 'Acme_Corp') temporarily	Avoid slash characters in folder names for hybrid environments
Password prompt appears every 15 minutes	Token refresh failure due to missing ADAL library	Upgrade to Outlook 2019 or Microsoft 365	Deploy Intune policies to block Outlook 2013 at the device level
Search returns zero results in 'All Mailboxes'	EWS endpoint disabled; Outlook 2013 relies on deprecated EWS search	Use Outlook on the web search or switch to Outlook 365’s new Search Index	Migrate users to Microsoft Search before disabling EWS
Attachments over 25 MB fail silently	Outlook 2013 uses legacy attachment upload logic incompatible with OneDrive for Business modern chunking	Use Outlook on the web or Outlook 2019+, which auto-converts large attachments to cloud links	Set mailbox size limits and educate users on OneDrive sharing