Article

Content

Office 365 SMTP Settings (2026): Server, Port 587, TLS & SMTP AUTH Setup Guide

Office 365 SMTP Settings (2026): Server, Port 587, TLS & SMTP AUTH Setup Guide

Office 365 SMTP Settings (2026): Server, Port 587, TLS & SMTP AUTH Setup Guide

Summarize with
Book more meetings with pre-warmed mailboxesReady-to-send Google & Microsoft inboxes in 5 minutes. US/EU IPs. No warmup wait.Get pre-warmed inboxes
4.8on G2
4.5on Trustpilot
Add as a preferred source on Google
Table Of Contents

Scanning page for headings…

Office 365 SMTP settings 2025 complete setup guide with Port 587 secure configuration by LiteMail

Office 365 and Microsoft 365 business mailboxes use smtp.office365.com for authenticated SMTP submission. The recommended configuration uses port 587 with STARTTLS and TLS 1.2 or TLS 1.3.

This guide explains the correct SMTP settings, OAuth 2.0 authentication, SMTP AUTH requirements, printer configuration, sending methods, troubleshooting and Microsoft's latest authentication changes.

Office 365 SMTP Settings (Quick Configuration)

Microsoft 365 and Office 365 business mailboxes use the same SMTP submission hostname. Use the following configuration for applications and devices that support authenticated SMTP submission.

Setting

Configuration

SMTP Server

smtp.office365.com

SMTP Port

587 (recommended)

Alternative Port

25 (where supported)

Encryption

STARTTLS

TLS Version

TLS 1.2 or TLS 1.3

Authentication

Required

Username

Full Microsoft 365 email address

Mailbox

Licensed Microsoft 365 mailbox

Authentication Method

OAuth 2.0 recommended

SMTP AUTH

Must be permitted by tenant and mailbox settings

Port 465

Not supported for this submission method

Important: Correct server and port settings do not automatically enable SMTP AUTH. Your Microsoft 365 administrator must ensure that the mailbox and organization policies permit the selected authentication method.

Office 365 vs Microsoft 365 SMTP Settings: Is There a Difference?

Office 365 and Microsoft 365 business email accounts use the same Exchange Online SMTP submission server. Although Microsoft changed its product branding, the SMTP hostname remains unchanged.

Setting

Office 365 Business

Microsoft 365 Business

SMTP Server

smtp.office365.com

smtp.office365.com

Port

587

587

Encryption

STARTTLS

STARTTLS

Authentication

Required

Required

Recommended Method

OAuth 2.0

OAuth 2.0

You do not need a separate SMTP hostname for Microsoft 365. Both services use Exchange Online for business email.

Note: Personal Outlook.com, Hotmail and Live accounts use different server settings. Do not confuse personal Microsoft accounts with Microsoft 365 business mailboxes.

Office 365 SMTP Sending Limits

Microsoft 365 applies sending limits to authenticated client SMTP submission to protect Exchange Online from excessive or abusive sending activity.

For client SMTP submission, Microsoft's published limits include:

Limit

Maximum

Recipients per day

10,000

Messages per minute

30

Recommended SMTP port

587

These limits apply to client SMTP submission and should not be treated as universal limits for every Microsoft 365 sending method.

SMTP Relay, Direct Send and High Volume Email have separate requirements and limitations.

Can You Use Office 365 SMTP for Cold Email?

Microsoft 365 SMTP is primarily designed for authenticated business communication and application-generated messages.

It is important to distinguish normal business email from large-scale unsolicited outreach. Correct SMTP configuration does not guarantee inbox placement or make a mailbox suitable for bulk cold email.

Businesses conducting legitimate outbound campaigns should evaluate mailbox policies, applicable anti-spam requirements, sending reputation and their overall email infrastructure before selecting a sending solution.

Common Office 365 SMTP Errors and How to Fix Them

Error or Problem

Possible Cause

Recommended Solution

5.7.57 Client not authenticated

SMTP AUTH disabled or authentication rejected

Check mailbox and organization SMTP AUTH settings

