Setup Automated Macos
Doc updateThe link text changed from “ShipKeys” to “SkipKeys”; the destination URL is unchanged.
Daily highlights from Microsoft Learn and Message Center. Browse the archive from 1 January 2026 → About this project →
The period was dominated by Windows Autopilot guidance updates, with several concrete implications for deployment planning. Automatic Autopilot Policy documentation raises the managed-application selection limit from 10 to 25, while related pages clarify how device association selects between Autopilot and device preparation deployments and that association is unavailable in sovereign clouds. Other notable edits refine local Autopilot Reset procedures and remove a documented Enterprise App Catalog app restriction from current Enterprise App Management guidance.
The Apps section now says administrators can select up to 25 managed applications for deployment, increased from 10. The page also links to Enterprise App Catalog and its auto-update apps, allowing broader documentation-supported app selection before users access a device.
The Entra Join Device Association page states that unassociated devices run Windows Autopilot deployment, while associated devices run Windows Autopilot device preparation deployment. To run device preparation without association, administrators are directed to deregister the device from Windows Autopilot.
The Overview now states that device preparation supports GCCH and DoD environments, but device association is unavailable in sovereign clouds. Administrators in those environments should not plan deployments around device association.
The updated article revises local Reset configuration steps involving Intune, Windows Configuration Designer, and the Set up School PCs app. It also documents a full-wipe requirement for hybrid joined and Surface Hub devices.
The page no longer states that auto-update Enterprise App Catalog apps cannot be blocking apps in Enrollment Status Page or Autopilot device preparation. Administrators configuring blocking apps should review the current guidance rather than rely on the removed statement.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The link text changed from “ShipKeys” to “SkipKeys”; the destination URL is unchanged.
The page refreshes its metadata and changes the DISA SCAP benchmark hyperlink to a new URL.
The page received wording and metadata updates, clarified setup guidance, and added that licensed users can sign in and use entitled features such as Conditional Access. Existing guidance on primary users and TPM 2.0 remains documented.
The page received metadata, wording, and formatting updates. RSS guidance and requirement labels were rephrased, while the listed Windows 11 versions and KB references were reformatted.
The article was updated with refreshed wording, manufacturer terminology, metadata, and bullet formatting. Its guidance covers motherboard replacements and other servicing scenarios, including device deregistration.
The page was edited for clearer setup wording, corrected ADFS known-issue text, updated metadata, standardized links, and removal of two detailed OOBE process steps.
The article was updated with clearer wording and revised instructions for configuring local Windows Autopilot Reset, including use of Intune, Windows Configuration Designer, and the Set up School PCs app. The page date was also updated.
The documentation now states that device preparation supports GCCH and DoD environments, but device association isn't available in sovereign clouds. It also explains TPM-backed association, policy precedence, corporate ownership, naming, and OOBE customization.
The page now explains that unassociated devices run Windows Autopilot deployment, while associated devices run Windows Autopilot device preparation deployment.
The Apps section documentation now states that up to 25 managed applications can be selected for deployment, increased from 10. It also adds links for Enterprise App Catalog and its auto-update apps.
The article no longer includes the note that Win32, Microsoft Store, and Enterprise app catalog apps can be skipped when a managed installer is configured for the tenant.
The reporting and monitoring page no longer includes the note that configuring a managed installer can cause Win32, Microsoft Store, and Enterprise app catalog apps to be skipped.
The tutorial adds a link about automatic updates for Enterprise App Catalog apps and removes guidance about device association precedence and deregistering Autopilot devices.
The page date changed to November 3, 2026, and the statement that auto-update Enterprise App Catalog apps cannot be blocking apps in ESP or Autopilot device preparation was removed.