Ref Settings Windows
Public previewThe documentation now lists Windows App alongside Microsoft Edge as a supported app for Windows MAM app protection policies.
Two scheduled changes give this period its clearest operational signals: iOS/iPadOS and macOS Company Portal will require v5.2608.0 starting in February 2027, while improved Microsoft Purview DLP setup and Intune multi-admin approval support for unmanaged apps in Edge for Business is scheduled to roll out from January 2027. New Intune guidance also covers a CIS Windows 11 audit profile in preview, a nonproduction Windows Server Insider Preview pilot, and managed Google Account authentication for supported Android Enterprise devices. The CIS profile assesses 404 settings without configuring or remediating devices.
Microsoft 365 Message Center says iOS/iPadOS and macOS Company Portal will require version 5.2608.0 starting in February 2027. Most users update automatically; organizations that block app installation may need to push updates or arrange manual updates.
The new audit workflow assesses 404 settings across CIS Level 1, Level 2, and BitLocker checks without configuring or remediating devices. Using it requires Advanced Analytics, enrolled Windows 11 devices, and appropriate Intune permissions, with results available for review and export.
The end-to-end guide covers enrollment, configuration, compliance, apps, updates, verification, prerequisites, and supported server types for testing supported Windows Server Insider Preview vNext builds. The guidance is for evaluation rather than production, and Server Core is unsupported.
The planned January 2027 rollout adds clearer setup status, error reporting, and task coordination while supporting Intune multi-admin approval for unmanaged apps in Edge for Business. Existing policies remain unchanged and current Intune approval behavior continues during the transition.
New guidance explains how to require managed Google Account authentication through Intune policies on supported corporate-owned and personally owned Android Enterprise devices. It covers prerequisites, enrollment types, policy creation, assignment, and the profile approach for each ownership scenario.
Prepare helpdesk communications for the Company Portal change; most users update automatically, but devices that block app installation may need pushed or manual updates. No prior action is required for the Purview DLP rollout, and existing policies and Intune approvals remain unchanged. CIS auditing requires Advanced Analytics, enrolled Windows 11 devices, and appropriate permissions, and its findings should be treated as assessment results rather than remediation. Keep Windows Server Insider testing in nonproduction environments, use the dedicated guide, and note that Server Core is unsupported. For Android Enterprise, follow the prerequisites and select the policy method that matches device ownership.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The documentation now lists Windows App alongside Microsoft Edge as a supported app for Windows MAM app protection policies.
The deployment documentation now describes selecting Platform, Category, and App type for Android apps, including store, Managed Google Play, LOB, built-in, web, and system apps. It retains App type-only instructions for other platforms.
The instructions now explicitly identify Android as the platform, the applicable category, and the Managed Google Play app type.
The instructions now use “Referenced app” for Category, add an App type step, and direct admins to select Select instead of Create.
The instructions now specify selecting Android as the platform, Referenced app as the category, and Android Enterprise system app as the app type.
The instructions now specify selecting Android as the platform, Built-in app as the category, and Built-in app as the app type for Android apps. The iOS/iPadOS selection path remains listed under Other.
The instructions now identify the Platform as Android, Category as Line-of-business app, and App type as Intune.
The instructions now direct admins to select Android as the platform, Store app as the category, and Android Store app as the app type.
The instructions now specify selecting Android as the platform, Web link as the category, and Web link as the app type. Instructions for other platforms remain under Other types.
The instructions now specify selecting Android, Store app, and Managed Google Play app in the Select app type pane before selecting Select.
The instructions now specify selecting Android as the platform, Store app as the category, and Managed Google Play app as the app type before choosing Select.
The documentation now lists Windows App among supported Windows MAM apps and identifies its support as preview. Government cloud support is clarified as applying to Microsoft Edge.
The supported-device guidance now includes eligible Windows Server Insider Preview devices for nonproduction evaluation and links to Server-specific requirements and limitations.
Microsoft Purview DLP will enhance setup and activation for unmanaged apps in Edge for Business, supporting Intune multi-admin approval with clearer status, error reporting, and task coordination. Rollout starts January 2027, requiring no prior action; existing policies remain unchanged and Intune approvals continue as before.
The reference now includes EnGlobe Mobile, Everbridge 360, Hypergate Files for Intune, Newcode, Ramp, Reliaquest GreyMatter, Rogo AI, Rogo AI (Intune Wrapped), ShareCRM, and Zoho Mail - Intune, with descriptions, icons, and store links.
The documentation now includes separate Allowed data sources and Allowed data destinations entries, with options and a Microsoft Edge note for No destinations. The page metadata date was also updated.
The page updates wording and expands explanations of KDC strong mapping, the OnpremisesSecurityIdentifier SAN variable, Android trusted-root limitations, and public CA requirements for S/MIME certificates.
Microsoft added an end-to-end guide for piloting supported Windows Server Insider Preview vNext builds in Intune. It covers enrollment, configuration, compliance, apps, updates, verification, prerequisites, and supported server types; Server Core isn't supported.
The page now explains that only Windows Server Insider preview builds can enroll, production server enrollment is unsupported, and servers are blocked by default. It also documents enrollment restriction and ownership-filter options for allowing servers.
The documentation now states that only Windows Server Insider preview builds can enroll, server devices are blocked by default, and production enrollment isn't supported. It also describes configuration options for allowing enrollment.
The enrollment guide now states that enrollment is enabled by default for listed platforms except Windows Server, which is blocked by default. It also adds a link for Windows Server Insider Preview nonproduction testing.
The Android settings catalog now documents requiring users to authenticate with a managed Google Workspace account, including supported device types, prerequisites, unsupported dedicated devices, and authentication behavior.
The guide now identifies the Managed Google Play enterprise and Intune tenant involved, requires the Google Workspace Super Admin role for upgrades, and adds domain, account, and policy preparation for device authentication.
The guide now explains that some corporate- and personally owned work-profile devices may require managed Google Workspace authentication during enrollment. Gmail remains disabled until authentication is completed.
The documentation now explains how to optionally require Google Workspace authentication through a Settings Catalog policy, assigned either before enrollment or to already enrolled devices.
The page now documents optionally requiring Google Workspace authentication through a settings catalog policy, assignable before enrollment or to already enrolled devices.
The article updates its title, description, wording, metadata date, and screenshot formatting. It also adds clearer visual guidance for device naming, product keys, and Wi-Fi setup.
The iOS/iPadOS Apple Configurator enrollment page received updated wording, formatting, metadata, and a new screenshot of the enrollment policy creation pane.
The page title, description, metadata, navigation labels, and wording for Android Enterprise dedicated-device enrollment profiles and tokens were updated.
The article now explains the management benefits of corporate identifiers, including phone number and app inventory examples. It also updates wording, formatting, a link label, and the publication date.
The page title and description were updated, and wording was revised throughout the enrollment-method, bootstrap-token, escrow-status, and extension guidance sections.
Starting February 2027, the minimum iOS/iPadOS and macOS Company Portal version will be v5.2608.0. Most users update automatically; those with app installation blocked may need manual updates. Prepare by informing helpdesk and pushing updates if device restrictions are enabled.
The instructions now direct admins to select Android as the platform and Store app as the category in the Select app type pane, replacing the previous direct selection of Managed Google Play app.
The page now documents the CIS audit baseline (preview), which checks Windows 11 configurations against the CIS benchmark and reports findings without enforcing or remediating settings. Security baselines are also relabeled as configuration baselines.
The antivirus documentation now describes native Intune management for eligible Windows Server Insider Preview devices enrolled for nonproduction evaluation, including prerequisite and configuration guidance.
The documentation now states that native Intune management for Windows Server is limited to eligible Insider Preview devices enrolled for nonproduction evaluation, with linked requirements, supported profiles, and limitations.
The index now links to “Audit Windows devices against CIS benchmarks (preview)” and includes updated documentation metadata.
Intune documentation now describes creating and assigning a CIS Microsoft Intune for Windows 11 Benchmark audit profile. The profile assesses 404 settings across Level 1, Level 2, and BitLocker checks without configuring or remediating devices, and supports reviewing results and exporting findings.
The documentation now explains how to run `mst-cli diagnose` on a Tunnel Gateway, review logging checks, use the generated `diagnosticReport.txt`, and troubleshoot missing logs or failed uploads.
The documentation now describes running `mst-cli diagnose` on the Linux server to check prerequisites, configuration, and logging requirements, with some corrective guidance for common failures.
The prerequisites page now explains how to use `mst-readiness` and `mst-cli diagnose` to check installation and logging requirements, including connectivity, proxy, and rootless Podman guidance.
The overview adds a CIS Microsoft Intune for Windows 11 audit baseline that assesses device configurations without changing settings. It also links to guidance for profile creation, results, and exports.
The article now specifies that its guidance covers baselines that configure and enforce settings. Audit-only baselines have separate prerequisites and procedures, with links to the CIS and STIG auditing guides.
The article now states that audit-only profiles use Audit report instead of standard configuration reports and links to CIS and STIG audit-result guidance.
The article’s title, description, date, terminology, link phrasing, and setup guidance wording were updated. Two authoring links were removed, and references to compliance, Conditional Access, enrollment, and licensing were edited.
The article updates its title and wording, clarifies how to access Support Assistant, and adds steps for resolving an authentication issue when opening Help and Support.
The article received capitalization, grammar, wording, metadata, and authoring-reference updates. Its guidance continues to cover configuring the on-premises AD domain, certification authority, NDES server, and Certificate Connector for SCEP.
The tutorial was refreshed with clearer wording, updated metadata, revised navigation descriptions, and links explaining that device enrollment requires an MDM authority and Intune setup.
The page title, metadata date, capitalization, punctuation, and instructional wording were updated for consistency and readability. The documented MDM authority options and setup guidance were retained.
The documentation now refers to Windows OS SKUs and lists five server values, including Datacenter, Standard, evaluation, and Azure Edition SKUs.
The device details table changes the Serial number entry from “All” to Windows, iOS, macOS, and Android.
The What's New page adds Remote Help diagnostic sharing, OneDrive for Business as an Edge work-file destination, updated Edge and Chrome settings catalog templates, Cloud PC reset settings, and opt-in management for eligible Windows Server Insider builds.
The page no longer includes the planned capability for sharing device diagnostics during attended Remote Help sessions on Windows. The page date was updated to November 17, 2026.
The November 16, 2026 service release documents Android Enterprise local actions, new macOS settings catalog controls, PowerShell script group exclusions and built-in group targeting on Windows, and 10 newly available protected apps.
The archive now documents Platform SSO registration during macOS Automated Device Enrollment for macOS 26+ with Company Portal 5.2604.0+, plus faster, richer app inventory for Windows 10/11.
The page date changed from October 30 to November 15, 2026, and entries for Windows maintenance windows, Android Enterprise local actions, and Remote Help in GCCH were removed.
The instructions now direct admins to choose Android as the platform, Referenced app as the category, and Android Enterprise system app as the app type.
The new article explains how to require managed Google Account authentication through Intune policies on supported corporate-owned and personally owned Android Enterprise devices. It covers prerequisites, enrollment types, policy creation, and assignment.
The documentation now directs admins to use the settings catalog for corporate-owned fully managed devices and corporate-owned work-profile devices, while personally owned work-profile devices require a device configuration template.
The article now covers granting permissions to both Managed Home Screen and the Intune app for Local Actions scenarios. It adds app package names, permission details, prerequisites, supported OEMs, role requirements, and the 500-KB profile limit.
The documentation now lists KEYENCE with package identifier `com.keyence.autoid.oemconfig.release`; page metadata was also updated.
The supported platforms documentation now includes Windows Server vNext Insider Preview build 29621.1000 or later for nonproduction testing, with links to enrollment prerequisites, limitations, and downloads.
The documentation now covers Win32 app deployment on eligible Windows Server Insider Preview devices in nonproduction environments and links to enrollment requirements, limitations, and guidance.
The Windows platform guide now directs nonproduction evaluations on eligible Windows Server Insider Preview devices to a dedicated getting-started guide and clarifies that Windows client workflows don't automatically apply.
The article now explains that Intune-deployed apps tagged by the Intune management extension as a managed installer are recognized as allowed apps. It also clarifies that ApplicationControl CSP replaces AppLocker CSP for new development while AppLocker CSP remains supported.
The page received wording, capitalization, grammar, formatting, link-label, description, and metadata updates. The documented settings and profile-creation guidance remain represented in the revised text.
The settings catalog common tasks page now documents requiring managed Google Account authentication for supported Android Enterprise devices and links to prerequisites and setup steps.
The iOS/iPadOS Enterprise SSO app extension page received updated title and description text, refreshed links and metadata, and clearer wording for Intune, Jamf Pro, and other MDM prerequisites and setup guidance.
The article’s wording, formatting, metadata, and references were updated. Instructions now more clearly describe upload limits, ADML pairing, dependency order, RBAC permissions, and possible errors involving Windows.admx.
The update rings documentation now includes eligible Windows Server Insider Preview devices for nonproduction evaluation and links to setup requirements and update limitations.
The documentation now states that the Google Workspace authentication setting reports Error until authentication is completed, but this does not change the device’s overall compliance state.
The documentation now notes that associated devices may enter OOBE before organizational settings are downloaded and applied. TPM attestation and local device association can delay policy retrieval by about a minute.
The documentation now describes reports showing Failure and a 0–1 second duration after pre-provisioning and ESP complete successfully. The device remains enrolled and functional; the issue is caused by a nonblocking Win32 app error being treated as ESP-blocking.
The guide now directs eligible Windows Server Insider Preview devices to separate nonproduction enrollment guidance and clarifies that Configuration Manager supports released Windows Server versions.
The page title now explicitly references Windows Autopilot and states that existing devices can be automatically registered through Intune or another MDM service.
The documentation states that non-owner IT admins retain recovery-key access, while admins who own affected reused Windows Autopilot devices are subject to the same BitLocker self-service restriction as users, even with administrative permissions.
The documentation now states that Windows Autopilot OEM registration lets manufacturers register devices on an organization’s behalf.
The release notes now document task sequence status-message failures after Windows PE when boot media uses CNG/KSP certificates, and content download failures with HTTP 403.7 from PKI HTTPS distribution points. Workarounds and diagnostic details were added.
Documentation now describes helpers requesting point-in-time Windows device diagnostic data reports. Sharers can allow or decline requests, view the report, and stop sharing.
Helpers can request permission to view and possibly store a sharer’s device diagnostic data. With consent, both participants can view the report; helpers can refresh it during troubleshooting. Reports include device, hardware, network, performance, security, update, storage, and peripheral details.
The page now clarifies that Advanced Analytics features in endpoint analytics require the listed prerequisites and configuration, and adds a link to the CIS audit baseline (preview) for assessing Windows 11 configurations against the CIS benchmark.