Microsoft to Phase Out Legacy TLS 1.0 and 1.1 for Exchange Online Starting July 2026
Microsoft is set to retire support for outdated Transport Layer Security (TLS) protocols—specifically TLS 1.0 and TLS 1.1—for POP3 and IMAP4 connections to Exchange Online, a move that could disrupt email access for organizations still relying on legacy systems. The deprecation, announced by the company on April 27, 2026, is part of a broader effort to modernize security standards and align with industry best practices. Starting July 1, 2026, connections using these older protocols will be blocked, with the transition fully completed by December 31, 2026.

For most users, the change will go unnoticed, as modern email clients and applications already support TLS 1.2 or later. However, organizations with older integrations, custom applications, or aging hardware may face connectivity issues if they fail to update their systems in time. Microsoft has emphasized that the vast majority of POP and IMAP traffic to Exchange Online already uses the newer protocols, but those who have explicitly opted into legacy endpoints will need to seize action.
Why TLS 1.0 and 1.1 Are Being Phased Out
TLS is the encryption protocol that secures data transmitted over the internet, including emails. While TLS 1.0 and 1.1 were once standard, they are now considered insecure due to known vulnerabilities that can be exploited by attackers. TLS 1.2, introduced in 2008, and TLS 1.3, released in 2018, offer stronger encryption and are widely adopted across modern platforms. The industry has been moving away from the older versions for years, with major tech companies, including Microsoft, Google, and Apple, already deprecating support for TLS 1.0 and 1.1 in their services.
Microsoft’s decision to retire these protocols for Exchange Online follows a similar move in 2020, when the company began blocking TLS 1.0 and 1.1 for SMTP authentication in Exchange Online. The latest announcement extends this security measure to POP3 and IMAP4 connections, which are commonly used by email clients like Outlook, Thunderbird, and mobile apps to retrieve messages from servers.
Who Is Affected and What Happens If You Don’t Update
The deprecation will primarily impact organizations that rely on legacy email clients, custom applications, or embedded systems (such as older printers, scanners, or IoT devices) that connect to Exchange Online via POP or IMAP. If these systems are not updated to support TLS 1.2 or later, they will lose the ability to send or receive emails starting in July 2026. Microsoft has stated that there will be no fallback or warning when the block takes effect—connections will simply fail.

To determine if your organization is affected, Microsoft recommends checking the configuration of your POP and IMAP clients. If you’re unsure whether your systems support TLS 1.2, the company advises consulting your application or device vendor for upgrade guidance. Admins can also review their Exchange Online settings to identify any legacy connections still in use.
What Organizations Need to Do Now
Microsoft has outlined several steps organizations should take to prepare for the transition:
- Audit your email clients and applications: Identify any systems that rely on POP or IMAP to connect to Exchange Online and verify their TLS support. This includes not only email clients but also third-party applications, scripts, or devices that interact with email.
- Update or replace legacy systems: If any of your systems only support TLS 1.0 or 1.1, you’ll need to update them to a version that supports TLS 1.2 or later. In some cases, this may require upgrading hardware or software, or replacing outdated devices entirely.
- Test your connections: Before the July 2026 deadline, test your email clients and applications to ensure they can successfully connect to Exchange Online using TLS 1.2 or later. Microsoft provides documentation on how to configure POP and IMAP clients for modern TLS versions.
- Communicate with stakeholders: Inform your IT teams, helpdesk staff, and end-users about the upcoming change to avoid disruptions. If your organization relies on third-party vendors for email-related services, confirm that they are also prepared for the transition.
Microsoft has assured customers that the rollout will be gradual, with the block on legacy TLS connections taking effect between July 1 and December 31, 2026. The company has also emphasized that no action is required for organizations whose connections already use TLS 1.2 or later.
Why This Change Matters for Security
The deprecation of TLS 1.0 and 1.1 is a critical step in improving the security of Exchange Online and protecting users from potential cyber threats. Older TLS versions are vulnerable to attacks such as POODLE, BEAST, and downgrade attacks, which can allow attackers to intercept or manipulate data. By enforcing the use of TLS 1.2 or later, Microsoft is reducing the risk of data breaches and ensuring that email communications remain secure.
This move aligns with broader industry trends, as organizations worldwide phase out outdated encryption protocols. The National Institute of Standards and Technology (NIST) and other regulatory bodies have long recommended discontinuing the use of TLS 1.0 and 1.1 due to their security weaknesses. Microsoft’s decision reflects its commitment to maintaining a secure and modern email environment for its customers.
What Happens Next
Microsoft has stated that it will continue to communicate updates about the deprecation through its Exchange Team Blog and other official channels. Organizations are encouraged to monitor these updates and take proactive steps to ensure their systems are compliant before the July 2026 deadline.

For those who need assistance, Microsoft offers resources, including guidance on TLS configuration and support for troubleshooting connectivity issues. The company’s Microsoft 365 Roadmap provides visibility into upcoming changes and their timelines.
Key Takeaways
- Timeline: Microsoft will begin blocking TLS 1.0 and 1.1 for POP3 and IMAP4 connections to Exchange Online on July 1, 2026, with the transition completed by December 31, 2026.
- Who is affected: Organizations using legacy email clients, custom applications, or embedded systems that rely on TLS 1.0 or 1.1 for POP or IMAP connections.
- Action required: Audit your systems, update or replace legacy clients, and test connections to ensure they support TLS 1.2 or later.
- Why it matters: The change improves security by eliminating outdated encryption protocols that are vulnerable to cyberattacks.
- Where to find updates: Monitor Microsoft’s Exchange Team Blog and Microsoft 365 Roadmap for the latest information.
The next official update from Microsoft is expected as the July 2026 deadline approaches. In the meantime, organizations should prioritize updating their systems to avoid disruptions to email services. Have you checked whether your organization’s email clients support TLS 1.2 or later? Share your thoughts and experiences in the comments below.