Autopilot Device Preparation (AutoPilot V2) Part 3: Automating Corporate Identifiers

Рет қаралды 1,106

Күн бұрын

With the importance of corporate identifiers in Autopilot V2 now established, we can explore various options.
Today I'll demonstrate how to automate the process of uploading a Windows PC as a corporate device. Additionally, we'll look at how to create an Azure automated workflow for adding a large number of devices.
Be warned, I did take a few minutes in the beginning to address a lot of seemingly negative thoughts on the new Autopilot, so feel free to skip the first 6 minutes or so if you just want to dive into the tech stuff.
My original post on setting up Azure automation with runbooks:
• How to run PowerShell ...
Scripts from this video:
github.com/stevecapacity/Intu...
Join the official Discord server
/ discord
Read more at
www.getrubix.com
Chapters
0:00:00 - Coffee shops and my stuff
0:01:22 - Rant on Autopilot negativity (feel free to skip)
0:06:40 - The corporate identifier Graph API
0:08:07 - Graph explorer example
0:08:56 - Differences
0:10:35 - Import through the API
0:11:35 - Use PowerShell to collect info and post
0:16:46 - Using the webhook
0:19:11 - Webhook script logic
0:22:47 - Automation account permissions
0:23:54 - Create the runbook
0:24:55 - Create a webhook
0:25:48 - Test time
0:27:16 - We're gonna need this
#intune #autopilot #windows10 #windows11 #microsoftgraph #azureadministrator #azure #powershellscripting #powershell #activedirectory #bitlocker #windows365 #zerotrust #certificate #entra #microsoftdefender #zerotrust

Пікірлер: 12

@upinsmoke-tv Ай бұрын

helpful! Thank you

@MrMarcLaflamme Ай бұрын

Our tenant is the same as your Rubix tenant (missing the CSV import part).

@MrMarcLaflamme Ай бұрын

Great script! I want to check out that automation video because I only used it for Update Management a while back and never really got into more use from it. The one weird thing I am noticing about this process compared to V1 is that V1 was done during OOBE, this one is pushed to devices that have already been enrolled. So all of the benefits that we got with V1 (customizing OOBE), can't happen the first time around for the new method and new devices. We've got the cart before the horse now.

@getrubix Ай бұрын

Correct. This is going to be for a very different use case VS APV1

@javierduran2757 Ай бұрын

Very helpful! Thank you

@paulwoodward8265 Ай бұрын

Great video, thanks. Great help for getting going with automation. Good points in the intro. There will be use cases for this, as you point out. But not my org. Not unless they come up something to manage the OOBE like V1 does, which feels unlikely given the design. There are valid reasons to be disappointed. It is hard to see why the new shiny ESP UI is exclusive to the V2 process. Same goes for the improved reporting and diagnostics. And the configuration UI in Intune is also better for V2. I'd like those things back ported, V1 needs some attention too, if it's not being abandoned. Then MS have said "We expect both environments to exist in parallel _for a while_ as we work to improve the experience and add more functionality." "For a while" is super vague, but it doesn't _feel_ like a long time. So that's going to press people's buttons when the new thing just can't ever do what the old thing does. The fact that it's also broken on launch just adds to the negative first impression. MS could've handled this a lot better, for sure.

@getrubix Ай бұрын

Thanks. I can completely understand that perspective. My hope is they eventually take the improved pieces of V2 and retro fit them to V1 long before they decommission it. But time will tell.