5.7.60 Client doesn't have permissions to send as this sender

Missing Send As permission

Grant the appropriate mailbox permission

Authentication failed

Invalid credentials or unsupported authentication method

Check OAuth configuration and tenant policies

STARTTLS handshake failure

Unsupported TLS version or client configuration

Update the device or application to support TLS 1.2 or later

Connection timeout

Port blocked by firewall or network

Check port 587 connectivity and firewall rules

4.7.500 Server busy

SMTP throttling

Reduce sending rate and implement appropriate retry delays

How to Troubleshoot SMTP Authentication

Start by checking whether the mailbox is licensed, SMTP AUTH is enabled where required, and the application supports the authentication method permitted by the tenant.

Next, review Exchange Online logs and the application's SMTP response. Correct the underlying configuration before attempting repeated connections.

Understanding Office 365 SMTP Basics

What is SMTP?

SMTP (Simple Mail Transfer Protocol) is the standard protocol used to send outgoing emails across the internet. In Microsoft 365, SMTP allows users, applications, and devices to send messages through Microsoft's mail servers securely.

When you send an email from Outlook, a CRM platform, a printer, or another application, SMTP handles the connection between your account and the recipient's mail server.

How SMTP Works in Office 365

Office 365 SMTP uses the server smtp.office365.com to process outgoing email requests. Before messages are delivered, Microsoft verifies the sender through authentication and encryption requirements to help prevent unauthorized sending and improve email security.

SMTP is commonly used for:

  • Sending emails from Outlook and other email clients

  • Connecting business applications and CRM platforms

  • Configuring printers and scanners for scan-to-email

  • Sending automated notifications from servers or software tools

A correct SMTP configuration ensures reliable email delivery, reduces connection errors, and helps maintain a trusted sender reputation.

SMTP vs IMAP vs POP3: Key Differences in Office 365

Understanding the difference between SMTP, IMAP, and POP3 helps you configure Microsoft 365 email correctly. Each protocol has a different role in email communication.

Protocol

Purpose

How It Works

SMTP

Sending emails

Sends outgoing messages from your Microsoft 365 account, application, or device to the recipient's mail server.

IMAP

Receiving and syncing emails

Keeps emails synchronized across multiple devices by storing messages on the mail server.

POP3

Downloading emails

Downloads emails from the server to a single device and may remove them from the server depending on settings.

Which Protocol Should You Use?

For most Microsoft 365 users:

  • Use SMTP for sending emails through Outlook, applications, printers, and automated systems.

  • Use IMAP when you need email synchronization across multiple devices.

  • Use POP3 only when you need to download emails to a specific device.

For business applications and automated email sending, SMTP is the required protocol because it handles outgoing email delivery securely through Microsoft 365 servers.

Stop Losing Emails to Spam — Get Pre-Warmed Inboxes
Ready to send from day 1. No warm-up wait. No extra tools needed.
Find Your Sending Domains →
100,000+ mailboxes · US & EU IPs · From $4.99/inbox

Why Proper SMTP Configuration Matters

Email Deliverability is Everything

When your SMTP settings are correct, your emails reach people's inboxes. When they're not? Bounced messages, spam folders, and lost business opportunities. Proper configuration dramatically reduces delivery failures and keeps your communications reliable.

Security Can't Be Ignored

SMTP servers are prime targets for hackers. A solid Office 365 SMTP setup protects you through:

  1. Better server authentication to stop unauthorized access

  2. Up-to-date encryption for data protection

  3. Strong password policies as an extra defense layer

One security breach could expose client information and damage your reputation that's why proper configuration is essential.

Stop Losing Emails to Spam — Get Pre-Warmed Inboxes
Ready to send from day 1. No warm-up wait. No extra tools needed.
Find Your Sending Domains →
100,000+ mailboxes · US & EU IPs · From $4.99/inbox

How to Set Up Office 365 SMTP Settings

Setting up Office 365 SMTP depends on where you want to send emails from. Microsoft 365 SMTP can be configured for email clients, business applications, printers, scanners, and other devices.

