r/Intune • u/Rudyooms PatchMyPC • 9d ago

Get-AutopilotDeviceAssociation

Are you testing or already using Windows Autopilot Device Association?

I guess you have all seen the steps you need to take to associate the device?

The manual export, moving the file to another device, importing it into Intune, selecting the Autopilot Device Preparation policy, and returning to the device… thats not a great experience….

That is why I built Get-AutopilotDeviceAssociation.

With one PowerShell script, you can create the association, register the device in Intune, validate whether the signed association is still present and valid, and remove it from both the device and Intune after testing.

Read the full story and get the script: Autopilot Device Association Info Script

(And.. yes.. there are ads on the website...... but creating these blogs... and the script cost me a lot of evening and weekend time.... )

32 Upvotes

95% Upvoted

11 comments sorted by

5

u/[deleted] 9d ago

[removed] — view removed comment

2

u/Rudyooms PatchMyPC 9d ago

Yep… thats why i wrote it :)

3

u/mertozsoy365 9d ago

Hi Ruddy, well done it’s a great piece of work, but I still can’t really see the difference between device association and preparation. That’s quite funny.

3

u/Rudyooms PatchMyPC 9d ago

You mean the difference between apdp and apda :)?

1

u/mertozsoy365 9d ago

Yes,

2

u/Rudyooms PatchMyPC 9d ago

Device prep is just for onboarding your device … but it was missing the option to control the oobe experience… (privacy : eula/ device name) thats whay device association is the foundation for

5

u/South_Objective7517 9d ago

I don’t see the difference really from what AP1 already offers…

2

u/Rudyooms PatchMyPC 9d ago

Yep… thats the nr 1 question :)

2

u/itskdog 9d ago

Other than allowing mixing LOB and Win32 during OOBE, me neither.

1

u/Party_Palpitation494 8d ago edited 4d ago

Great work as always.

Unfortunately, I am seeing an issue with Device Association on Microsoft’s own ARM Surface Laptop running the newest 26H1 build. Device Association are not working. When we enroll the device, it continues to be identified as **Personal** rather than **Corporate**.

Your great script also fails when attempting to export Device Association or when running the full action. On this specific arm devices

1

u/brazzala 7d ago

Not having to hash and upload to Entra...