
Endpoint Management
Self-Maintaining Intune App Catalogue with AI
How I built a self-maintaining Intune app catalogue: Graph API pulls inventory, AI classifies it, and surfaces your MSIX migration shortlist automatically.
By Paul Bentley12 min read
Practical AI for Endpoint Management · Part 1 of 1
On this page
- Why manual catalogues die
- Architecture
- What Graph API gives you
- Managed apps
- Detected apps
- The gap
- Building the sync flow
- The AI classification step
- Five categories
- The prompt matters
- Two implementation paths
- The catalogue as a living asset
- From catalogue to migration backlog
- Running it in practice
- First run
- Steady state
- Where this goes next
In Part 4 of the Windows Endpoint Management series, I described the catalogue problem in about 200 words and waved my hands at a solution. Graph API, Power Automate, AI classification: the building blocks were named but not assembled. This post is the 4,000-word version where we actually build the thing.
Someone asks "what applications do we have deployed?" and the answer takes three weeks of archaeology through Intune portals, spreadsheets of varying vintage, and conversations with people who left the organisation two years ago. The catalogue that was supposed to answer this question died quietly in a SharePoint list that nobody updated after March.
This post fixes that. Spreadsheet discipline has already been tried, and it didn't hold. A pipeline that maintains the catalogue automatically, enriches it with AI, and surfaces the outputs you need for migration and governance decisions does the job instead.