Before starting, make sure you have:

  • A valid Microsoft 365 email account

  • SMTP AUTH enabled if required

  • Port 587 available for outgoing connections

  • STARTTLS/TLS encryption supported by your application or device

Method 1: Configure Office 365 SMTP in Email Clients

To configure SMTP in an email client such as Outlook or another mail application, use these settings:

Outgoing SMTP Server: smtp.office365.com
Port: 587
Encryption: STARTTLS
Authentication: Required
Username: Your full Microsoft 365 email address
Password: Your Microsoft 365 password or app password (if MFA is enabled)

After entering the settings, send a test email to confirm the connection is working.

Method 2: Configure Office 365 SMTP for Applications

Many business tools such as CRMs, websites, monitoring systems, and automation platforms use SMTP to send emails.

Enter the following SMTP details:

  • SMTP Host: smtp.office365.com

  • SMTP Port: 587

  • Security: STARTTLS

  • Authentication: Enabled

  • Username: Microsoft 365 mailbox address

  • Password: Account password or app password

For applications that support modern authentication, Microsoft recommends using OAuth 2.0 instead of basic authentication.

Method 3: Configure Office 365 SMTP for Printers and Scanners

Printers and scanners often use SMTP for scan-to-email features.

Use:

  • Server: smtp.office365.com

  • Port: 587

  • Encryption: STARTTLS

  • Authentication: Required

If your device does not support TLS encryption or modern authentication, consider using an SMTP relay connector instead.

Method 4: Configure Office 365 SMTP Relay

SMTP Relay allows devices and applications to send email through Microsoft 365 without using a mailbox login.

SMTP Relay is commonly used for:

  • Printers

  • Copiers

  • Internal applications

  • Server notifications

To configure SMTP Relay:

  1. Open the Microsoft 365 Exchange Admin Center.

  2. Go to Mail Flow → Connectors.

  3. Create a new connector.

  4. Configure your trusted IP address or mail routing settings.

  5. Test email delivery from your device or application.

SMTP Relay is different from authenticated SMTP because it relies on connector settings instead of mailbox credentials.

Correct SMTP configuration is only one part of successful email delivery. Review our email deliverability checklist to understand the additional factors that influence sender reputation and inbox placement.

SMTP AUTH vs SMTP Relay vs Direct Send vs High Volume Email

Microsoft 365 offers different sending methods for applications, printers, scanners and automated email systems. The right option depends on whether you need authentication, external delivery, a mailbox or an Exchange connector.

Feature

Client SMTP Submission

SMTP Relay

Direct Send

High Volume Email

SMTP Host

smtp.office365.com

Your MX endpoint

Your MX endpoint

Microsoft HVE endpoint

Port

587 or 25

25

25

587

Authentication

OAuth or permitted SMTP AUTH

Connector using IP or certificate

None

HVE credentials or OAuth

External Delivery

Yes

Yes

No

No

Internal Delivery

Yes

Yes

Yes

Yes

Main Use

Applications and email clients

Devices and organizational systems

Internal notifications

High-volume internal messages

Which Method Should You Choose?

Client SMTP Submission: Choose this for applications that need to send messages to internal and external recipients through a licensed mailbox.

SMTP Relay: Choose this when an organizational device or application needs to send through an Exchange Online connector using an authorized static public IP or TLS certificate.

Direct Send: Choose this when an application only needs to send messages to recipients within your Microsoft 365 organization.

High Volume Email: Consider this for applications that need to send large volumes of messages to internal organizational recipients.

These methods are not interchangeable. Check Microsoft's current requirements before selecting one.

Need pre-warmed inboxes ready today? Litemail delivers Google Workspace & Microsoft 365 mailboxes with weeks of warm-up history built in.Check Available Domains →

Common Issues and How to Fix Them

Even with a reliable platform like Office 365 SMTP, setup challenges can occasionally arise. Understanding these common issues and how to resolve them ensures uninterrupted, secure, and efficient email delivery.

Authentication Errors
Authentication errors are among the most frequent problems users encounter during SMTP configuration. They usually stem from incorrect login credentials, expired passwords, or disabled authentication settings.

