Blog
How to automate Windows 365 security baselines
Learn how to automate Windows 365 security baselines, manage Intune upgrades, detect drift, and produce Cloud PC audit evidence.
Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story
Blog
Learn how to automate Windows 365 security baselines, manage Intune upgrades, detect drift, and produce Cloud PC audit evidence.
Table of Contents
When Microsoft ships a new security baseline version, existing Microsoft Intune profiles become read-only until updated, and Microsoft has acknowledged cases where Intune did not save customized settings during security baseline policy updates. Automating Windows 365 security baselines means maintaining large Cloud PC fleets through version upgrades and conflict-driven drift.
This guide is for enterprise endpoint and security teams responsible for Windows 365 Cloud PCs across the Windows Cloud portfolio (Microsoft's umbrella for Windows 365 and Azure Virtual Desktop).
Microsoft's baseline deployment steps walk you through profile creation in a nine-step wizard. Ongoing automation work happens across the baseline lifecycle that follows.
Windows 365 uses its own Cloud PC-tuned security baseline, currently Windows 365 Security Baseline Version 24H1. The only other version available in Microsoft Intune is November 2021. Profile updates happen against a specific baseline template, so the version you're on determines what you can edit.
Each template is a bundle of security policy settings that Microsoft has pre-configured to cover Windows 11, Windows 10, Microsoft Edge, and Microsoft Defender for Endpoint. Your automation has to track that template boundary, not just the profile name.
The Windows 365 baseline excludes BitLocker because Cloud PCs don't support it, while the standard Windows MDM baseline, currently version 25H2, includes BitLocker settings for fixed and removable drives. The separate Defender for Endpoint baseline is currently not recommended for use on virtual machines (VMs) or VDI endpoints (virtual desktop infrastructure endpoints), and Microsoft's Windows 365 deployment guidance says the Cloud PC baseline is tuned so remote connectivity isn't impacted. Deploying the physical-device baseline to Cloud PCs means enforcing settings the virtual hardware can't honor.
Notable v24H1 defaults include Credential Guard enabled with UEFI lock, virtualization-based security turned on, a minimum device password length of 14 with a history of 24, SMB v1 disabled, and AutoPlay blocked across all drives.
Separately from the baseline, Microsoft disabled clipboard, drive, opaque low-level USB, and printer redirections by default for all newly provisioned and reprovisioned Cloud PCs beginning June 18, 2025. Teams should review the v24H1 defaults before broad assignment.
As part of Windows 365 management, Cloud PCs enroll into Intune automatically at provisioning, so the baseline does not require an enrollment project. Microsoft's canonical workflow runs through the Intune admin center.
Enterprises spend much of the deployment work reviewing and documenting configuration changes. A practitioner response on Microsoft Q&A puts it plainly: applying the baseline as-is "almost always causes friction because it's designed for maximum security, not usability," and "most enterprises keep 80–90% of the baseline intact but relax settings around application control, scripting, and user experience blockers. The key is to document every deviation."
Those documented deviations become your exception register when auditors ask why a setting differs from Microsoft's recommendation.
Dynamic Microsoft Entra ID device groups recalculate membership periodically, which can delay policy for newly provisioned Cloud PCs. For immediate enrollment-time evaluation, teams can use the All devices virtual group paired with device filters.
For rollout sequencing, Microsoft's cloud-native endpoint tutorial defines a three-ring model. The model starts with a pilot ring for IT plus volunteers, moves to early adopters at roughly 5% of users, and then expands to broad deployment. Microsoft recommends assignment filters to target rings rather than duplicating groups for every policy. The baseline should be tested on a pilot ring of Cloud PCs before broad assignment. A locked-down setting that breaks a line-of-business app is far cheaper to find in a pilot than after broad deployment.
Once the baseline is live and targeted correctly, enforcement depends on how it interacts with every other policy type in your tenant, and Intune's precedence rules are less intuitive than the wizard.
Three Intune policy types shape what lands on a Cloud PC. A security baseline is a Microsoft-curated template that configures devices to a recommended security posture. A device configuration profile is a custom policy your team builds to configure specific settings. A compliance policy evaluates whether devices meet your standards and reports the result.
Teams that automate Intune compliance policies need to model these policy types separately because that distinction drives both conflict behavior and audit evidence.
Under the hood, Intune treats baselines as a specialized form of configuration policy. Once multiple policies touch the same setting, that shared category is what Intune uses to decide the winner. Microsoft's endpoint security documentation gives these Intune precedence rules:
Intune does not include automated prevention for those conflicts. Microsoft's own planning guide states: "In Intune, policies are applied to users and groups you create. There isn't a hierarchy. If two policies update the same setting, then the setting shows as a conflict."
For example, the Security Baseline for Windows 10 and later and the Windows 365 baseline can set identical settings and conflict with each other. The same happens when a device configuration profile overlaps with a baseline setting.
Baselines and device configuration profiles enforce configuration. A compliance policy validates that enforced state and feeds it to Conditional Access, which can block noncompliant Cloud PCs from organizational resources per Microsoft's Windows 365 compliance documentation. Auditors usually need the compliance state record in addition to the baseline profile.
Sorting out precedence is manageable while your policies stay static. It compounds the moment Microsoft ships a new baseline version, where lifecycle automation needs to extend the native workflow.
Baseline version upgrades stay manual per profile, and the Graph API only partially closes the gap. Teams that want end-to-end automation either build and own a scripted pipeline or add a management platform on top.
When Microsoft releases a new version, existing profile instances become read-only until updated. Customized settings have historically not carried over. Microsoft acknowledged a 2025 known issue, stating "The Intune team will be delivering an update to automate migration of the impacted security baselines (and all future versions) in an upcoming release." The update process also leaves the original baseline behind as a duplicate you must clean up to avoid conflicts.
Even service updates within a version require a touch. Per Microsoft's what's-new documentation, "The new setting isn't visible in a baseline profile's properties until you edit and save the profile." Bulk version migration across profiles still requires per-profile administrative work.
The Graph API supports parts of policy automation. Graph policy inventory is fragmented by policy type, and a Microsoft response on Microsoft Q&A explains that "currently there is no one Graph API that can get all types of Intune policies at the same time, because Intune policies are separated into different Graph APIs to get them." Baseline creation runs through the beta Graph intents endpoint, and profiles created that way may not appear in the Intune portal's Endpoint Security view.
Throttling also caps write operations at 200 requests per 20 seconds per tenant. Microsoft's own STIG baseline documentation notes a 197-rule baseline needs "at least 591 API calls for a single tenant" via per-setting calls, versus two to three with the bulk export API.
A configuration-as-code approach, using Microsoft's configuration-as-code guidance, stores policy JSON in version control and reconciles through Graph. The sample scripts carry a clear disclaimer. Microsoft states that it "does not support the scripts themselves, even if they are on our GitHub repository. They are provided for example only."
You can build the pipeline, but you own it when it breaks. For teams that do not want to own that code path, Nerdio Manager for Enterprise can add Intune policy backup and restore, audit logging, and feature rollback workflows around the same baseline lifecycle.
Cloud PC drift comes from a handful of predictable sources, and native Intune covers most of the detection loop. The gap for auditors is versioning, backup, and cross-policy drift tracking.
Four documented causes commonly create Cloud PC drift:
Per-setting status under each baseline profile reports Succeeded, Conflict, or Error for every setting on every device. A device can take up to 24 hours to report status after check-in, per Microsoft's status reporting delay.
Intune Remediations pair a detection script with a remediation script on a schedule. A documented timing caveat is that detection responses arrive within 5–6 minutes while remediation responses can take 6–7 hours or a full day, per Microsoft's remediation response delay. Microsoft is also previewing client-driven compliance evaluation, where devices detect state changes locally and request re-evaluation instead of waiting for the next check-in.
For the compliance mapping, NIST SP 800-53 control CM-2 covers baseline configuration. NIST defines a baseline configuration as "a documented set of specifications for a system... which can be changed only through change control procedures," and CM-2(2) requires automation support for accuracy and currency at Moderate and High baselines. Per-device compliance state reporting provides the continuous-monitoring evidence CM-2(2) contemplates.
On the CIS side, the current CIS Microsoft Intune for Windows 11 Benchmark is v5.0.0, updated in a July 2026 update with 22 new settings, 15 updated, and 23 removed. Starting July 1, 2026, Microsoft bundles Intune Advanced Analytics into Microsoft 365 E3, which removes a cost barrier to Advanced Analytics reporting for E3 enterprises.
Microsoft provides the native building blocks with baseline, compliance policy, Remediations, and Conditional Access. Native Intune can deploy the profile, report per-setting status, run Remediations, and feed compliance state into Conditional Access enforcement.
Deploying CIS Benchmarks by hand, per Nerdio CIS documentation, means referencing a 1,300+ page PDF guide. Nerdio Manager adds versioning, backup, and drift workflows around that loop.
Nerdio Manager runs as an automation layer on top of your Microsoft tenant and extends Microsoft Intune management for Cloud PCs. Nerdio Manager's Enterprise Intune integration covers Intune-enrolled endpoints, including Windows 365 Cloud PCs and other Intune-enrolled devices, plus Azure Virtual Desktop hosts. It spans the Windows Cloud portfolio plus physical devices from one console.
Many enterprises run both paths, so Nerdio Manager pairs Windows 365 Intune policy backup and restore with Cloud PC reporting and Advisor right-sizing alongside Desktop orchestration for Azure Virtual Desktop. On the Azure Virtual Desktop side, a benchmark by Dr. Benny Tritsch found that updating a custom image took 0:37 and 13 clicks in Nerdio Manager versus 5:09 and 146 clicks natively, reducing time by 88% and clicks by 91%, which means fewer admin inputs and fewer chances to misclick during image updates.
Nerdio Manager addresses the baseline lifecycle through policy backup, reporting, and Windows Cloud management:
Version 7.6, released February 12, 2026, added cross-tenant Intune and Windows 365 management in public preview for organizations running multiple tenants. With backed-up policy history and centralized Intune reporting, baseline lifecycle work becomes a monitored workflow instead of a per-profile rescue job.
Teams can deploy Windows 365 Security Baseline v24H1 to a pilot ring using device filters rather than duplicated groups. Teams should document every deviation from the defaults so the exception register exists before your first audit. The baseline can be paired with a compliance policy and Conditional Access so noncompliant Cloud PCs are blocked from organizational resources.
Your team can then decide whether it will maintain a scripted Graph pipeline without Microsoft support or use a management platform that versions, backs up, and reports on policy state.
The read-only profile problem, the conflict sprawl, and the audit evidence question all live in that last decision. You can get a demo to see how Nerdio Manager handles baseline drift, policy backup, and Intune management across your Windows 365 and Azure Virtual Desktop environment, or try it free in your Azure tenant.
No. Windows 365 Security Baseline Version 24H1 is built for Cloud PCs: it excludes BitLocker, which Cloud PCs don't support, and is optimized to avoid impacting remote connectivity. The standard Windows MDM baseline, currently version 25H2, includes BitLocker drive settings. Microsoft also advises against using the Defender for Endpoint baseline on VMs or VDI endpoints.
No. Existing baseline profiles never self-update to a new version. Profiles on an old version become read-only until an admin updates them, and the update leaves the original behind as a duplicate that must be removed to prevent conflicts. Even mid-version service updates require editing and saving each profile before new settings appear.
It depends on the policy type. A compliance policy setting overrides a configuration policy setting, and the most restrictive value wins between compliance policies. Between two configuration policies, including two baselines, Intune flags a conflict for manual resolution and the setting may fail to apply. You can check Per-setting status under the baseline profile to find Conflict and Error states.
Partially. Baselines can be created through the beta deviceManagement/intents endpoint, but Graph endpoints are segmented by policy type, API-created profiles sometimes fail to appear in the portal, and Microsoft documents no API for bulk baseline version upgrades. Write operations are also throttled at 200 requests per 20 seconds per tenant, which constrains per-setting automation at scale.
Learn more about Nerdio Manager