PatchPilot365 Documentation
A multi-tenant vulnerability management tool that orchestrates remediation for devices enrolled in Microsoft Defender and Intune.
What is PatchPilot365
PatchPilot365 watches every customer tenant an MSP manages for security findings from Microsoft Defender Vulnerability Management, then does something about them — dispatching fixes through Winget (for third-party apps) and Windows Update (for OS patches). Instead of jumping between separate Microsoft consoles for each customer, an engineer gets one place to see what’s exposed across the whole fleet and act on it.
It doesn’t replace Defender or Intune — it orchestrates them, using the access relationship (GDAP) the MSP already holds with each customer. There’s no agent to install on a customer’s devices; every finding and every fix goes through Microsoft’s own APIs.
PatchPilot365 is designed to run primarily as a virtual machine in Azure, deployed with one click, with support for on-premises or third-party hosting if you need it. A couple of things worth knowing up front:
- Tokens never touch the browser. Every Microsoft Graph/Defender call happens server-side.
- No standing credential for any customer. Every action runs with the signed-in engineer’s own access, for only as long as it takes.
Where to go next
| If you want to… | Go to |
|---|---|
| Stand up an instance and see it running | Getting Started |
| Understand how it connects to a tenant and reaches a device | Architecture |
| Check licensing, roles, and network prerequisites before you commit | Requirements |
| See what PatchPilot365 can’t do yet, before you hit it in the field | Known Issues |
| Find your way around a page you’re looking at right now | Navigating PatchPilot365 |
| Keep an already-running instance healthy | Server Health & Maintenance |
| Walk through a specific task step by step | User Guide |
This site covers using and operating PatchPilot365 as an MSP engineer or admin. For contributor-facing details (monorepo layout, running the test suite, internal design notes), see the repository README.