Exchange Connection Problems

How to Fix Exchange SMTP Authentication Fails for IMAP and SMTP

Rana GarciaRana Garcia Oct 23, 2026 868 views

Question details

The user is unable to configure an Exchange email account via IMAP and SMTP on an online portal, receiving errors that no account or settings were found despite SMTP being enabled.

How to Fix Exchange SMTP Authentication Fails for IMAP and SMTP
Product
Microsoft Exchange
Device & OS
not provided
Scenario
Configuring a Microsoft Exchange email account on a third-party online portal using IMAP and SMTP.
Observed behavior
The portal reports that no account or settings are found, causing the connection to fail, even though SMTP is enabled and modern authentication is disabled.
Before you start

Ensure you have administrator access to your Microsoft 365 tenant and that Exchange Online PowerShell is installed on your system.

Solution 1Recommended

Reset Basic Authentication for POP and IMAP via PowerShell

Toggle the Basic authentication settings in your Microsoft 365 tenant to resolve hidden configuration conflicts blocking IMAP and SMTP.

Even when SMTP appears to be enabled, underlying tenant policies might block legacy authentication methods. Resetting the Basic authentication status for POP and IMAP forces the server to refresh these permissions.

1
Connect to Exchange Online

Open PowerShell as an administrator and connect to Exchange Online using your tenant admin credentials.

2
Verify Basic Authentication Status

Check if Basic authentication is currently enabled for POP and IMAP protocols within your tenant settings.

3
Disable Basic Authentication

If it is already enabled, run the appropriate PowerShell command to disable Basic authentication for both POP and IMAP temporarily.

4
Wait for Settings to Sync

Pause for a few minutes to allow the updated authentication policies to propagate across the Microsoft 365 servers.

5
Re-enable Basic Authentication

Execute the PowerShell command to re-enable Basic authentication for POP and IMAP, then attempt your portal configuration again.

Reset Basic Authentication for POP and IMAP via PowerShell
Modern Authentication Settings: Since modern authentication is disabled in your scenario, successfully connecting relies entirely on explicit permission for Basic authentication at the tenant level.
Free Microsoft Office alternative

Looking for a Lightweight Office Suite? Try WPS Office

While troubleshooting complex Microsoft Exchange and Office 365 tenant settings, you might be looking for a simpler, cost-effective office suite. WPS Office provides a complete set of productivity tools with excellent Microsoft format compatibility, without the heavy administrative overhead.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install WPS Office: Run the setup file and follow the on-screen instructions to install the suite on your device.
  3. 3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Office documents without losing any formatting.
Free and lightweight office suite for daily productivityFully compatible with Microsoft Word, Excel, and PowerPoint formatsFamiliar user interface for a seamless transitionNo complex tenant administration or PowerShell configuration required
microsoft office alternative - wps office

Frequently Asked Questions

Why does Exchange IMAP/SMTP authentication fail when SMTP is enabled?

Even if SMTP is enabled on the mailbox, the tenant's overall authentication policies, such as disabled Basic authentication, can block connections from third-party portals.

How do I check my Exchange tenant authentication settings?

You can verify your tenant's authentication policies by logging into the Microsoft 365 admin center under Org Settings, or by querying the authentication policies using Exchange Online PowerShell.

Do I need PowerShell to fix IMAP/SMTP connection issues?

In many cases, yes. Resetting or explicitly defining authentication policies for specific legacy protocols often requires Exchange Online PowerShell for granular control.

What should I do if resetting Basic authentication doesn't work?

If the issue persists, capture a detailed screenshot of the exact error message, verify that no Conditional Access policies are blocking legacy authentication, and consult Microsoft's official troubleshooting documentation.