Important apps that are likely to be needed within the first 30 minutes to 1 hour of provisioning the device.Core productivity apps like Microsoft 365 Apps and Teams.Critical apps that if missing would lead to an inability to be secure or access core services (ex: VPN, antivirus, etc.).Required apps that can be installed as the device is usedĪpps that can be installed later from Company Portal The following table can be useful in planning what apps should be configured to block use of the device during the Enrollment Status Page:īlock device use until required apps are installed This post will provide a simple framework for evaluating those trade-offs and discuss how to configure the Enrollment Status Page within Microsoft Intune to meet your goals. Successful transition to Autopilot must begin with a careful evaluation of the approach and assumptions of “how” and “why” services are delivered by IT and requires making necessary changes to the experiences and expectations of both IT and users. However, carry-over of this legacy approach comes with trade-offs that may compromise your goals of delivering a better user experience and simplified setup with Autopilot. Blocking on all apps will most closely mimic what IT and users are familiar with in their existing deployment process where a fully configured device is delivered to the user. Those familiar with Windows operating system deployment using a custom “golden image” may want to block device use until all apps are installed. An available configuration is the option to block device use until apps are installed – preventing the user from accessing the desktop for the first time until the device is in an expected state.

The Enrollment Status Page is a feature of Microsoft Endpoint Manager that displays progress of preparing the device for management, applying policies, and installing apps during the out-of-box experience (OOBE) of Windows Autopilot. By Jon Callahan – Senior Program Manager | Microsoft Endpoint Manager

Office 365 view installed devices