#Portal reloaded trigger bug update#
#Portal reloaded trigger bug windows 10#

This error can be resolved by configuring your virtual machine with a minimum of two processors and 4 GB of memory. Virtual machine failing at 'Preparing your device for mobile management' This issue is limited to the UI and shouldn't affect the deployment process.

There's a UI bug on Autopilot HAADJ deployments where the Enrollment Status page is displayed as a white screen. If you don't want the device to go through an Autopilot deployment, remove the Autopilot registration. It makes sure that all devices that you register with Autopilot go through the Autopilot experience. When a device is registered in Autopilot and no profile is assigned, it will take the default Autopilot profile. The grace period can be as short as 0.25 days.ĭevice goes through Autopilot deployment without an assigned profile For more information, see Conditional Access: Require compliant or hybrid Azure AD joined device.Ĭonditional Access policies such as BitLocker compliance require a grace period for Autopilot devices, because until the device has been rebooted the status of BitLocker and Secure Boot haven't been captured, and can't be used as part of the Compliance Policy. To resolve the conflict, a user must to sign in to the device, or the device-based policy must be modified. In this case, Conditional Access is behaving as intended. The temporary N/A compliance state can cause issues with device based Conditional Access polices that block access based on compliance. Intune only syncs with the Hybrid device ID after a successful user sign-in. The hybrid compliance state will display as N/A when viewed from the devices list in the Azure portal until a user signs in. Hybrid Azure AD devices: When Hybrid Azure AD devices are deployed with Autopilot, two device IDs are initially associated with the same device - one Azure AD and one hybrid. If a policy is in place such that all cloud apps require a compliant device (there's no exclusion list), Microsoft Intune Enrollment will already be excluded by default, so that the device can register with Azure AD and enroll with Intune and avoid a circular dependency. In this case, Microsoft Intune Enrollment and Microsoft Intune should be included in that exclusion list of policy 1. Conditional Access policy 2: Require a compliant device for the apps on the exclusion list.Conditional Access policy 1: Block all apps except those on an exclusion list.See Per-device terms of use.Įxceptions to Conditional Access policies to exclude Microsoft Intune Enrollment and Microsoft Intune cloud apps are needed to complete Autopilot enrollment in cases where restrictive polices are present such as: The Intune Enrollment app must be excluded from any Conditional Access policy requiring Terms of Use because it isn't supported. If there isn't an issue with the recovery environment, enter administrator credentials to continue with the reset process. When you attempt an Autopilot reset, you see the following message: Autopilot reset ran into trouble. It's in preview mode only and not recommended for production purposes at this time. When you use the EnableWebSignIn CSP, the defaultuserX profile may not be deleted.

#Portal reloaded trigger bug update#

To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device. As a result, any settings made in the profile may not be configured for the user such as device renaming.

#Portal reloaded trigger bug windows 10#

In Windows 10 April and some May update releases, there is an issue where the Autopilot profile may fail to apply to the device and the hardware hash may not be harvested. Known issues Autopilot profile not being applied when assigned For information about issues that can be resolved by applying a cumulative update, see Windows Autopilot - resolved issues. This article describes known issues that can often be resolved by configuration changes, or might be resolved automatically in a future release.