Microsoft Intune Settings Catalog updated to support Windows 11, version 26H2
Windows 11, version 26H2 is now available, and Microsoft Intune provides day zero support for validated Windows policy settings in the Settings Catalog. We continue to invest in the settings catalog infrastructure to ensure timely support for new Windows policy settings. This enables organizations to adopt new OS versions and features without delay and maintain secure, compliant, and well-managed environments. These settings are rolling out globally and should appear across all Intune tenants over the coming days. Settings Catalog support for Windows 11, version 26H2 As part of Windows 11, version 26H2 settings catalog support, the Settings Catalog now includes all newly released settings and updates to existing settings introduced with the latest Windows 11, version 26H2 release. These settings are available to be configured in settings catalog, enabling administrators to manage and configure Windows endpoints using the newest 26H2 capabilities. What this means for administrators Administrators can find the new settings within the settings catalog in the Microsoft Intune admin center under Devices > Manage devices > Configuration > Create > New policy. Select Windows 10 and later for the platform and Settings catalog for the profile type. Before deploying Windows 11, version 26H2: Review the new and updated settings that apply to your organization. Test configuration profiles with a representative device group. Confirm that the targeted Windows edition and version support each setting. Monitor profile deployment and device status after assignment. Windows 11, version 26H2 security baseline Windows 11 version 26H2 Security Baseline will also be made available shortly in Intune. We are validating the final recommendations and plan to make the updated baseline available over the coming days following the Windows 11, version 26H2 release. The current baseline includes: A new recommendation for Configure Windows Ready Print driver ranking. An updated Turn off encryption support recommendation that changes the supported Transport Layer Security versions from TLS 1.1 and 1.2 to TLS 1.2 and 1.3. Configure NetBIOS settings - This setting is pending availability in the Settings Catalog and will be added to the baseline in a future update. Learn more Create a policy using settings catalog in Microsoft Intune Windows 11 - release information Learn about Intune security baselines for Windows devices We welcome your feedback. If you have questions about these settings or Windows 11, version 26H2 management in Intune, leave a comment on this post or follow us on LinkedIn or @MSIntune and @IntuneSuppTeam on X to continue the conversation.
Feature Request: Extend Security Copilot inclusion (M365 E5) to M365 A5 Education tenants
Background At Ignite 2025, Microsoft announced that Security Copilot is included for all Microsoft 365 E5 customers, with a phased rollout starting November 18, 2025. This is a significant step forward for security operations. The gap Microsoft 365 A5 for Education is the academic equivalent of E5 — it includes the same core security stack: Microsoft Defender, Entra, Intune, and Purview. However, the Security Copilot inclusion explicitly covers only commercial E5 customers. There is no public roadmap or timeline for extending this benefit to A5 education tenants. Why this matters Education institutions face the same cybersecurity threats as commercial organizations — often with fewer dedicated security resources. The A5 license was positioned as the premium security offering for education. Excluding it from Security Copilot inclusion creates an inequity between commercial and education customers holding functionally equivalent license tiers. Request We would like Microsoft to: Confirm whether Security Copilot inclusion will be extended to M365 A5 Education tenants If yes, provide an indicative timeline If no, clarify the rationale and what alternative paths exist for education customers Are other EDU admins in the same situation? Would appreciate any upvotes or comments to help raise visibility with the product team.
Provide a global setting to hide the User Information List in SharePoint Online Sites
Many organization uses SharePoint Online sites that include external guests, suppliers, partners, and other collaborators. Today, any user with appropriate site permissions can access and enumerate the site's User Information List, either through the SharePoint interface or directly through REST API calls. While this list is scoped to a specific site collection and is not a tenant-wide directory, it can still expose a significant amount of user profile information. On large collaboration sites, enterprise portals, or widely shared workspaces, users may be able to retrieve names, email addresses, job titles, departments, phone numbers, and other synchronized profile data for everyone known to that site. A current workaround is removing the Browse User Information permission from site permission levels. However: This can impact legitimate SharePoint functionality and user experiences. It must be managed on a site-by-site basis. Site Owners can re-enable the permission, unintentionally reintroducing the risk. It is difficult to govern consistently across large environments with thousands of sites. Requested Enhancement: Introduce a tenant-level setting that allows SharePoint Online administrators the ability to: Hide the User Information List from end users. Block direct access through SharePoint REST APIs. Enforce the setting regardless of site-level permission changes. Optionally scope the control to sites that allow external sharing. This would provide organizations with a more reliable way to reduce unnecessary exposure of user profile information while maintaining consistent governance across their SharePoint environment.
(KB5124010) Niepowodzenie instalacji dnia 1.10.2026 — Ox800f0922
Mam problem z instalacją aktualizacji (Aktualizacja dla systemu Windows (KB5124010) Niepowodzenie instalacji dnia 1.10.2026 — Ox800f0922). Próbowałem też ponownie zainstalować system (Windows Update - Opcje zaawansowane - Odzyskiwanie - Rozwiązywanie problemów za pomocą usługi Windows Update Ta opcja jest teraz niedostępna) instalowanie zakończone niepowodzeniem, nie mogę zainstalować ponownie systemy za pomocą Windows Update. Próbowałem też zainstalować ponownie poprzez utworzenie bootowalnego pendrive za pomocą "Media creation tool" ale też nie mogłem zainstalować, a nawet naprawić systemu. Pobrałem plik obrazu systemu Windows kliknąłem na niego następnie został zamontowany on w napędzie, po wejściu do napędu i klikmięciu "setup.exe" również nie miałem możliwości instalacji systemu. W jaki sposób naprawić system aby zainstalować najnowszą aktualizację i mieć sprawny system? P.S jeżeli to zły dział to proszę o przeniesienie tematu.
