Microsoft’s Intune What’s New documentation now lists five operational changes: an Insider preview for Windows Server management, diagnostic sharing in Remote Help, OneDrive destinations for Edge work downloads, expanded Windows settings-catalog controls, and CIS benchmark auditing for Windows 11.
For Intune administrators, the signal is clear: Microsoft is extending familiar endpoint workflows into servers, support sessions, browser data handling, Cloud PC recovery, and configuration auditing. Each change requires deliberate scope control before broader assignment.
1. Windows Server Management Enters Insider Preview
Microsoft’s getting-started guidance, dated November 17, 2026, describes management for eligible Windows Server Insider Preview builds through familiar Intune workflows. Microsoft explicitly limits the preview to testing and evaluation in nonproduction environments and does not support production use.
What you can control: The preview supports selected device configuration and endpoint security policies, including settings-catalog policies, custom configuration profiles, and administrative templates. Administrators can also evaluate supported compliance policies, use compliance with Microsoft Entra Conditional Access, deploy Win32 apps, configure supported Windows Update ring settings, and inspect inventory, policy, app, and compliance status.
Supported remote actions include sync, restart, BitLocker key rotation, and diagnostic collection. Microsoft says Azure and Azure Arc are not required, although Azure Arc can provide complementary governance, monitoring, automation, and hybrid or multicloud services.
The eligible device scope is narrow. Microsoft includes persistent physical servers and virtual machines running Desktop Experience, including persistent single-session hosts. Server Core, multisession, ephemeral, and nonpersistent hosts are excluded.
Why this matters: This is not production server management through Intune. It is a controlled evaluation of whether established Windows endpoint workflows translate cleanly to persistent server estates.
Enrollment is blocked by default. That safeguard matters because existing Windows assignments could otherwise reach servers with consequences that were never evaluated for a server workload.
Admin action:
- Keep the preview isolated: Use dedicated server pilot groups and assignment filters rather than reusing broad Windows device groups.
- Review current assignments: Check Windows policies, applications, compliance rules, and update configurations before allowing any server enrollment.
- Confirm device eligibility: Limit testing to supported Windows Server Insider Preview builds running Desktop Experience.
- Change enrollment restrictions deliberately: Allow server devices only in the enrollment restriction profile intended for the pilot.
- Use preview channels for issues: Microsoft directs preview feedback through the Intune Server Management preview form and Windows Server Insiders community rather than standard production support.
2. Remote Help Adds Diagnostic Sharing on Windows
Microsoft Intune Remote Help is rolling out diagnostic sharing for attended Windows sessions. According to Microsoft’s Remote Help documentation, a helpdesk agent can request a point-in-time report containing system details and resource-usage information.
What you can control: The end user must consent before the diagnostic data is shared. The user can inspect the data, stop sharing at any time, or decline the request without ending the Remote Help session.
Remote Help must be enabled for the tenant. Microsoft also requires the helper and sharer to authenticate with organizational Microsoft Entra accounts.
Why this matters: Diagnostic access no longer needs to be separated from the active support workflow, but consent remains an explicit boundary. This gives helpdesk teams additional troubleshooting context without making data disclosure a condition for receiving assistance.
Because the feature is rolling out, availability may differ across tenants. Your support procedures should account for sessions where the diagnostic request is not yet available.
Admin action:
- Verify tenant availability: Confirm that diagnostic sharing appears before updating support scripts or service-level expectations.
- Train helpdesk agents: Explain what the report contains and require agents to describe why the data is being requested.
- Preserve user choice: Do not instruct agents to end a session solely because a user declines diagnostic sharing.
- Test the consent flow: Validate what helpers and sharers can see before using the capability with production users.
3. Edge Work Downloads Can Move to OneDrive
Microsoft now supports directing downloaded work files from the Microsoft Edge for Business work profile to OneDrive for Business instead of the Windows device’s local disk. The control is delivered through a Windows app protection policy and requires Microsoft Edge version 158 or later.
What you can control: In the app protection policy, set Send org data to to Selected apps. Under Allowed data destinations, select OneDrive for Business.
Microsoft says downloads from the Edge work profile will then use OneDrive for Business as the destination. The change applies to work-profile downloads governed by the configured policy; it is not a general redirection of every browser download.
Why this matters: This closes a data-handling gap between protected browser activity and local storage. Organizations can keep downloaded work content within an approved organizational destination rather than relying on the endpoint’s local disk.
The browser prerequisite is the immediate deployment dependency. A correctly configured policy will not provide the intended behavior on devices that have not reached Edge 158.
Admin action:
- Check browser readiness: Identify targeted devices that have not reached Microsoft Edge
158. - Review destination policy: Confirm that
Send org data tois set toSelected appsbefore adding OneDrive for Business. - Pilot the download flow: Test work-profile downloads, OneDrive access, and user expectations with a limited device group.
- Document scope clearly: Tell users that the control applies to downloaded work files from the Edge work profile.
4. Windows Settings Catalog Expands Browser and Cloud PC Controls
Microsoft has refreshed the Windows settings catalog with updated Microsoft Edge and Google Chrome administrative templates, plus two device-scoped Cloud PC reset settings. Administrators can configure the additions through a Windows settings-catalog profile, subject to each setting’s supported device and operating-system applicability.
What you can control: The Microsoft Edge template refresh adds the following settings:
- Microsoft Edge
154:AutofillSettings. - Microsoft Edge
156:RemixAvailability, labeled Control Remix availability, for device and user scope. - Microsoft Edge
157:AllHttpAuthSchemesAllowedForProxies. - Microsoft Edge
157:BlueprintGWAAvailability. - Microsoft Edge
157:CloudManagementEnrollmentToken.
Microsoft Edge 155 changes existing policy text but does not add settings. Microsoft also updated the Google Chrome administrative templates to version 153.0.8010.53.
For Cloud PCs, the CloudPCDevice policy area adds two device-scoped controls:
- Authenticated-user reset:
AllowAuthenticatedUserResetcontrols whether authenticated users can perform a refresh or full reset. - Any-user reset:
AllowAnyUserResetcontrols whether refresh or full reset can proceed without authentication.
Why this matters: The browser template changes require policy owners to distinguish new controls from documentation-only text revisions. The Cloud PC additions carry a more direct operational risk because they govern who can initiate recovery actions and whether authentication is required.
This is not a routine catalog refresh for Cloud PC administrators. It introduces reset authority that should be reviewed as a privileged operational capability.
Admin action:
- Inventory existing profiles: Identify settings-catalog profiles that manage Microsoft Edge, Google Chrome, or Cloud PCs.
- Validate applicability: Confirm device scope and operating-system support before assigning any new setting.
- Review reset authority: Treat
AllowAnyUserResetas a higher-risk control and document the operational need before enabling it. - Test recovery behavior: Verify refresh and full-reset workflows in a pilot group before changing production Cloud PC assignments.
- Record template versions: Use Edge and Chrome version identifiers in change records so reviewers can distinguish policy additions from text-only updates.
5. Windows 11 CIS Benchmark Auditing Enters Preview
Microsoft now supports auditing Windows 11 devices against the CIS Microsoft Intune for Windows 11 Benchmark in public preview. The capability requires Microsoft Intune Advanced Analytics.
What you can control: Administrators can create and assign an audit profile, review results for individual settings, and export findings. Microsoft describes the capability as audit-only: it identifies configuration gaps but does not configure settings or remediate devices.
Why this matters: The preview separates benchmark assessment from enforcement. That distinction prevents an audit profile from silently changing device configuration, but it also means every reported gap needs a separate review and remediation decision.
This is evidence collection, not a compliance outcome. Your team still owns exception handling, change testing, remediation, and verification.
Admin action:
- Confirm entitlement: Verify access to Microsoft Intune Advanced Analytics before planning a pilot.
- Create a limited audit assignment: Begin with a representative Windows 11 group rather than the full fleet.
- Export and classify findings: Separate approved exceptions from genuine configuration gaps.
- Build remediation independently: Use established policy and change-control processes because the audit does not alter settings.
- Reassess after changes: Run the audit again after remediation to verify the resulting configuration state.
The Bigger Picture
Summary: Microsoft is broadening Intune’s operational reach, but the controls arrive with different maturity levels and risk profiles. Windows Server management and CIS auditing remain previews. Remote Help diagnostics are rolling out behind user consent. OneDrive download routing depends on Edge 158, while the settings catalog adds browser controls and Cloud PC reset authority that require targeted testing.
Keep previews isolated, validate prerequisites, and treat new reset or data-transfer settings as explicit change-control items. Broad assignment should follow observed pilot behavior—not merely the appearance of a new control in the admin experience.
Stay tuned for more Intune updates, and as always, test thoroughly before deploying to production!
