---
title: "Outlook modern authentication: connect Outlook.com with OAuth"
description: "Connect an Outlook.com or Hotmail mailbox to Mailera with OAuth. Check Microsoft sign-in, mailbox status, sync and incoming mail without app passwords."
url: https://mailera.app/en/blog/outlook-modern-authentication-oauth
published: 2026-10-25
updated: 2026-10-25
---

# Outlook modern authentication: connect Outlook.com with OAuth

Outlook.com and Hotmail connections need OAuth, not another password retry. Connect your mailbox to Mailera through Microsoft, then check authentication and incoming mail separately.

## TL;DR: How do you connect Outlook.com with modern authentication?

Connect your Outlook.com or Hotmail mailbox to Mailera with OAuth. An Admin or Leader opens **Mailboxes → Add mailbox → Sign in with Microsoft** and completes Microsoft's authorization flow. Then check authentication and incoming mail separately. This guide covers adding a personal Microsoft mailbox to Mailera, not repairing an existing Mailera entry or every Outlook desktop problem.

## Is the problem with Outlook.com, the Outlook app, or Microsoft 365?

Start by identifying what you are connecting. Outlook.com is a mailbox service. Outlook is also an application name. Instructions for one are not automatically instructions for the other.

| Account or client | How to identify the scope | Appropriate next step |
| --- | --- | --- |
| Personal Outlook.com or Hotmail mailbox | You are connecting your personal Microsoft mailbox | Use a supported OAuth connection; follow the Mailera steps below |
| Work or school Microsoft 365 mailbox | Your organization manages the account | Use OAuth and check applicable administrator restrictions if consent fails |
| Outlook desktop application | The failing connection is inside the installed Outlook client | Follow Microsoft's guidance for that client and its account configuration |

