Hi Intunestuff, this change is unrelated to the join type used for the
device during Autopilot and does not impact that functionality in any
way, however, we do (and have for multiple years now) strongly suggest
that orgs avoid using hybrid join for newly provisioned Windows
endpoints and in particu...
H Tbag76, That is correct. If this will significantly, impact your org,
you can either request an exception for your tenant or begin using
corporate identifiers for Windows.
Hi lasse nilsson, If you disable the enrollment of personal devices in
your tenant and the devices are not registered for Autopilot, that is
correct, you will not be able to leverage this scenario. Workarounds
include requesting an exception for your tenant, registering the devices
for Autopilot, or...
Hi @Manish Bangia, No, this change is not specific to device preparation
Autopilot. Using the Autopilot for existing devices functionality does
not require you to register a device for Autopilot. As called out, this
scenario enabled a possibly undesirable path that could be considered a
security or ...
Other MDM's have similar issues, the general recommendation is to target
the devices with the FileVault Configuration Profile and have FileVault
enable as the user logs in for the first time rather than encrypting
during setup assistant.
Latest Comments