Send & Receive Issues

Fix SMTP AUTH OAuth 2.0 Error 535 for Microsoft Personal Accounts

Natalie Taylor Oct 20, 2026 869 views

Question details

Users are experiencing an authentication failure (Error 535) when trying to use SMTP AUTH with OAuth 2.0 on personal Microsoft accounts.

How to Fix SMTP AUTH OAuth 2.0 Error 535 on Personal Microsoft Accounts

Product: Microsoft Outlook / Exchange
Device & OS: not provided
Scenario: Attempting to authenticate and send outbound emails using SMTP.Send permissions via OAuth 2.0 on a personal Microsoft or Outlook.com account.
Observed behavior: The server rejects the access token and returns SMTP Error 535, even though the same token and setup work perfectly for Microsoft 365 business accounts. Meanwhile, IMAP and Exchange ActiveSync continue to function normally.

Before you start

Ensure that your email client is updated to the latest version and verify that your application has been granted the correct SMTP.Send delegated permissions in Microsoft Entra ID.

Solution 1Recommended

Verify Configuration and Monitor Microsoft Service Updates

Confirming your configuration is strictly correct prevents wasted debugging time on this known Microsoft service issue.

Microsoft has acknowledged issues with SMTP.Send OAuth permissions for consumer accounts since February 2023.

While business accounts (onmicrosoft.com) authenticate successfully, consumer accounts frequently reject valid tokens with Error 535. Ensure your setup is flawless, then monitor for server-side fixes.

Verify OAuth Scopes

Check your application registration to ensure that your OAuth token strictly requests and includes the 'SMTP.Send' scope.

Check Client Settings

Ensure that 'SMTP AUTH' is explicitly enabled in your email client's outbound server settings, rather than falling back to unauthenticated SMTP.

Monitor for Patches

Check the Microsoft 365 Service health dashboard and related Microsoft Q&A forums regularly for officially released patches regarding this consumer-account bug.

Verify Configuration and Monitor Microsoft Service Updates

Known Server Limitation: Because this is an ongoing server-side Microsoft issue affecting personal accounts, a complete client-side fix may not be possible until Microsoft patches the authentication endpoint.

Solution 2

Use an Alternative Protocol or Microsoft Graph API

Bypassing SMTP entirely by using Microsoft Graph API or Exchange ActiveSync can immediately restore your ability to send emails.

Free Microsoft Office alternative

Try WPS Office for a Seamless and Free Productivity Experience

While you troubleshoot complex Microsoft email server issues, you do not have to let your document productivity suffer. WPS Office is a lightweight, fully compatible alternative to Microsoft Office that easily handles your Word, Excel, and PowerPoint files.

1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
2. Install the Software: Run the downloaded setup file and follow the straightforward on-screen instructions.
3. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Word, Excel, or PowerPoint files without losing any formatting.

Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Free and lightweight alternative to heavy Microsoft 365 subscriptionsFamiliar user interface makes migration instant and effortlessBuilt-in PDF editor and comprehensive toolkit for all your daily tasks

Frequently Asked Questions

Why does Error 535 only affect my personal Outlook account and not my work account?

Microsoft utilizes different backend authentication infrastructures for consumer (personal) accounts and enterprise (Microsoft 365 business) tenants. This specific OAuth 2.0 SMTP.Send bug currently resides within the consumer authentication endpoints.

Can I fix Error 535 by generating a new App Password?

If your client allows you to fall back to Basic Authentication using an App Password instead of OAuth 2.0, it might work as a temporary workaround. However, Microsoft is actively deprecating Basic Authentication, so OAuth 2.0 is highly recommended for long-term security.

Does IMAP still work even if SMTP is failing with Error 535?

Yes, incoming email protocols like IMAP and Exchange ActiveSync typically continue to function normally. Error 535 in this specific scenario is entirely isolated to outbound SMTP authentication using OAuth 2.0.

Outlook & Email Problems