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
Негізгі бет Ғылым және технология Autopilot Device Preparation (AutoPilot V2) Part 3: Automating Corporate Identifiers
Пікірлер: 12