If you are troubleshooting server settings in another application, see the guide to [Outlook IMAP and SMTP settings](https://mailera.app/en/blog/outlook-imap-smtp-settings). Mailera's Microsoft connection uses Microsoft Graph instead of that generic IMAP setup.

For a broader review across providers, use the [2026 email authentication changes checklist](https://mailera.app/en/blog/email-authentication-changes-2026).

## What changed, and why does the old password connection fail?

Modern authentication, in this context, means OAuth2: the application uses access tokens for authorized access rather than sending your mailbox username and password with every request.

Microsoft's [Outlook.com modern-authentication notice](https://support.microsoft.com/en-us/support/known-issues/modern-authentication-methods-now-needed-to-continue-syncing-outlook-email-in-non-microsoft-email-ap) gives September 16, 2024 as the date Basic Authentication became unavailable. Its [Outlook.com connection settings](https://support.microsoft.com/en-us/outlook/pop-imap-and-smtp-settings-for-outlook-com) explicitly require Modern Auth / OAuth2, and note that POP and IMAP access is disabled by default.

That is why retrying the correct password can still leave an old connection broken. The authentication method itself needs to change. OAuth does not mean you will never see Microsoft's sign-in screen; the distinction is how the application accesses mail after authorization.

Mailera connects Outlook.com, Hotmail and Microsoft 365 through OAuth and Microsoft Graph. Use its [Microsoft mailbox connection](https://mailera.app/en/providers/microsoft), not an app-password or custom IMAP flow.

For Outlook desktop, Microsoft's notice recommends automatic account configuration in a new profile to add Outlook.com with Modern Authentication. For Outlook for Windows, Microsoft's notice says that Modern Authentication is not supported when Outlook is configured to connect to Outlook.com using POP or IMAP. Those are client-specific instructions, not a reason to edit registry settings for a Mailera connection.

## How do you connect Outlook.com to Mailera with OAuth?

To add an Outlook.com or Hotmail mailbox to Mailera, use Microsoft's interactive sign-in flow.

1. **Check access at Microsoft first.** Sign in to the intended mailbox on Microsoft's own site. Confirm that you can open that mailbox. This checks account access; it does not establish that a third-party application has authorization.
2. **Open the Microsoft connection path.** As an Admin or Leader in Mailera, go to **Mailboxes → Add mailbox → Sign in with Microsoft**. These are the roles that can add mailboxes. Do not select **Custom IMAP** for this workflow.
3. **Choose the intended Microsoft account.** Check the address before continuing. Review the requested permissions and complete Microsoft's sign-in and consent flow. Microsoft asks for consent to requested permissions that you have not already approved.

![Mailera Add mailbox page with the Sign in with Microsoft tab selected.](https://mailera.app/media/d8e9591c875d36fe/email-app-passwords-connect-your-mailbox-to-an-ai-agent-add-en-1200.jpg)
_Choose Sign in with Microsoft for an Outlook.com or Hotmail mailbox._

For work or school accounts, read the actual consent error before changing anything. Microsoft's [authorization-code flow documentation](https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-auth-code-flow) explains that some permissions are administrator-restricted. An organizational restriction may need an administrator's involvement; repeated password changes do not address that restriction.

## How do you verify that authentication and mail sync work?

Treat authentication, retrieval and sending as separate checks. A successful read does not establish that sending works.

### Check the mailbox and a controlled message

In **Unified inbox**, select the connected mailbox and confirm that you are inspecting the intended address.

Then send a message from another mailbox you control. Give it a distinctive subject, such as `Outlook OAuth connection test — cedar`, and keep the body free of sensitive information. Look for that subject in the selected mailbox. Check Junk as well as Inbox.

![A controlled test message in the selected Microsoft mailbox in Mailera's Unified inbox.](https://mailera.app/media/cd9e7ba53410f84c/choose-an-email-mcp-server-for-your-existing-mailboxes-en-1200.jpg)
_Verify retrieval with a newly sent test message in the intended mailbox._

Finding that newly sent message confirms retrieval for that message. An older message already visible in Mailera is not a useful substitute for this check. If the new message is absent, check the selected mailbox and folders, then use the API checks below to inspect authentication and sync details.

### Check Microsoft sign-in through the API

For a developer check, set `$MAILERA_API_KEY` to your Mailera key and `$MAILBOX_ID` to the intended mailbox ID in your local environment. The status endpoint requires the `read` scope and checks Microsoft sign-in directly:

```bash
curl --request GET \
  "https://mailera.app/api/public/v1/mailboxes/$MAILBOX_ID/status" \
  --header "Authorization: Bearer $MAILERA_API_KEY"
```

Use **Settings → API key → Create key** to create a key with the **Read** permission and a mailbox scope limited to the relevant group. Keep the key out of screenshots, shared logs and source files. See [Mailera's security information](https://mailera.app/en/security) when deciding how to handle access credentials.

For additional connection details, use `GET /mailboxes/{id}` with a read-scoped key. Its response contains `provider`, `protocol`, `status`, `last_sync_at` and `sync.sleeping_since` under `data`. Inspect those fields for the intended mailbox rather than treating an HTTP response alone as proof that the mailbox is healthy.

### Request sync if needed

Mailera checks active mailboxes more often than idle ones, and inactive mailboxes can sleep. A sync request can wake a sleeping mailbox. It requires the separate `sync` scope, shown as **Sync** when creating a key:

```bash
curl --request POST \
  "https://mailera.app/api/public/v1/mailboxes/$MAILBOX_ID/sync" \
  --header "Authorization: Bearer $MAILERA_API_KEY"
```

This requests a sync; it does not repair failed Microsoft authorization or promise a fixed arrival time. If sign-in fails, address that failure before repeatedly requesting sync. For a working connection with missing mail, use the [mailbox sync troubleshooting guide](https://mailera.app/en/blog/mailbox-sync-troubleshooting).

You can also inspect recent Inbox messages with a read-scoped key:

```bash
curl --request GET \
  "https://mailera.app/api/public/v1/mailboxes/$MAILBOX_ID/messages?folder=inbox&limit=10" \
  --header "Authorization: Bearer $MAILERA_API_KEY"
```

Look at `subject`, `received_at` and `folder` to identify your test message. Change `folder=inbox` to `folder=junk` to inspect Junk. The [API documentation](https://mailera.app/en/docs) covers the endpoints; the broader [reliable email API workflow guide](https://mailera.app/en/blog/reliable-email-api-agent-workflows) covers building checks into an application.

## What common mistakes keep an old connection broken?

| Symptom | What to check | Next action |
| --- | --- | --- |
| Outlook keeps asking for a password | Whether the failing application still uses password-based authentication | Switch that application's account setup to a supported OAuth method |
| The wrong mailbox appears | The account selected during Microsoft sign-in | Check the selected address before authorizing access |
| Microsoft rejects consent | The exact error and whether this is a personal or organizational account | Address the stated restriction; involve the organization's administrator when required |
| Sign-in succeeds but new mail is missing | Mailbox selection, Inbox and Junk; last sync and sleep state through the API | Look for a controlled test message; request sync if appropriate |
| A registry workaround seems relevant | The guide's Outlook version and account type | Use current client-specific instructions rather than applying it to Mailera |
| A status check works but sending fails | Whether sending has been tested separately | Diagnose the send operation; do not treat a read check as proof of sending |

Do not disable MFA, repeatedly reset your password or delete the mailbox as a general troubleshooting sequence. First identify which operation is failing and which connection performs it.

## What does Mailera provide for Microsoft mailboxes?

Mailera provides an OAuth connection to your existing Microsoft mailbox, with separate connection and sync checks. The [Mailera product overview](https://mailera.app/en/product) explains how connected mailboxes become available to applications.

Mailera does not create new mailboxes or email addresses, and it does not connect Microsoft mailboxes using app passwords.

When sharing troubleshooting screenshots, hide account identifiers and unrelated mailbox contents. Never include API keys, refresh tokens or consent-session URLs.

**Connect your first mailbox in 2 minutes** — Add an Outlook, Gmail or IMAP mailbox and read email messages in the app or via the API. [Connect mailbox](https://mailera.app/auth?mode=signup)