DevOps Not ClickOps - Making end user...
summary
Claim: Intune still forces ClickOps workflows because APIs and tooling lag. Concrete tools used: PowerShell, Graph, Microsoft 365 DSC, Intune Backup & Restore, CI/CD pipelines (Python-based Intune CD shows install friction). Surprising numbers: device policy success is when it lands on devices which can take days so realistic targets are nearer 95%. Built prototype features: versioned publish, decoupled assignments, ringed deployments, audit reporting and a CIS-import demo that works end to end.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:04Agenda
- 4:32Problem: ClickOps in device management
- 7:19Limitations of IaC for Intune
- 10:48Azure vs Intune automation
- 14:01Existing Intune automation solutions
- 19:19Requirements for Intune automation
- 26:01Security for pipeline automation
- 28:56Best practices for Intune pipelines
- 33:52Assignments and change management
- 35:59Reporting and success metrics
- 37:23Why 100% deployment is impossible
- 41:36Importance of reporting and compliance
- 42:18Demo: Intune automation workflow
- 44:03Community collaboration
- 47:20Closing
related talks
39mPutting the Ops in DevOps
43mDevOps – when doing the right thing hurts!
37mDevOps - The Automation of Compliance
34mStop clicking and start committing: a GitOps workflow for endpoint management
36mDevOps is the answer! What was the question again?
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
48mContinuous Delivery: Tales from Windowsland
34mDevOps from an Auditor’s Perspective: A Meaningful Partnership to Drive Business Transformation
