Wednesday, 8 July 2026

Configuration Manager baseline guidance now spells out power and idle launch conditions

This was a quiet, documentation-only period. Configuration Manager guidance clarifies when deployed baselines are evaluated and how to troubleshoot missed schedules, while Intune Android work-profile guidance retains web-enrollment limitations without promising a future fix. No feature launch, retirement, or availability change is evidenced.

• Configuration Manager · Compliance

  Baseline evaluation timing now includes first-launch conditions

  The deployment guidance now says computer-targeted baselines are evaluated within a two-hour randomization window of each scheduled start after the first evaluation. The first evaluation on a Windows client additionally requires the device to be powered above the low-battery threshold and the user to be idle. This is a documentation clarification of client evaluation behavior, not an announced product change.

• Configuration Manager · Compliance

  Missed baseline schedules now link directly to Scheduler.log troubleshooting

  The compliance-monitoring page adds a tip directing administrators to the client-evaluation guidance for launch conditions and to Scheduler.log when a scheduled evaluation did not run as expected.

• Intune · Device enrollment

  Android web-enrollment caveats remove obsolete future-fix wording

  Intune still documents that users in tenants accepting only passkeys can't complete web enrollment, so administrators shouldn't enable it until passkey support is announced. Phone-call MFA may also break web enrollment; the documented workarounds are authenticating on a secondary device or using SMS. The revision removes statements that these limitations will be resolved in a future update, without announcing that they are resolved.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.