How to Fix:

  1. Double-check your username and password for accuracy.

  2. Ensure SMTP authentication is enabled in your Office 365 account.

  3. Activate multi-factor authentication (MFA) to enhance account security and reduce unauthorized access.

Port Configuration Problems
Port misconfiguration can prevent your emails from being sent successfully. Office 365 primarily uses Port 587 for secure transmission via TLS encryption. If this port is blocked by your firewall, emails may fail to deliver.

How to Fix

If issues persist, test with Port 25 as an alternative.
Verify that your SMTP settings are correctly aligned with Microsoft’s recommended configuration.

Connectivity Issues
Poor network connectivity or temporary server downtime can interrupt communication with the SMTP server, causing email delays or failures.

How to Fix:

Run a ping or traceroute test to check server accessibility.
Verify that your internet connection is stable.
Review server logs for detailed error messages to pinpoint the exact cause.
If problems continue, contact your network administrator or Microsoft support for advanced troubleshooting.

SMTP Authentication (SMTP AUTH) in Office 365 Explained

SMTP AUTH is the authentication method that allows applications, email clients, and devices to send emails through Microsoft 365 by signing in with a mailbox account.

When SMTP AUTH is enabled, the application connects to smtp.office365.com, provides the user's Microsoft 365 credentials, and sends email securely using SMTP submission.

Office 365 SMTP AUTH Requirements

Before using SMTP AUTH, check the following:

  • The mailbox must have SMTP AUTH enabled.

  • The application or device must support TLS encryption.

  • Port 587 should be used for secure email submission.

  • Multi-factor authentication (MFA) may require an app password or modern authentication support.

How to Enable SMTP AUTH in Office 365

To enable SMTP AUTH for a mailbox:

  1. Open the Microsoft 365 Admin Center.

  2. Go to Users → Active Users.

  3. Select the mailbox you want to configure.

  4. Open Mail settings.

  5. Enable SMTP AUTH.

  6. Save the changes and test the SMTP connection.

For organizations using Exchange Online, administrators can also manage SMTP AUTH settings through the Exchange Admin Center.

SMTP AUTH vs SMTP Relay vs Direct Send

Microsoft 365 provides different ways to send emails depending on your use case.

Feature

SMTP AUTH

SMTP Relay

Direct Send

Requires mailbox login

Yes

No

No

Uses SMTP authentication

Yes

No

No

Requires connector setup

No

Yes

No

Best for

Users, apps, email clients

Printers, devices, internal applications

Internal Microsoft 365 emails

External email delivery

Yes

Yes

No

SMTP AUTH

Best for:

  • Outlook and email clients

  • Business applications

  • Third-party tools

  • Automated email systems

SMTP AUTH uses a Microsoft 365 mailbox username and password to send messages.

SMTP Relay

Best for:

  • Printers

  • Scanners

  • Copiers

  • Internal business systems

SMTP Relay uses an Exchange Online connector and trusted IP addresses instead of mailbox credentials.

Direct Send

Direct Send allows devices and applications to send emails only to recipients inside your Microsoft 365 organization. It does not support sending messages to external email addresses.

Choosing the correct sending method depends on your device, application requirements, authentication support, and email delivery needs.

How to Enable SMTP AUTH in Microsoft 365

SMTP AUTH can be controlled at both the organization and individual mailbox levels. A mailbox-level setting can override the organization-wide setting.

Follow these steps:

  1. Sign in to the Microsoft 365 Admin Center.

  2. Navigate to Users → Active users.

  3. Select the mailbox you want to configure.

  4. Open the Mail tab.

  5. Find Email apps and select Manage email apps.

  6. Locate Authenticated SMTP.

  7. Enable the setting if your application requires SMTP AUTH and your organization's security policy permits it.

  8. Save your changes.

Important Administrative Considerations

  • SMTP AUTH can also be disabled across the organization through Exchange Admin Center settings.

  • Security Defaults disable SMTP AUTH in Exchange Online.

  • Authentication policies can block Basic Authentication even when SMTP AUTH is enabled.

  • Enabling SMTP AUTH does not mean that Basic Authentication is automatically permitted.

