M365 Message Center

Geändert

02.02.2026

Handlung bis

01.07.2026

Services

Exchange Online

Updated February 2, 2026: We have updated the timeline. Thank you for your patience. We’re making some changes to DNS provisioning of A records for all new Accepted Domains provisioned after July 1st, 2026 (previously February 1st). Between early and late July 2026 (previously February), we will gradually switch provisioning of all A records for new Accepted Domains into the new subdomains under mx.microsoft.We are doing this to reduce the friction of adopting DNSSEC in the long run. DNSSEC is a set of extensions to DNS that provides cryptographic verification of DNS records, preventing DNS spoofing and adversary-in-the-middle attacks to DNS. [How this will affect your organization:] After July 1, 2026 (previously February 1), all A records for new Accepted Domains will be provisioned into the new subdomains under mx.microsoft. July 1, 2026 (previously February 1) if not secured with DNS

Geändert

30.01.2026

Services

Microsoft 365 apps

Updated January 30, 2026: Updated January 30, 2026: No new updates on this feature rollout yet. We expect to share a status update by the end of March. In the meantime, we have updated the Conditional Access Policy and Office Deployment documentation with a note that Conditional Access Policies may block Microsoft 365 self-installs.The My account portal will be replaced by a new modal dialog within the Microsoft 365 Copilot app (formerly Office.com) on web and desktop. The new modal will support end user self-installs that are currently available on the My account portal (Office, Project, Visio, and Skype for Business).[When this will happen:] Targeted Release: We will communicate via Message center when we are ready to proceed.General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.[How this will affect your organization:]End users will be a

Geändert

29.01.2026

Services

SharePoint Online

Updated January 29, 2026: We are updating this post as a reminder. Upcoming SharePoint Online changes may impact your organization. Please review the below.We are implementing the following changes to custom scripting and classic publishing in SharePoint Online.1. Disablement of custom scriptingCustom scripting will be disabled by default (setting DenyAddAndCustomizePages to 1 or $true) for sites created with the following templates:BLANKINTERNETCONTAINER#0 = Classic Publishing Portal Site CMSPUBLISHING#0 = Classic Publishing Site BLANKINTERNET#0 = Classic Publishing Site BlankCSPCONTAINER#0 = SharePoint Embedded SiteNOTE: Existing classic publishing sites created with the templates listed above will have custom scripting disabled by default. Disabling custom scripting does not affect the execution of scripts that have already been added to a site or page.Refer to this documentation to l

Geändert

14.01.2026

Services

Windows

Preview the expanded Windows Backup for Organizations experience! In early 2026, if users miss the restore option during the out-of-box experience (OOBE) by accident or due to a technical issue, they can still restore at first sign-in. Windows Backup for Organizations helps preserve Windows settings, the list of installed Microsoft Store apps, and the Start menu pins. And now, even more devices can take advantage of this capability, including Microsoft Entra hybrid joined, multi-user setups, and Windows 365 Cloud PCs. When will this happen: The opportunity to sign up for private preview is open now and until February 13, 2026. First sign-in restore will become generally available in early 2026. How this will affect your organization: Windows Backup for Organizations helps your organization upgrade, migrate, or refresh Windows devices. First sign-in restore experience expands its benefits

Geändert

13.01.2026

Services

Windows

Prepare for a two-phase hardening change related to CVE-2026-0386. The Unattend.xml file that underlies the hands-free deployment feature of Windows Deployment Services (WDS) poses a vulnerability when it’s transmitted over an unauthenticated RPC channel. Starting with the January 2026 security update, you can explicitly disable it with the help of new Event Log alerts and registry key options. In April 2026, hands-free deployment will be disabled by default. After that date, it will no longer work unless explicitly overridden with registry settings. When will this happen:January 2026 security update: Phase 1 of hardening begins. Hands-free deployment continues to be supported and can be explicitly disabled to enhance security. Use the new Event Log alerts and registry key options.April 2026 security update: Phase 2 of hardening follows. Hands-free deployment will be disabled by default

Geändert

13.01.2026

Services

Windows

The January 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5072033 (released December 9, 2025).This update makes quality improvements to the servicing stack, which is the component that installs Windows updates.This update addresses an issue where you might experience RemoteApp ​​​​​​​connection failures in Azure Virtual Desktop environments. This might occur after installing KB5070311.This update addresses an issue where devices wit