Automating App Updates with Robopatch Flows
Apps get updated frequently — sometimes multiple times per month. Instead of manually importing every update, you can set up a Robopatch Flow that automatically packages and deploys new versions, with Deployment Waves to stage the rollout.
Video Walkthrough
What you'll need
- A connected Intune tenant with Admin Consent authorization
- Familiarity with importing apps and creating assignments
Patch groups and flows
This tutorial starts from an individual app. If you want several apps to share settings and deployment waves, you can instead create a patch group first, then add apps to it. Adding each app to the group creates its Robopatch flow.
A patch group exists independently of flows: you do not need to create a flow before creating the group. See Creating a patch group for the group-first sequence.
Step-by-Step Guide
1. Navigate to an app
You can set up a flow from two places:
- Recent Packages — find an app you've already imported (e.g. 7-Zip from the previous tutorial) and click Set up Robopatch Flow
- Instant Apps search — search for a new app (e.g. Notepad++) and click Setup Flow directly, skipping the analyze-and-build step entirely
2. Configure the flow
When you create a flow, you'll see these settings:
| Setting | Description |
|---|---|
| Flow name | Defaults to the app name (e.g. "Notepad++") |
| Platform | The installer type detected by Robopack (e.g. Nullsoft Installer) |
| Architecture | x64 or x86 |
| Scope | Machine or User scope |
| Script template | Your PSADT template (default provided) |
Click Create Flow.
There are additional advanced options on this screen. They are documented in the Robopatch feature reference — see Supersedence, Detection method options and Additional Intune properties. For now, the defaults work well.
3. Add Deployment Wave 1 — IT test computers
Click Add Deployment Wave. You can either create a new Entra ID group or use an existing one.
For a test group, it's best to use an existing group of known test devices:
- Click Existing Group
- Select your tenant
- Choose your test group (e.g. "IT Test Computers")
- Click Add Group to Wave
Then configure the wave thresholds:
| Setting | Example | Meaning |
|---|---|---|
| Minimum response rate | 60% | At least 60% of targeted devices must report a result (installed or failed) before Robopack checks the success rate; targeted devices are those that have checked in and picked up the assignment, not the whole group (see How the wave thresholds are calculated) |
| Minimum install success rate | 100% | 100% of targeted devices must report a successful install before the flow moves to the next wave; measured against all targeted devices, not only those that have reported so far |
| Delay after completion | Optional | Wait period before moving to the next wave (gives you time to verify) |
4. Add Deployment Wave 2 — broader rollout
Click Add Deployment Wave again and choose a broader group (e.g. "All Devices"). Choose the assignment type:
- Required — auto-installs on all devices in the group
- Available — appears in Company Portal for self-service
You can also add exclusion groups to a wave — Entra ID groups containing devices or users that should be excluded from the deployment.
For critical applications, set the Proceed Mode to Manual on a wave. This prevents Robopack from advancing automatically — you'll need to click Skip to next wave to approve the rollout.
5. Save and start deployment
Click Save and Start Deployment. From now on, every time the app vendor releases a new version:
- Robopack detects the update
- Builds and packages it automatically
- Deploys to Wave 1 (your IT test computers)
- Waits for the minimum response rate and minimum install success rate to be met
- Moves to Wave 2 (broader rollout)
You don't have to touch it again.
What's next?
Not every app is in the Instant Apps library. In the next tutorial, you'll learn how to deploy custom apps by uploading your own installers.