M365 Message Center

Geändert

20.03.2026

Services

Microsoft Copilot (Microsoft 365)

Updated March 20, 2026: We have updated the timeline below. Thank you for your patience.Introduction We’re introducing a new request and approval experience in the Microsoft 365 admin center for Microsoft agents. This update enables users to request access to agents—even those currently unavailable due to your organization’s configuration—directly from the Agent Store. You can manage these requests centrally from the Copilot > Agents & connectors page in the Microsoft 365 admin center, streamlining access control and improving visibility into user interest.Note: This request flow applies exclusively to agents built by Microsoft and does not extend to other agents available in the store. This message is associated with Microsoft 365 Roadmap ID 494809. When this will happen Rollout will begin July 2026 (previously early March) and is expected to complete by end of July 2026 (previously end

Geändert

20.03.2026

Services

Exchange Online

In 2018, we announced that we were no longer making feature updates to Exchange Web Services (EWS) in Exchange Online, and we advised developers to move to Microsoft Graph. In September 2023, we announced that on October 1, 2026, we will start blocking EWS requests to Exchange Online. We are now less than 12 months from October 1, 2026. We have made progress on closing most parity gaps with more changes in development to be released in the coming quarters. Please refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information. You are receiving this notification because there are EWS applications in your tenant. If you haven't already, start the process of working with your application development organization and your application vendors to either sunset or migrate active EWS applications on your tenant to the Graph API, Power Platform, o

Geändert

20.03.2026

Services

Windows

Updated March 20, 2026: Added additional guidance for devices using Azure Files SMB with Active Directory–based authentication and Azure Virtual Desktop.Windows updates released April 2026 and later introduce the second deployment phase of protections for a Kerberos information disclosure vulnerability (CVE‑2026‑20833). In this phase, domain controllers change default Kerberos ticket behavior for accounts that do not have an explicit Kerberos encryption configuration, shifting to AES‑SHA1-only by default. Environments with remaining RC4 dependencies may experience authentication issues unless those dependencies are remediated or explicitly configured.When this will happen:April 2026 - Enforcement Phase with manual rollback: Default Kerberos behavior changes so domain controllers use AES‑SHA1-only encryption for accounts without explicit encryption type settings, and Enforcement mode is e

Geändert

16.03.2026

Services

Microsoft Teams

Introduction To improve reliability, compliance, and collaboration, we’re updating where Microsoft Whiteboard files created from a Teams Channel tab are stored. Previously, these whiteboards were saved in the OneDrive of the user who created them, which could lead to access issues due to sharing settings, Information Barriers, or Conditional Access policies. With this update, whiteboards created from Teams Channels will be stored in the associated SharePoint site for the channel, aligning Whiteboard with the storage behavior of other Microsoft 365 apps and ensuring consistent access for all channel members. When this will happen: We will begin rolling out this change in late September 2026. How this affects your organization: Who is affected: All Microsoft Teams users who create or collaborate on Whiteboards using the Teams Channel tab app What will happen: Whiteboards created from a Tea

Geändert

16.03.2026

Services

Microsoft Teams

[Introduction] Teams Phone user multi-line provides greater flexibility for organizations whose users manage multiple business numbers. This capability allows administrators to assign up to 10 telephone numbers to a single Teams Phone user, all within one Teams account. Users can make and receive calls from multiple numbers across Teams desktop, Teams mobile, and Teams devices without switching accounts or hardware. This enhancement supports a familiar and localized calling experience for users who work across regions, roles, or business lines. This capability supports scenarios such as: Establishing local presence across multiple regions Supporting users with multiple roles or responsibilities Allowing executives, assistants, or support teams to manage multiple business lines within one Teams account This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for

Geändert

16.03.2026

Services

Windows

Microsoft has identified an issue affecting hotpatch-enabled Enterprise editions of Windows where Bluetooth devices may not appear on the Bluetooth & devices page in Windows Settings or in Quick Settings, even though the devices are connected and functioning as expected. In addition, users might be unable to add Bluetooth devices because available devices do not appear in the connection list.This issue was identified in Microsoft’s internal environment and is expected to affect a limited set of Enterprise devices running Windows hotpatch updates.An out-of-band (OOB) hotpatch update (KB5084897) was released today, March 16, 2026, to address this issue. This cumulative update includes all protections and improvements from the March 2026 Windows hotpatch updates released on March 10 and March 13, 2026.This OOB hotpatch update is offered only to hotpatch‑enabled Windows 11, versions 25H2 and