For security, enable SMTP AUTH only for mailboxes that genuinely require it.

How to Configure OAuth 2.0 for Office 365 SMTP

OAuth 2.0 allows supported applications to authenticate with Microsoft 365 without relying on traditional mailbox passwords.

For applications that support OAuth-based SMTP authentication, the general configuration process involves:

  1. Register an application in Microsoft Entra ID.

  2. Configure the appropriate SMTP permissions.

  3. Obtain administrator consent where required.

  4. Acquire an OAuth access token using the appropriate authentication flow.

  5. Connect to smtp.office365.com on port 587.

  6. Establish a STARTTLS connection.

  7. Authenticate using the XOAUTH2 mechanism.

  8. Send a test email and verify the result.

What Permissions Are Required?

The required permissions depend on the authentication flow.

For delegated authentication, configure the appropriate SMTP.Send permission and obtain user consent.

For unattended application authentication, the administrator must configure the SMTP.SendAsApp application permission, grant consent, register the service principal in Exchange Online and assign the necessary mailbox permissions.

Important: OAuth configuration does not automatically override SMTP AUTH restrictions. The organization and mailbox must still permit the relevant SMTP submission method.

Microsoft 365 SMTP AUTH Deprecation Timeline (2026–2027)

Microsoft is gradually moving Exchange Online SMTP AUTH away from Basic Authentication and toward Modern Authentication (OAuth 2.0).

According to Microsoft's January 2026 announcement, the updated timeline is:

Timeline

Microsoft Change

Through December 2026

Existing SMTP AUTH Basic Authentication behaviour remains unchanged

End of December 2026

Basic Authentication will be disabled by default for existing tenants

New tenants after December 2026

Basic Authentication will be unavailable by default

Second half of 2027

Microsoft will announce the final removal date

Existing tenant administrators will still be able to enable Basic Authentication after the December 2026 default change, where Microsoft permits it.

What Should Businesses Do?

  • Check which applications currently use Basic Authentication.

  • Identify devices that cannot support OAuth 2.0.

  • Update compatible applications to Modern Authentication.

  • Review mailbox-level SMTP AUTH settings.

  • Test the new authentication method before changing production systems.

Businesses should prepare their applications and devices before the default authentication changes take effect.

Source: Microsoft's Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline.

Litemail's pre-warmed Google Workspace & Microsoft 365 inboxes come with US/EU IPs, automated DNS, full admin access, and 4–12 weeks of warm-up history — all from $4.99/inbox. No separate warm-up tool needed.

Best Practices for SMTP Management

Keep your Office 365 SMTP running smoothly with these habits

  1. Regular Updates Keep settings current for security and efficiency

  2. Security Protocols Use latest encryption methods and secure authentication

  3. Monitor Logs Watch SMTP logs to catch issues early

  4. Capacity Management Check storage and speed regularly to prevent overload

  5. Verification Checks: Test settings periodically to ensure proper configuration

Security Tips for Office 365 SMTP

Protecting your email system should be a top priority

  • Always use TLS encryption for data in transit

  • Implement strong password policies across all accounts

  • Enable multi-factor authentication wherever possible

  • Regularly review and update connector settings

  • Monitor for suspicious activity in your logs

  • Limit SMTP relay permissions to only necessary users

Start Sending Cold Email Today — Not in 6 Weeks
Pre-warmed Google Workspace & Microsoft 365 inboxes. Automated DNS. US & EU IPs. From $4.99/inbox.
See Domains Ready to Send →
No credit card required · Setup in 5 minutes · Cancel anytime
Start Sending Cold Email — Pre-warmed inboxes from $4
Get Inboxes

Optimizing Email Performance

Get the most out of your Office 365 SMTP

  1. Use dedicated connectors for different application types

  2. Monitor delivery rates to identify potential issues early

  3. Set up proper SPF and DKIM records to improve deliverability

  4. Regular maintenance prevents small problems from becoming big ones

  5. Keep documentation of your settings for troubleshooting

