Microsoft 365 SMTP Settings
The SMTP server, port and encryption for Microsoft 365 work mailboxes, how to turn on SMTP AUTH, and what to do when a printer or app still won't send.
Quick answer
Microsoft 365 server settings
- SMTP Outgoing STARTTLS
-
smtp.office365.comport 587
- IMAP Incoming SSL/TLS
-
outlook.office365.comport 993
- POP3 Download SSL/TLS
-
outlook.office365.comport 995
- Username
- The mailbox's full email address
- TLS
- TLS 1.2 or 1.3 required; port 465 is not supported
- Requirements
- A licensed mailbox with SMTP AUTH enabled
- Sending limits
- 10,000 recipients per day; 30 messages per minute
- Personal accounts
- Outlook.com uses smtp-mail.outlook.com instead
Microsoft 365 work and school mailboxes send mail from apps, printers and scanners through smtp.office365.com on port 587 with STARTTLS. Microsoft calls this SMTP AUTH client submission. It needs three things besides the right server name: a licensed mailbox, TLS 1.2 or later, and SMTP AUTH switched on for that mailbox. If any one is missing, sending fails even when the settings below are typed correctly.
These settings are for business mailboxes on Exchange Online. A personal Outlook.com, Hotmail or Live address uses different servers — see Outlook.com SMTP settings.
Microsoft 365 SMTP settings
| Setting | Value |
|---|---|
| Server | smtp.office365.com |
| Port | 587 (recommended) or 25 |
| Encryption | STARTTLS, using TLS 1.2 or TLS 1.3 |
| Authentication | Required |
| Username | The sending mailbox's full email address |
| Password | That mailbox's sign-in credentials — Microsoft recommends OAuth (modern authentication) |
| Sending limits | 10,000 recipients per day; 30 messages per minute |
Port 465 is not supported. Microsoft notes that a device or app that defaults to port 465 doesn't support the TLS versions client submission requires. Always enter the server name, not an IP address.
Before it will work
- A licensed mailbox. The account the device signs in with must be a licensed Microsoft 365 mailbox.
- SMTP AUTH enabled for that mailbox. Microsoft disables SMTP AUTH for organizations created after January 2020. An administrator can turn it on for individual mailboxes (steps below).
- TLS 1.2 or later. A device that can't negotiate TLS 1.2 can't use client submission at all. Check for a firmware update, or use SMTP relay instead.
- Security defaults off for this purpose. When security defaults are enabled in Microsoft Entra ID, SMTP AUTH is already disabled, and client submission with Basic authentication isn't compatible with them.
Turn on SMTP AUTH for one mailbox
Microsoft recommends keeping SMTP AUTH off for the organization and enabling it only for the mailboxes that still need it — for example, the account a scanner uses. An administrator can do this in either of two places.
In the Microsoft 365 admin center
- Go to Users > Active users and select the user.
- Select Mail, then Manage email apps.
- Check Authenticated SMTP and select Save changes.
In Exchange Online PowerShell
Set-CASMailbox -Identity scanner@contoso.com -SmtpClientAuthenticationDisabled $false
To check the result:
Get-CASMailbox -Identity scanner@contoso.com | Format-List SmtpClientAuthenticationDisabled
False means enabled, True means disabled, and a blank value means the mailbox follows the organization-wide setting. A mailbox setting always overrides the organization setting.
One more lock can still apply: if an authentication policy blocks Basic authentication for SMTP, clients can't use SMTP AUTH with a password even after this setting is enabled.
Passwords, OAuth and Basic authentication
Microsoft recommends OAuth for client submission. Basic authentication — a username and password stored on the device — is scheduled for deprecation in Exchange Online, and Microsoft has revised that schedule since first announcing it. Check Microsoft's current deprecation timeline before relying on a password-only setup, and plan for the device to move to OAuth or to one of the options further down.
Sending from a different address
If the From address isn't the mailbox the device signs in with — a shared address like invoices@, for example — the sign-in mailbox needs Send As permission for it. Without that, the message is refused with:
5.7.60 SMTP; Client doesn't have permissions to send as this sender
When SMTP AUTH isn't the right fit
Microsoft documents two other ways for devices and applications to send through Microsoft 365. Both connect to your domain's MX endpoint — in the form contoso-com.mail.protection.outlook.com — on port 25.
| Method | Sign-in | Can email | Licensed mailbox |
|---|---|---|---|
| SMTP AUTH (this page) | Mailbox credentials | Anyone | Required |
| Direct send | None | Your organization's Microsoft 365 recipients only | Not required |
| SMTP relay | Connector using a certificate or a static IP | Anyone | Not required |
Microsoft says most customers don't need direct send. SMTP relay needs an inbound connector and either a certificate or a static IP address that isn't shared outside your organization; dynamic IP addresses aren't allowed. For application mail that can't use OAuth, Microsoft points to High Volume Email for internal recipients, and Azure Communication Services Email when external recipients are involved.
If it still won't send
- Port 465 is set. Change to 587 with STARTTLS.
- Authentication is rejected. Confirm Authenticated SMTP is enabled for the mailbox, security defaults aren't blocking it, no authentication policy blocks Basic authentication for SMTP, and the mailbox is licensed.
- Error 5.7.60. The sign-in mailbox lacks Send As permission for the From address.
- TLS or connection errors on an older device. It may not support TLS 1.2. Update the firmware, or move the device to SMTP relay.
- Sending stops partway through a batch. Client submission is capped at 30 messages per minute and 10,000 recipients per day.
Not sure the domain is on Microsoft 365 at all? Enter the address in the Email Settings Finder — it reads the domain's mail records and tells you.
Incoming mail settings
To receive Microsoft 365 mail in an IMAP or POP client, use outlook.office365.com with port 993 and SSL/TLS for IMAP, or port 995 and SSL/TLS for POP. Use the full email address as the username, and leave Secure Password Authentication turned off. Accounts operated by 21Vianet in China use partner.outlook.cn for incoming mail and smtp.office365.cn for sending.
How this guide was checked · October 2026
Verified against 4 official sources
Every step, setting and limit in this guide was checked against the provider’s own documentation on learn.microsoft.com, support.microsoft.com and techcommunity.microsoft.com. Anything we couldn’t confirm was left out.
- 01 Microsoft Learn: Send email from a device or application using Microsoft 365 learn.microsoft.com
- 02 Microsoft Learn: Enable or disable SMTP AUTH in Exchange Online learn.microsoft.com
- 03 Microsoft Support: POP, IMAP and SMTP settings for Microsoft 365 support.microsoft.com
- 04 Microsoft Tech Community: SMTP AUTH Basic authentication deprecation timeline techcommunity.microsoft.com
Questions
Frequently asked questions
What is the SMTP server for Microsoft 365?
smtp.office365.com on port 587 with STARTTLS. The connection must use TLS 1.2 or TLS 1.3, and the device must sign in with a licensed Microsoft 365 mailbox that has SMTP AUTH enabled.
Can I use port 465 with Microsoft 365?
No. Microsoft does not support port 465 for client submission. A device or app that defaults to 465 doesn't support the TLS versions Microsoft 365 requires; switch it to port 587 with STARTTLS.
Why does my scanner say authentication failed even though the password is right?
Usually SMTP AUTH is switched off for that mailbox. Microsoft disables it for organizations created after January 2020, and it is also off whenever Microsoft Entra security defaults are enabled. An administrator can turn on Authenticated SMTP for the mailbox in the Microsoft 365 admin center.
What are the Microsoft 365 SMTP sending limits?
For SMTP AUTH client submission Microsoft lists 10,000 recipients per day and 30 messages per minute. Higher volumes need SMTP relay through a connector, or a dedicated sending service.
Is smtp.office365.com the same as smtp-mail.outlook.com?
No. smtp.office365.com is for Microsoft 365 work and school mailboxes. Personal Outlook.com, Hotmail and Live addresses use smtp-mail.outlook.com.
Related guides
Keep reading
Microsoft 365 Security
Microsoft 365 SPF, DKIM & DMARC Setup
Set up SPF, DKIM and DMARC for a custom domain in Microsoft 365: the exact SPF record for each Microsoft cloud, the two DKIM CNAMEs, and a safe DMARC rollout.
6 min read
Server Settings SMTP
SMTP Ports Explained: 587 vs 465 vs 25
Which email port to use: 587 with STARTTLS or 465 with SSL/TLS for sending, 25 only for server relay, and 993 or 995 for incoming mail. How to match encryption, test a port and fix errors.
7 min read
Server Settings SMTP
SMTP Server Settings for Every Email Provider
Outgoing SMTP server, port and encryption for Gmail, Outlook, Microsoft 365, Yahoo, iCloud and more — plus how to pick 587 or 465 and why your password is refused.
7 min read
Gmail SMTP
Gmail SMTP Settings
The current Gmail SMTP server, port, encryption and authentication requirements, plus focused fixes for failed authenticated outgoing mail submission.
4 min read
Outlook.com SMTP
Outlook.com SMTP Settings
The current Outlook.com SMTP server, port, encryption and authentication requirements, plus focused fixes for failed authenticated outgoing mail submission.
4 min read
Yahoo Mail SMTP
Yahoo Mail SMTP Settings
The current Yahoo Mail SMTP server, port, encryption and authentication requirements, plus focused fixes for failed authenticated outgoing mail submission.
4 min read