Aktuelle Microsoft 365-Ankündigungen direkt aus dem Admin Center - Bereich "Message Center"
Aktualisierung täglich um 12:00 Uhr
200 Einträge · Seite 17 von 34
stayInformednormalMC1218691
Initial deployment phase for Kerberos RC4 hardening begins with the January 2026 Windows security update
Geändert
Services
Windows
Windows updates released on and after January 13, 2026, introduce the first phase of protections addressing a Kerberos information disclosure vulnerability (CVE‑2026‑20833). These updates introduce new auditing and optional registry controls that devices can use to begin reducing reliance on RC4 encryption. They also help prepare domain controllers for a future shift to AES‑SHA1 as the default Kerberos encryption method for accounts without explicit encryption settings. The initial deployment phase focuses on identifying misconfigurations or dependencies before the second deployment phase begins in April 2026.When this will happen:The initial deployment phase starts January 13, 2026, and introduces new Kerberos audit events that help identify any remaining RC4 dependencies across your environment. This phase also adds the temporary RC4DefaultDisablementPhase registry value, which organiz
planForChangenormalMC1218421
Retirement of Power BI Q&A
Major Change
Geändert
Services
Power BI
Introduction We are announcing the retirement of Q&A, Power BI’s legacy natural language tool. Starting December 2026, Q&A experiences will be retired. Moving forward, users can leverage Power BI Copilot, which offers a more advanced and integrated solution for querying data using generative AI. This change reduces feature overlap, accelerates innovation, and provides a consistent experience across Power BI. When this will happen:Q&A experiences and Q&A Setup will be fully retired by the end of December 2026.How this affects your organization: Who is affected: All organizations using Q&A experiences in Power BI reports, dashboards, mobile, or embedded analytics. What will happen: Creation of new Q&A visuals or experiences will no longer be permitted after December 2026. Existing Q&A visuals in reports, dashboards, mobile, and embedded scenarios will stop working and will be removed. Q&A
stayInformednormalMC1217951
Windows Backup for Organizations expands to first sign-in restore
Geändert
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
stayInformednormalMC1217584
Windows Deployment Services (WDS): Hands-free deployment hardening (Phase 1)
Major Change
Geändert
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
stayInformednormalMC1217507
The January 2026 Windows security update is now available
Major Change
Geändert
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
stayInformednormalMC1216196
Hardening changes coming to Common Log File System (CLFS) authentication
Geändert
Services
Windows
A new hardening authentication mitigation has been introduced for the Common Log File System (CLFS) driver. Windows updates that include this new version of CLFS will initiate a 90 day "learning mode" period during which authentication codes will be added to log files automatically. Device behavior will change after this period. For more information, see Common Log File System (CLFS) Authentication Mitigation.When will this happen:Windows 11, version 25H2 and Windows Server 2025 updates released on or after October 28, 2025 include this change. A mitigation adoption period, referred to as "learning mode" will be in place for 90 days following installation of updates. During this time, authentication codes are automatically added to existing logfiles when they are opened. After this period ends, the CLFS driver will enter enforcement mode, requiring all logfiles to contain valid authentic