Using Classic Outlook on Windows for personal email, calendar, and contact management
Office 2013 still supports POP and SMTP for Outlook.com, but Microsoft has tightened authentication. The issue is not POP itself, but modern sign-in requirements.
Outlook.com no longer allows basic authentication (username + password only) for many older clients unless specific conditions are met. That’s why different server/port combinations often fail.
Correct POP/SMTP settings for Outlook.com:
Incoming (POP) Server: outlook.office365.com Port: 995 Encryption: SSL/TLS Username: full Outlook.com email address Password: account password or app password
Outgoing (SMTP) Server: smtp.office365.com Port: 587 Encryption: STARTTLS Authentication: required (same username and password)
Important blockers in Office 2013:
- Basic auth limitations Office 2013 often cannot complete modern OAuth sign-in required by Microsoft accounts.
- Security defaults in Microsoft account If two-step verification is enabled, normal password will fail. You must use an app password.
- Legacy client restriction Microsoft has progressively reduced support for older Outlook builds, especially for Outlook.com POP access.
What this means in practice: POP works in theory, but Office 2013 is frequently rejected due to authentication method mismatch. IMAP or upgrading Outlook is the stable solution. If upgrade is not possible, try:
- Enable 2FA
- Generate an app password from Microsoft account security settings
- Use that app password in Outlook 2013
Final note: Your reference to newer Outlook support is correct for modern clients. Office 2013 sits in a legacy category where POP/SMTP still exists, but authentication is the limiting factor, not server configuration.Office 2013 still supports POP and SMTP for Outlook.com, but Microsoft has tightened authentication. The issue is not POP itself, but modern sign-in requirements.
Outlook.com no longer allows basic authentication (username + password only) for many older clients unless specific conditions are met. That’s why different server/port combinations often fail.
Correct POP/SMTP settings for Outlook.com:
Incoming (POP)
Server: outlook.office365.com
Port: 995
Encryption: SSL/TLS
Username: full Outlook.com email address
Password: account password or app password
Outgoing (SMTP)
Server: smtp.office365.com
Port: 587
Encryption: STARTTLS
Authentication: required (same username and password)
Important blockers in Office 2013:
- Basic auth limitations
Office 2013 often cannot complete modern OAuth sign-in required by Microsoft accounts. - Security defaults in Microsoft account
If two-step verification is enabled, normal password will fail. You must use an app password. - Legacy client restriction
Microsoft has progressively reduced support for older Outlook builds, especially for Outlook.com POP access.
What this means in practice:
POP works in theory, but Office 2013 is frequently rejected due to authentication method mismatch. IMAP or upgrading Outlook is the stable solution. If upgrade is not possible, try:
- Enable 2FA
- Generate an app password from Microsoft account security settings
- Use that app password in Outlook 2013
Final note:
Your reference to newer Outlook support is correct for modern clients. Office 2013 sits in a legacy category where POP/SMTP still exists, but authentication is the limiting factor, not server configuration.