Proper email authentication is essential for protecting your sending domain and establishing trust with receiving mail servers. Follow our guide to SPF, DKIM and DMARC setup to understand how these authentication protocols work together.

Get Fresh Email Inboxes — Set Up in 30 Minutes
Real Google Workspace and Microsoft 365 accounts on your domains. Automated DNS, SPF, DKIM and DMARC included.
Find Your Sending Domains →
Starts at $2.50/inbox · Automated DNS · No manual setup

Wrapping It Up

Getting your Office 365 SMTP settings right goes beyond just sending emails it safeguards your business and preserves client relationships. Proper configuration ensures smooth operations and prevents costly email issues. With LiteMail's step-by-step guidance, you can confidently set up, troubleshoot, and maintain your email system. Now, managing your email workflow is simpler, more reliable, and fully under your control

How to Test Your Office 365 SMTP Connection

After configuring your Microsoft 365 SMTP settings, test the connection before using it in a production application.

Follow these checks:

  1. Confirm that your application uses smtp.office365.com.

  2. Verify that port 587 is available on your network.

  3. Confirm that STARTTLS and TLS 1.2 or later are supported.

  4. Check whether SMTP AUTH is permitted for the mailbox.

  5. Verify that your selected authentication method is supported.

  6. Send a test email to an address you control.

  7. Check the SMTP response and message delivery status.

If the connection fails, review the application logs and Microsoft 365 authentication settings before changing ports or repeatedly retrying the connection.

A successful SMTP connection confirms that the sending application can communicate with the server. It does not guarantee that future messages will reach the recipient's inbox.

How to Test Your Office 365 SMTP Connection

After configuring your Microsoft 365 SMTP settings, test the connection before using it in a production application.

Follow these checks:

  1. Confirm that your application uses smtp.office365.com.

  2. Verify that port 587 is available on your network.

  3. Confirm that STARTTLS and TLS 1.2 or later are supported.

  4. Check whether SMTP AUTH is permitted for the mailbox.

  5. Verify that your selected authentication method is supported.

  6. Send a test email to an address you control.

  7. Check the SMTP response and message delivery status.

If the connection fails, review the application logs and Microsoft 365 authentication settings before changing ports or repeatedly retrying the connection.

A successful SMTP connection confirms that the sending application can communicate with the server. It does not guarantee that future messages will reach the recipient's inbox.

Frequently Asked Questions About Office 365 SMTP Settings

What are the correct Office 365 SMTP settings?

The correct Office 365 SMTP settings are:

  • SMTP Server: smtp.office365.com

  • Port: 587

  • Encryption: STARTTLS

  • Authentication: Required

  • Username: Your full Microsoft 365 email address

These settings allow secure email sending through Microsoft 365 applications, email clients, and supported devices.

What is the SMTP server for Office 365?

The Office 365 SMTP server is smtp.office365.com. Microsoft recommends using this server with Port 587 and STARTTLS encryption for secure SMTP submission.

What port does Office 365 SMTP use?

Office 365 SMTP uses Port 587 with STARTTLS encryption. Port 587 is the recommended option because it provides secure email transmission and authentication.

How do I enable SMTP AUTH in Office 365?

To enable SMTP AUTH:

  1. Open the Microsoft 365 Admin Center.

  2. Select the required mailbox.

  3. Open mail settings.

  4. Enable authenticated SMTP.

  5. Save changes and test the connection.

SMTP AUTH may also be controlled by organization-wide Exchange Online settings.

Why is my Office 365 SMTP not working?

Common reasons include:

  • Incorrect SMTP username or password

  • SMTP AUTH disabled

  • Wrong port or encryption settings

  • MFA requiring an app password

  • Device not supporting TLS encryption

Check that your configuration uses smtp.office365.com, Port 587, and STARTTLS.

Can I use Office 365 SMTP for bulk email sending?

Microsoft 365 SMTP has sending limits and is designed mainly for normal business communication, applications, and notifications.

