M365 Message Center

Geändert

25.11.2025

Services

Microsoft 365 apps

Updated November 25, 2025: This change is currently on hold. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience this may have caused and thank you for your patience. Introduction To enhance workbook security, a new group policy is being introduced to expand File Block Settings to external workbook links. This policy allows administrators to control whether links to blocked file types can be refreshed. If not configured, no changes will take effect immediately. However, starting November 2025, the default behavior will block external links to file types currently blocked by the Trust Center. When this policy is enabled, new references to blocked file types will return a #BLOCKED error. Existing links will display the last successfully refreshed values but will no longer refresh. When this will happen General Availability: We will update

Geändert

21.11.2025

Services

Windows

If you manage Windows Servers, plan for removal of Windows Internet Name Service (WINS). WINS was officially deprecated since Windows Server 2022 and will be removed from all Windows Server releases following Windows Server 2025. Standard support will continue through the lifecycle of Windows Server 2025, until November 2034. We encourage you to migrate to modern Domain Name System (DNS)-based name resolution solutions before then. When will this happen: WINS deprecation was announced in Windows Server 2022. Deprecation means the feature remains supported and maintained, but there is no further active development or new functionality planned. November 2034 is the end of the lifecycle for Windows Server 2025, which also marks the end of support for WINS. How this will affect your organization: Once removal takes effect, the following components will no longer be part of Windows Server: WI

Geändert

20.11.2025

Services

Windows

Microsoft has identified an issue affecting some organizations using hotpatch updates on devices running Windows 11 Enterprise, version 25H2. After installing the hotpatch update KB5068966 released November 11, 2025, affected devices repeatedly download and install the same update when a Windows Update scan is run. This behavior does not impact device functionality; only the update history will reflect the latest installation timestamp.An out-of-band (OOB) update was released today, November 20, 2025, to address this issue. This is a cumulative update, so you do not need to apply any previous updates before installing this update, as it supersedes all previous updates for affected versions.If you have not yet deployed the November 2025 hotpatch update (KB5068966) on Windows 11, version 25H2 devices in your environment, we recommend you apply this OOB update (KB5072753) instead.

Geändert

20.11.2025

Services

Windows

The November 2025 non-security preview update is now available for all supported editions of Windows 11, version 23H2. The non-security preview update for Windows 11, versions 25H2 and 24H2 will be available soon. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained.Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available.Highlights for the Windows 11, version 23H2 update: This update makes quality improvements to the servicing stack, which is the component that installs Windows updates.This update addresses an issue where File Explor

Geändert

19.11.2025

Handlung bis

14.10.2027

Services

Microsoft Entra

Introduction Starting October 2027 and ending November 2027, we will retire the isAttestationEnforced and keyRestrictionsproperties from the existing fido2AuthenticationMethodConfiguration API schema. This change aligns with the latest update to the passkey policy API schema, which introduces support for granular group-based configurations with passkey profiles. During the retirement period, isAttestationEnforced and keyRestrictions will remain in sync with their counterparts attestationEnforcement and keyRestrictions within the Default passkey profile. When this will happen Retirement begins in mid-October 2027 and is expected to complete by early November 2027. How this affects your organization:You are receiving this message because our reporting indicates your organization may be using this feature. Who is affected: Admins managing FIDO2 authentication configurations and any custom a

Geändert

19.11.2025

Handlung bis

01.07.2026

Services

Microsoft Defender XDR

Updated November 19, 2025: We have updated the timing of this change below. Thank you for your patience.On July 1, 2026, you may encounter issues if you haven't updated your analytic rules, automation rules/playbooks, workbooks, hunting queries, or custom integrations to be precedence-aware for account entity naming. We've standardized the account entity naming logic in Microsoft Sentinel incidents and alerts, where the account entity naming priority is: UPN prefix → name → display name. Please update your queries and automations to use the new precedence pattern.You are receiving this message because our reporting indicates your organization may be using Microsoft Sentinel incidents, alerts (AlertV3), or related automation.[When this will happen:]July 1, 2026 (previously February 13, 2026)[How this will affect your organization:] If you don't fix this problem, these queries, automations