Microsoft 365

M365 Message Center

Aktuelle Microsoft 365-Ankündigungen direkt aus dem Admin Center - Bereich "Message Center"

Aktualisierung täglich um 12:00 Uhr

200 Einträge · Seite 12 von 34

planForChange normal MC1225192

Microsoft Entra ID Governance: Azure subscription required to continue using guest governance features

Major Change
Geändert
Services
Microsoft Entra

Introduction Beginning January 30, 2026, Microsoft Entra ID Governance will require all tenants to have a linked Azure subscription to continue using Identity Governance features for guest users. This change ensures accurate billing for governance actions performed by guests and supports continued access to advanced governance capabilities. When this will happen: General availability and enforcement begin on January 30, 2026. How this will affect your organization: Who is affected: Organizations using Microsoft Entra ID Governance features for guest users (userType = Guest). Admins managing lifecycle workflows or Entra ID Governance features in entitlement management for external or guest identities. Access reviews will be included by March 31, 2026. What will happen: If your tenant does not have a linked Azure subscription, creation or updates of policies scoped to guest users using pre

stayInformed normal MC1275343

Hardening administrative actions: Windows imaging, cloning, and auth workflows

Geändert
Services
Windows

Administrative actions are undergoing hardening changes that might require operational change to support your organization’s security posture. With the August 2025 Windows non-security update, devices were hardened against unauthorized attempts to bypass loopback detection. However, if you’ve cloned machines without Sysprep, you might see Kerberos and NTLM authentication failures. This is by design. The recommended solution is to rebuild affected devices using supported imaging methods. A temporary workaround is also available. When will this happen:September 2025 and later: Windows security updates include hardening changes that strengthen the trust boundary between identity, authentication, and User Account Control (UAC).April 2026 and later: Windows security updates include a temporary workaround for machines cloned without Sysprep. This registry-based compatibility option isn’t recom

stayInformed normal MC1275342

Windows Office Hours: April 16, 2026

Geändert
Services
Windows

If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions.Want to attend the April 16 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you.

stayInformed normal MC1274396

Extended Security Updates (ESU) available for Windows 10 Enterprise LTSB 2016

Geändert
Services
Windows

If your organization relies on Windows 10 Enterprise LTSB 2016, you know it’s nearing end of support on October 13, 2026. While the long-term solution is upgrading to a newer LTSC release, another temporary solution is available as of April 1, 2026. Extended Security Updates (ESU) are now available for purchase through Volume Licensing or a Microsoft Cloud Solution Provider (CSP).When will this happen:October 13, 2026: Devices on Windows 10 Enterprise LTSB 2016 will receive a final monthly security update. This date marks end of support (EOS) for this product.April 1, 2026: Extended Security Updates (ESU) are available as a temporary bridge to your next step.How this will affect your organization:After October 13, 2026, these devices will no longer receive Windows security updates, non-security updates, bug fixes, technical support, or online technical content updates. If your organizati

stayInformed normal MC1274349

ESR management is moving to Windows Backup for Organizations

Geändert
Services
Windows

Starting May 2026, Enterprise State Roaming (ESR) management will transition to Windows Backup for Organizations. Windows Backup for Organizations is the enterprise‑grade solution for backing up and restoring Windows user settings and Microsoft Store app list. It’s designed to support device refresh, replacement, and upgrade scenarios (for example, moving to the latest version of Windows 11). ESR settings remain the same in scope. The only change is in how you manage these settings. This change aligns ESR‑managed settings with Windows Backup for Organizations policies. You can now manage and synchronize user settings with a policy‑based experience through Microsoft Intune or other mobile device management (MDM) providers. When will this happen:This change begins May 2026. You can manage ESR settings through both the Microsoft Entra portal and Windows Backup for Organizations policies for

stayInformed normal MC1269727

Replacement of the Microsoft SaRA command-line utility in Windows

Geändert
Services
Windows

Migrate away from the Microsoft Support and Recovery Assistant utility (SaRA). This command-line utility is deprecated to help secure and harden your environment. The Get Help command-line tool has similar capabilities and is recommended as a replacement for the SaRA utility. You’ll need to download it and use GetHelpCmd.exe to run your scenarios. When will this happen: March 10, 2026: Microsoft has officially removed the SaRA utility from all in-support versions of Windows. The Get Help command-line tool has been available for some time now. How this will affect your organization: The infrastructure powering GetHelpCmdLine includes improved security. The core functionality of GetHelpCmdLine and SaraCmdLine remains the same. All the scenarios supported in SaRACmdLine tool are supported as-is in GetHelpCmdLine. All SaRA scripts are migrated to GetHelpCmdLine. These scripts no longer work