For large cold email campaigns or high-volume outreach, a dedicated email infrastructure is usually more suitable.

What is the difference between SMTP AUTH and SMTP Relay in Office 365?

SMTP AUTH requires a mailbox username and password to send emails.

SMTP Relay uses Exchange Online connectors and trusted IP addresses, making it better for devices such as printers, scanners, and internal applications.

Can I use Office 365 SMTP with printers and scanners?

Yes, but the device must support SMTP authentication and TLS encryption.

For older printers or scanners that cannot support modern security requirements, Microsoft 365 SMTP Relay may be a better option.

Does Office 365 SMTP support Port 465?

No. Standard Office 365 SMTP submission uses Port 587 with STARTTLS encryption. Port 465 is not the recommended configuration for Microsoft 365 SMTP.

How can I improve Office 365 email deliverability?

To improve deliverability:

  • Configure SPF records

  • Enable DKIM signing

  • Publish DMARC policies

  • Maintain a good sender reputation

  • Monitor bounce rates and email activity

Can I use Office 365 SMTP without SMTP AUTH?

Yes, but it depends on the sending method. Microsoft 365 Direct Send does not require SMTP AUTH, but it only supports sending messages to recipients within your organization. SMTP Relay uses an Exchange Online connector and an authorized IP address or TLS certificate. For authenticated client SMTP submission, SMTP AUTH must be permitted.

How do I find my Microsoft 365 SMTP server address?

For Microsoft 365 business mailboxes, the SMTP submission server is smtp.office365.com, normally using port 587 with STARTTLS. You can confirm the configuration in Microsoft's official SMTP settings documentation.

Need Microsoft 365 Inboxes for Your Outbound Email Operations?

LiteMail provides official Microsoft 365 and Google Workspace business inboxes with automated DNS configuration and infrastructure options for outbound email workflows.

Explore LiteMail's Microsoft 365 inbox solutions and find an email setup that fits your sending requirements.

Explore Microsoft 365 Email Inboxes

Businesses managing multiple outbound email accounts should also understand the role of cold email infrastructure, including mailbox provisioning, domain configuration and sending environment management.

Stop Losing Emails to Spam — Get Pre-Warmed Inboxes
Ready to send from day 1. No warm-up wait. No extra tools needed.
Find Your Sending Domains →
100,000+ mailboxes · US & EU IPs · From $4.99/inbox

Final Thoughts

Setting up Office 365 SMTP correctly ensures your applications, email clients, and business devices can send messages securely and reliably. Using the correct configuration smtp.office365.com, Port 587, STARTTLS encryption, and proper authentication — helps prevent connection issues and improves email security.

For regular business communication, Microsoft 365 SMTP provides a reliable solution. However, organizations sending high-volume outreach or cold email campaigns should use dedicated email infrastructure designed for deliverability, inbox management, and sender reputation protection.

If you need Microsoft 365 mailboxes built for reliable sending with proper infrastructure, LiteMail provides pre-configured Microsoft 365 inboxes with setup support and deliverability-focused features.

Book more meetings with pre-warmed mailboxesReady-to-send Google & Microsoft inboxes in 5 minutes. US/EU IPs. No warmup wait.Get pre-warmed inboxes
4.8on G2
4.5on Trustpilot
Add as a preferred source on Google

Share

Share LiteMail automated email setup on Twitter (X)
Share LiteMail email marketing growth strategies on Facebook
Share LiteMail inbox placement and outreach analytics on LinkedIn
Share LiteMail cold email infrastructure on Reddit
Share LiteMail affordable business email plans on Pinterest
Share LiteMail deliverability optimization services on Telegram
Share LiteMail cold email outreach tools on WhatsApp
Share Litemail on whatsapp
FREESearch pre-warmed domains for freeReady-to-send inboxes that land in the inbox, not spam.Search now
FREESearch pre-warmed domains for freeReady-to-send inboxes that land in the inbox, not spam.Search now
FREESearch pre-warmed domains for freeReady-to-send inboxes that land in the inbox, not spam.Search now