M365 Message Center

Geändert

15.07.2026

Services

Exchange Online

Updated July 15, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft is retiring the -Credential parameter used when connecting to Exchange Online PowerShell. Starting with module versions released in December 2026 and later, the -Credential parameter will be removed from both Connect-ExchangeOnline and Connect-IppsSession cmdlets. Organizations using this parameter in automation scripts must migrate to a supported authentication method before that date. This change improves security by moving away from legacy authentication methods that do not support modern protections such as multifactor authentication (MFA). [When this will happen:] The -Credential parameter will be removed from Connect-ExchangeOnline and Connect-IppsSession cmdlets in Exchange Online PowerShell module versions released beginning end of year 2026 (previously July). A separate ser

Geändert

14.07.2026

Services

Microsoft Purview

Updated July 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Purview is introducing Classifier Simulation Mode, the first phase of the broader Classifier Health Monitoring Platform. This new capability allows admins to test and validate custom classifiers on production data before publishing. Simulation Mode enables admins to optimize classifier logic before deployment, helping in reducing false positives, scanning latency, and noisy matches. Admins will access simulation controls and classifier health insights directly in the Microsoft Purview compliance portal, making it easier to monitor and improve classifier performance in one centralized location. This message is associated with Roadmap ID 523201. [When this will happen:] Public Preview: Rollout begins mid-October 2026 (previously late June), completes by early November 2026 (previously

Geändert

09.07.2026

Services

Microsoft Viva · Microsoft Copilot (Microsoft 365)

Updated July 9, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Agent in Viva Engage communities are now available in Public Preview. Community admins can add agents to communities to help draft answers to questions without best or verified answers based on community content and add context to posts by answering follow up questions using the community's conversations and SharePoint site and library. We’re now adding the option for community admins to specify additional SharePoint sites outside the community as grounding sources. The agent will only use sites that community admins select, and it drafts answers from items that community members can view (Read). We are also adding a new capability: tagging by community members. Tagging by community members enables Microsoft 365 copilot-licensed users to @-mention the community agent in the comments and replie

Geändert

08.07.2026

Services

Microsoft Viva

Updated July 8, 2026: We have updated the content and timeline. Thank you for your patience. We’re introducing My Team audiences and expanded targeting capabilities in Viva Engage to help leaders communicate with the employees in their organization and tailor messages to relevant teams, departments, locations, or groups. My Team provides a ready-to-use, automatically maintained audience based on the organizational hierarchy, so leaders can reach the employees who report up to them, including both direct and indirect reports. This audience helps unlock and improve leadership experiences across Viva Engage, making Storyline Announcements, audience analytics, Leadership Corner, and feed and digest distribution more relevant with less setup. Leaders and delegates can use My Team as-is, review its membership, or further customize and save it as a reusable audience across leader communication

Geändert

07.07.2026

Handlung bis

31.07.2026

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

Geändert

06.07.2026

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