sme updates

Author: Stephanie-Rosenzweig

learn-pr/device-partner-university/windows-autopilot/includes/1-introduction.md

@@ -5,4 +5,4 @@ Windows Autopilot is a Microsoft cloud-based service that simplifies the deploym
 By completing this module, you can:
 
 - Apply Windows Autopilot to get devices up and running with minimal setup.
-- Discover how Windows Autopilot streamlines IT tasks such as resetting, repurposing, and reassigning devices.
+- Discover how Windows Autopilot streamlines IT tasks such as resetting, repurposing, and reassigning devices.

learn-pr/device-partner-university/windows-autopilot/includes/2-windows-autopilot.md

@@ -20,9 +20,9 @@ When an employee receives a device—whether via mail or other delivery methods
 
 Traditional deployment methods require IT administrators to maintain custom operating system images and device drivers for each hardware model.
 
-Windows Autopilot applies a preinstalled, OEM-optimized version of the Windows client during initial deployment of new devices. This approach eliminates the need for manual image and driver management, streamlining setup procedures and reducing IT workload.
+During initial device deployment, Windows Autopilot leverages the instance of Windows that comes preinstalled on the device (typically provided by the OEM). This approach eliminates the need for manual image and driver management, streamlining setup procedures and reducing IT workload.
 
-Existing Windows installations can be transformed into “business-ready” states by:
+Existing Windows installations can be transformed by Autopilot into “business-ready” states by:
 
 - Applying settings and policies.
 - Installing apps.
@@ -44,26 +44,28 @@ Existing Windows installations can be transformed into “business-ready” stat
 
 - Simplified image management: Eliminates the need to maintain custom operating system images and drivers for each device model.
 - Remote reset capabilities: Enables IT administrators to resolve device issues remotely without requiring physical access.
-- Automatic updates: For users with Microsoft 365 subscriptions (sold separately), Windows Autopilot supports automatic updates to ensure devices remain current with the latest Windows version.
-- Device upgrade and repurposing: Windows Autopilot can be used to upgrade existing devices and deploy specialized configurations such as kiosks, digital signage, or shared-use systems.
+- Automatic updates: In Autopilot deployments that use Intune’s Enrollment Status Page (ESP), monthly security (quality) updates can be installed during Windows OOBE when enabled via the ESP setting “Install Windows quality updates (might restart the device).” Feature updates aren’t supported for installation during OOBE.
 
 ## End-users experience
 
-- Devices are ready for use upon unboxing and sign in, minimizing delays typically associated with traditional deployment methods.
+- Devices are ready for use shortly after unboxing and sign in, minimizing delays typically associated with traditional deployment methods.
 - Provides users with up-to-date tools and configurations aligned with current workplace technology standards.
 - Devices can be preconfigured and shipped directly to users at various locations, eliminating the need for centralized setup.
-- Devices remain current with the latest Windows version, supporting optimal functionality and security.
+- Devices remain current with the latest Windows updates, supporting optimal functionality and security.
 
 ## Differentiating processes
 
 Here are deployment scenarios that fall under [Windows Autopilot](/autopilot/overview):
 
 - *User-driven:* Users enroll their devices using their credentials for a personalized setup.
 - *Self-deploying:* Devices configure automatically without user interaction.
-- *Pre-provisioning:* IT preconfigures devices before delivery, ensuring they're ready for immediate use.
+- *Pre-provisioning:* IT preconfigures devices before delivery, reducing setup time so end users can start using their devices faster after powering it on and signing in.
 
 In these scenarios, devices must first be registered with the Windows Autopilot deployment service. Once registration is complete, a Windows Autopilot profile must also be assigned to the device, defining the configuration options for the specific scenario. In contrast, [Windows Autopilot device preparation](/autopilot/device-preparation/overview) doesn’t require registration. While there’s still a profile assignment process, a Windows Autopilot profile is assigned to users rather than individual devices.
 
+> [!NOTE]
+> Windows Autopilot device preparation is still evolving, and device-based assignment is currently in development.
+
 ## Register and customize
 
 Next, follow through each step of the deployment process for Windows Autopilot scenarios, so you can:
@@ -72,4 +74,4 @@ Next, follow through each step of the deployment process for Windows Autopilot s
 
 - Customize setup and configuration by creating a profile to assign to your customer’s devices.
 
-Lastly, review what happens after the device is provided to an end user.
+Lastly, review what happens after the device is provided to an end user.

learn-pr/device-partner-university/windows-autopilot/includes/3-deployment-process.md

