(Updated) Exchange Online: Retirement of legacy TLS versions for POP and IMAP connections
Major Change
Geändert
Handlung bis
Services
Exchange Online
Updated July 7, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are retiring support for legacy Transport Layer Security (TLS) versions for POP3 and IMAP4 connections to Exchange Online. This change improves security and aligns with current industry standards. TLS 1.0 and TLS 1.1 are no longer considered secure. Most modern email clients already use TLS 1.2 or later. [When this will happen] Rollout start: August 1, 2026 Rollout end: December 31, 2026 The rollout will occur gradually worldwide. [How this affects your organization] Who is affected Microsoft 365 tenants using POP3 or IMAP4 with Exchange Online Admins managing email clients, applications, or devices that use POP or IMAP What will happen POP3 and IMAP4 connections will require TLS 1.2 or later. Connections using TLS 1.0 or TLS 1.1 will fail. Modern email clients are not expected to be affect
stayInformednormalMC1218713
(Updated) Microsoft Teams: Organization evaluation score for apps and agents
Geändert
Services
Microsoft Teams
Updated July 6, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Today, admins must manually review trust and compliance information for Teams apps and agents to determine whether they meet their organization’s security, privacy, and compliance requirements. To make this process more scalable and consistent, Teams will introduce a centralized evaluation experience. Admins will define their organization’s trust requirements once, and the system will generate a score and detailed evaluation report for each app and agent based on those requirements. This will help organizations make faster, more consistent approval decisions. This message is associated with Microsoft 365 Roadmap ID 532720. [When this will happen] Targeted release/Preview: We will begin rollout in late February 2026 and expect to complete by the end of March 2026. General Availability (Worldwid
stayInformednormalMC1219793
(Updated) Brand impersonation protection for Teams Calling
Geändert
Services
Microsoft Teams
Updated May 5, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Brand Impersonation Protection for Teams Calling adds proactive safeguards against fraudulent or deceptive external callers who attempt to appear as trusted organizations. This helps reduce social-engineering risks and improves tenant security when users receive first-contact external calls. This update aligns with Microsoft’s ongoing investments in caller identity protection and secure collaboration. This message is associated with Microsoft 365 Roadmap ID 543239. [When this will happen:] Targeted Release: Rollout will begin mid-May 2026 (previously early May) and is expected to complete by late May (previously late April). General Availability: Timelines will be communicated in a future message. [How this affects your organization:] Who is affected: All organizations using Microsoft Teams Cal
stayInformednormalMC1289724
(Updated) Microsoft Teams: Sharing recap access
Geändert
Services
Microsoft Teams · Microsoft Copilot (Microsoft 365)
Updated June 16, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Teams is introducing enhanced recap sharing. Meeting organizers can grant access to meeting recordings, transcripts, AI-generated summaries, and notes when copying or sharing a recap link. This update improves how meeting content can be shared with people who were not part of the original meeting. This message is associated with Microsoft 365 Roadmap ID 559606. [When this will happen:] Targeted Release: We will begin rolling out in late May 2026 (previously mid-May) and expect to complete by end of May 2026 (previously mid-May). General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by early June 2026. General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by late June 2026. General Availability
planForChangenormalMC1193415
(Updated) Microsoft Teams: Find SharePoint agents in Teams chats and Teams Store
Major Change
Geändert
Services
Microsoft Copilot (Microsoft 365)
Updated June 12, 2026: We have updated the timeline. Thank you for your patience. With this release, users can discover and add SharePoint agents directly within Microsoft Teams chats on Desktop and Mac. Agents can be added via the Add Agents and Bots option in the chat roster dropdown, which opens the in-context store for discovery and selection. This enables users to quickly bring SharePoint agents into conversations to support collaboration. Additionally, SharePoint agents are available in the Teams Store under the Agents category, making them easier to find and deploy across Teams experiences. This message is associated with Microsoft 365 Roadmap ID 515465. [When this will happen] Targeted Release: Rolling out in mid-October 2026 (previously mid-July) and expected to complete in late October 2026 (previously late July). General Availability: Rolling out in late October 2026 (previous
planForChangenormalMC1191578
(Updated) Update to EWS Access for Kiosk / Frontline Worker Licenses
Major Change
Geändert
Services
Exchange Online
Updated June 10, 2026: We have updated the timeline. Thank you for your patience. We're making some changes to Exchange Web Services (EWS). Starting October 1, 2026 (previously June 30), we will start to block EWS access for all mailboxes without license rights to EWS. This is another step in our ongoing commitment to enhance the security and control mechanisms of EWS. [How this will affect your organization:] The impacted licenses are: Exchange Online Kiosk Microsoft 365 and Office 365 F1 Microsoft 365 and Office 365 F3 As stated in the Service Descriptions, these licenses do not provide access to mailboxes via EWS, but these restrictions were never enforced. With this change, EWS access for users with only these license types will be blocked. [What you need to do to prepare:] If you wish these users to continue to use EWS, and your users are licensed with one of these noted above, you’