Windows Autopilot: notes from the field

Hi Cristina_Osorio,

i sadly was not able to send a new post anymore, so I answering to your reference post.
Sorry for that.

I have a question to your explanations regarding missing AAD entries around 10:40 in the video.

You said that "We altough check that azure ad object exist and if it's not there we auto-remediate."

Is this a new behaviour?

In the past we had devices, from which not only the old stale intune entries but altough the aad entries were deleted via graphAPI.

In late 2021 and early 2022 it seemed that the devices still could be enrolled, but since ~ april/may 22 it seemed that they could no be re-enrolled (after re-imaging them) again, because only consumer OoBE was shown on the device, so enrollment profile was not applied/downloaded to the device.
And of course, how should enrollment profile be assigned if AAD object doesn't exist?

So we had to manually delete affected devices, harvest a hash of the device and re-import it to AutoPilot/DDS that altough re-creates the AAD object (named with the serial number of the hardware) in may 2022.

But your explanations described above, let me hope that this accidently deleted devices should be re-enrolled without re-importing them now.

Did I understand correctly?

Is this maybee a change altough happend with Return of key functionality for Windows Autopilot sign-in and deployment experience ?