@@ -10,14 +10,12 @@ To complete the registration, you need to:
 
 - Associate the device with an Azure tenant ID.
 
-### Customer-led registration
+### Registration methods
 
-If you're a partner, you can perform these steps on an end user's behalf using the [registration authorization process](/autopilot/registration-auth). If you're an end user, you can choose to register devices themselves by collecting the hardware identity from new or existing devices and uploading it manually.
+If you're a partner, you can perform these steps on an end user's behalf using the [registration authorization process](/autopilot/registration-auth). If you're an end user, you can choose to register devices yourself by collecting the hardware identity from new or existing devices and uploading it manually.
 
 If the devices meet [certain requirements](/autopilot/automatic-registration#requirements), they can also be configured for automatic registration with Windows Autopilot.
 
-### Registration methods
-
 To learn about the different methods used to register devices with Windows Autopilot, select from the following articles on Microsoft Docs:
 
 - [OEM registration](/autopilot/oem-registration)
@@ -30,7 +28,7 @@ To learn about the different methods used to register devices with Windows Autop
 
 ### Upload the hardware hash
 
-To identify a device with Windows Autopilot, the device's unique hardware hash must be captured and uploaded to the Windows Autopilot deployment service.
+To identify a device for use with Windows Autopilot, the device's unique hardware hash must be captured and uploaded to the Windows Autopilot deployment service.
 
 If you're an end user and you want to do this yourself, it's possible to identify a device with a [harvesting process](/autopilot/add-devices#collect-the-hardware-hash) that collects the device's hardware hash from within a running Windows installation.
 
@@ -54,7 +52,7 @@ The Windows Autopilot deployment service matches a device even if moderate chang
 
 - Details about when the ID was generated
 
-- Many other attributes that can be used to uniquely identify the device
+- Other attributes that contribute to uniquely identifying a device
 
 For more information about device IDs, check out the [device guidelines](/autopilot/autopilot-device-guidelines) and [add devices to a customer account](/partner-center/customers/autopilot) pages.
 
@@ -68,41 +66,40 @@ Let’s say you have a device that you don’t want to go through Windows Autopi
 
 ### Verify registration success
 
-You can verify if a device has successfully registered with the Windows Autopilot deployment service. Registered devices appear in the Intune admin center under one of the following paths:
+You can verify if a device has successfully registered with the Windows Autopilot deployment service. Registered devices appear in the Intune admin center under the following path:
 
 *Devices → Windows → Enrollment → (Windows Autopilot) Devices* or *Devices → Enrollment → Windows → (Windows Autopilot) Devices*
 
 ### Intune is NOT Autopilot
 
-Windows Autopilot devices aren't the same as Microsoft Intune devices listed under:
+Windows Autopilot registered devices aren't the same as Microsoft Intune managed devices listed under:
 
-*Devices > Windows | Windows devices* 
+*Devices > Windows | Windows devices*
 
-Windows Autopilot devices are added to the list of Windows devices only when both of these requirements are met:
-
-- The Windows Autopilot registration process is successful.
-
-- The device has gone through Out-Of-Box Experience provisioning and a licensed user has signed in on the device.
+Windows Autopilot registration is an assignment of a device to an Intune tenant with the intent to manage t with that tenant once provisioning is complete. Intune enrollment is actual active control and management of the device.
 
 ![A photograph of a young man working at a desk in an office on a laptop.](../media/working.png)
 
 ## Provide device to the end user
 
 That’s it! The device is now ready.
 
-When you power on your device, all you need to do is:
+When you power on your device, all the user needs to do is:
 
 - Connect the device to the internet.
 - Answer some quick setup questions.
 
-Windows Autopilot handles the rest by installing all the preconfigured apps and settings via the cloud.
+Windows Autopilot handles the rest by installing the preconfigured apps and settings via the cloud.
 
 ### Enrollment Status Page
 
-When a user signs into a device for the first time, the Enrollment Status Page (ESP) displays the device's configuration progress.
+When a user signs into a device for the first time during Windows Autopilot provisioning, the Enrollment Status Page (ESP) displays configuration progress.
 
 The ESP makes sure the device is in the expected state before the end user can access the desktop for the first time. It tracks the installation of applications, security policies, certificates, and network connections.
 
+> [!IMPORTANT]
+> The ESP is not used for the newer Windows Autopilot device preparation.
+
 [ESP and ESP profiles](/autopilot/enrollment-status)
 
-![A screenshot of an Enrollment Status Page on a Windows device.](../media/autopilot.png)
+![A screenshot of an Enrollment Status Page on a Windows device.](../media/autopilot.png)

learn-pr/device-partner-university/windows-autopilot/includes/4-other-capabilities.md

@@ -19,7 +19,9 @@ Pre-provisioning enhances efficiency and boosts user satisfaction during the ini
 
 This process takes place between the time the device leaves the factory and when it arrives at the end user. During this phase, an IT technician performs intermediate but automatic configurations, such as installing apps and adjusting settings.
 
-As a result, when end users sign in for the first time, they don't have to wait for any configurations to complete—they can jump right in and start using their device.
+ This process occurs after the device leaves the factory and before it reaches the end user. An IT technician initiates the technician phase, which automatically applies configurations—such as installing apps and applying settings—before the device is delivered.
+
+As a result, when end users sign in for the first time, most device setup work is already complete, so they can start using the device sooner.
 
 Learn more about [Windows Autopilot for pre-provisioned deployment](/autopilot/pre-provision) on Microsoft Docs.
 
@@ -36,5 +38,65 @@ Learn more about [Windows Autopilot for pre-provisioned deployment](/autopilot/p
 **Redeploying devices in a business-ready state**
 [Windows Autopilot Reset](/autopilot/windows-autopilot-reset) takes the device back to a business-ready state, allowing the next person to sign in and get productive quickly and simply.
 
-**Reducing the time spent deploying devices** 
-[Windows Autopilot device preparation](/autopilot/device-preparation/overview) simplifies device deployment by delivering consistent configurations, enhancing the overall setup speed, and improving troubleshooting capabilities.
+**Reducing the time spent deploying devices**
+[Windows Autopilot device preparation](/autopilot/device-preparation/overview) is the newer provisioning path for Windows devices. While it isn’t yet feature‑complete compared to traditional Windows Autopilot, it introduces a simpler, more resilient approach that improves deployment speed, reliability, and supportability.
+
+## Key advantages of Windows Autopilot device preparation
+
+### Faster and more reliable provisioning
+
+- Device preparation significantly reduces provisioning time.
+- It removes several enrollment and ESP dependencies that commonly cause timeouts or failures in classic Autopilot.
+- Result: more consistent first-boot experiences, especially at scale.
+- **Why this matters:** Traditional Autopilot ESP frequently blocks on app installs, policy timing, or network conditions.
+
+### Simplified enrollment flow
+
+- No Enrollment Status Page (ESP) dependency.
+- Device setup completes without forcing users to wait for apps or policies to finish installing.
+- **Why this matters:** ESP is the single largest source of Autopilot failures and support tickets.
+
+### Reduced user impact and better first-sign-in experience
+
+- Users reach the desktop faster.
+- Apps and policies continue installing after the user signs in.
+- **Why this matters:** Classic Autopilot often creates the perception that “the device is broken” due to long, opaque waits.
+
+### Lower operational complexity
+
+- Fewer Autopilot-specific profiles and settings to manage.
+- Leverages modern Intune provisioning behaviors instead of legacy Autopilot constructs.
+- **Why this matters:** Autopilot has accumulated technical debt; device preparation is intentionally minimal.
+
+### Improved resilience to app and policy issues
+
+- App failures do not block device readiness.
+- Noncritical apps no longer prevent users from accessing the device.
+- **Why this matters:** In classic Autopilot, one misconfigured Win32 app can halt the entire deployment.
+
+### Better alignment with modern device management
+
+- Designed for cloud-native, Entra ID–joined devices from day one.
+- Assumes continuous management post-sign-in instead of “everything must finish at OOBE.”
+- **Why this matters:** This matches how Windows, Intune, and Microsoft Entra ID now operate.
+
+### Easier troubleshooting and support
+
+- Clearer separation between provisioning and ongoing management.
+- Failures occur in normal Intune app/policy workflows, not during a fragile OOBE phase.
+- **Why this matters:** Support teams can use standard Intune diagnostics instead of Autopilot-specific logs.
+
+### Summary table
+
+| Area | Device Preparation | Traditional Autopilot |
+|------|--------------------|-----------------------|
+| Provisioning time | Shorter | Longer, ESP-bound |
+| ESP dependency | None | Required |
+| User wait time | Minimal | Often significant |
+| App failure impact | Nonblocking | Blocking |
+| Operational complexity | Lower | Higher |
+| Troubleshooting | Standard Intune | Autopilot-specific |
+
+### Bottom line
+
+Windows Autopilot device preparation is the strategic replacement for traditional Autopilot. It prioritizes speed, reliability, and operational simplicity while eliminating the ESP-driven fragility that has plagued Autopilot deployments for years.