The tutorial was revised for clearer, consistent wording and formatting. Setup guidance for MDM servers, device assignment, RBAC permissions, User Affinity, and authentication options was clarified, and Apple Business links were updated.
Day in brief
Configuration Manager TLS guidance adds Azure Policy as co-management enrollment prerequisites are clarified
All six entries are documentation updates, with most involving wording, formatting, or refreshed links. The substantive exceptions are Configuration Manager guidance that adds a direct Azure Policy reference for TLS 1.2 and documents the Windows requirement, token fallback, and diagnostic log for co-management auto-enrollment. Intune updates also clarify the Account Driven Apple User Enrollment flow, distinguish default from custom boot images in operating-system deployment guidance, and expand the protected-app reference.
- TLS 1.2 guidance gains a built-in Azure Policy reference
Configuration Manager · GeneralThe Configuration Manager page now links directly to the built-in Azure Policy definition for configuring TLS 1.2. It also clarifies SQL Server, WSUS, and Windows Server support notes, along with related prerequisites and platform guidance.
- Co-management enrollment documents its Windows requirement and token fallback
Configuration Manager · Device enrollmentThe updated guidance states that device-token auto-enrollment requires Windows 10 version 1803 or later. If the device token fails, enrollment falls back to the user token; ComanagementHandler.log is identified as the diagnostic log to check.
- Account Driven Apple User Enrollment guidance spells out the sign-in flow
Intune · Device enrollmentThe revised Intune article explains that users begin enrollment by signing in to their work account in Settings, approve device management, and then receive silent policy installation. Service-discovery instructions were also refreshed.
- Configuration Manager deployment guidance separates default and custom boot images
Configuration Manager · FundamentalsThe operating-system deployment introduction now states that Configuration Manager provides default x86 and x64 boot images, while images added by administrators are custom. Deployment scenario and PXE, multicast, and bootable-media descriptions were also refreshed.
- Intune’s protected-app reference adds three applications
Intune · App managementThe reference now includes Elevate UC for Intune, eScription One, and Prisma Browser for Intune, with descriptions and icons. eScription One also has an Android Google Play link.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
6 updates
Microsoft Intune
3 updatesThe article now explains that users start enrollment by signing in to their work account in Settings, approve device management, and receive silent policy installation. It also includes wording, capitalization, date, and service-discovery instruction updates.
Ref Protected Apps
Doc updateThe reference now includes Elevate UC for Intune, eScription One, and Prisma Browser for Intune, with descriptions, icons, and an Android Google Play link for eScription One.
Microsoft Configuration Manager
3 updatesThe documentation now states that device-token auto-enrollment requires Windows 10 version 1803 or later and falls back to the user token if the device token fails. It also adds guidance to check ComanagementHandler.log and refreshes dashboard descriptions and image text.
The page refreshes wording for deployment scenarios and PXE, multicast, and bootable media methods, and adds that Configuration Manager provides default x86 and x64 boot images while administrator-added images are custom.
Enable Tls 1 2 Server
Doc updateThe documentation now links to a built-in Azure Policy definition for configuring TLS 1.2 and updates wording, dates, links, and platform guidance. SQL Server, WSUS, and Windows Server support notes were also clarified.