When Tools Don’t Fit: Filling the Gaps with PowerShell
summary
PowerShell code actually calls vendor APIs like Microsoft Graph (Invoke-GraphRequest / invoke-restmethod) to retire Intune devices, rename Android enrollments, and pull log-collection files into SQL — those automations run reliably. Hidden endpoints come from browser DevTools and Fiddler; some APIs surface only after tracing a Python SDK. When no API exists, web cmdlets or Selenium plus a Phone Link SQLite MFA grabber produce results but prove brittle and high‑maintenance. Scripts include throttling/backoff, Teams notifications, and local database ingestion.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:47Enterprise tools patchwork
- 6:09Stable automations
- 18:18Intune retirement list automation
- 22:38Renaming Android devices in Intune
- 26:12Extending Intune log collection
- 37:55Defending automations
- 38:17Web scraping undocumented APIs
- 54:59Printer data collection automation
- 1:00:11Exonius API automation
- 1:08:17Windows 11 readiness report
- 1:11:04Act three: Automations not to share
- 1:11:48Grocery price comparison tool
- 1:14:55Selenium for banking
- 1:20:53Stream Deck PowerShell
- 1:22:18Q&A
related talks
25mCreating Automation with APIs and PowerShell
48mDevOps Not ClickOps - Making end user...
44mPowerShell, Graphs, Topology and Real Use Cases
48mThe easy way to an API
01h 34mM365 Automation using PowerShell in Azure Function
48mDevice Management With PowerShell
03h 03mline tools work better for you
01h 30mConjuring data with APIs