docs: update Outlook.com IMAP documentation to reflect removal of Bas… (#4364)

This commit is contained in:
Kartik Balasubramanian
2026-03-18 09:57:40 +00:00
committed by GitHub
parent fb6bd5562b
commit 9302877245

View File

@@ -5,41 +5,26 @@ contentType: [integration, reference]
priority: high
---
/// warning | Microsoft has removed Basic Auth for Outlook.com IMAP
Microsoft deprecated Basic Authentication for IMAP in Exchange Online and
Outlook.com. As a result, the IMAP node **cannot connect to Outlook.com or
Microsoft 365 accounts**. App passwords are not a workaround for this
restriction.
**Use the [Microsoft Outlook node](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftoutlook.md)
instead.** It uses OAuth 2.0, which Microsoft now requires for mail access.
Refer to [Microsoft's deprecation notice](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online#what-we-are-changing)
for more information.
///
# Outlook.com IMAP credentials
Follow these steps to configure the IMAP credentials with an Outlook.com account.
IMAP access for Outlook.com and Microsoft 365 accounts is no longer supported in n8n due to Microsoft's deprecation of Basic Authentication. You cannot use IMAP (with a regular password or app password) to connect to Outlook.com or Microsoft 365 accounts.
## Set up the credentials
To replace IMAP triggers for incoming email, use the [Microsoft Outlook Trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.microsoftoutlooktrigger.md), which supports the Message Received event.
To set up the IMAP credential with Outlook.com account, use these settings:
For general Microsoft Outlook automation, use the [Microsoft Outlook node](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftoutlook.md), which uses OAuth 2.0 as required by Microsoft.
1. Enter your Outlook.com email address as the **User**.
2. Enter your Outlook.com password as the **Password**.
/// note | App password
Outlook.com doesn't require you to use an app password, but if you'd like to for security reasons, refer to [Use an app password](#use-an-app-password).
///
3. Enter `outlook.office365.com` as the **Host**.
4. For the **Port**, keep the default port number of `993`.
5. Turn on the **SSL/TLS** toggle.
6. Check with your email administrator about whether to **Allow Self-Signed Certificates**.
Refer to Microsoft's [POP, IMAP, and SMTP settings for Outlook.com](https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) documentation for more information.
## Connection errors
You may receive a connection error if you configured your Outlook.com account as IMAP in multiple email clients. Microsoft is working on a fix for this. For now, try this workaround:
1. Go to [account.live.com/activity](https://account.live.com/activity) and sign in using the email address and password of the affected account.
1. Under **Recent activity**, find the **Session Type** event that matches the most recent time you received the connection error. Select it to expand the details.
1. Select **This was me** to approve the IMAP connection.
1. Retest your n8n credential.
Refer to [What is the Recent activity page?](https://support.microsoft.com/en-us/account-billing/what-is-the-recent-activity-page-23cf5556-4dbe-70da-82c8-bb3a8d8f8016) for more information on using this page.
The source for these instructions is [Outlook.com IMAP connection errors](https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040). Refer to that documentation for more information.
## Use an app password
--8<-- "_snippets/integrations/builtin/credentials/email/outlook-app-password.md"
For more information, refer to [Microsoft's deprecation notice](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online#what-we-are-changing).