Documentation

Updates & Policies

Configure update behavior per app and tenant, trigger updates manually, and audit the full update execution history.

Policy Types

Type	Behavior
`auto_update`	Automatically triggers updates using saved deployment configuration
`notify`	Shows update availability without auto deployment
`ignore`	Suppresses update actions for the app
`pin_version`	Pins app to a specific version

Endpoints

Method	Path	Purpose
`GET/PATCH`	`/api/updates/available`	Read available updates and dismiss/restore entries
`POST`	`/api/updates/trigger`	Trigger single/bulk updates (max 10 per request)
`GET`	`/api/updates/history`	Read auto-update history and statuses
`GET/POST`	`/api/update-policies`	List and upsert policies
`GET/PATCH/DELETE`	`/api/update-policies/[id]`	Read, modify, or delete a specific policy

Trigger Behavior

Validates requested app update records for user + tenant context.
Ensures a policy exists (or derives one from prior deployment data).
Temporarily enforces auto-update for manual run execution.
Creates update history and packaging job records.
Restores original policy mode when manual trigger completes.

Safety Controls

Update logic applies failure thresholds, cooldown windows, and rate caps to reduce deployment risk.

Assignment Intents

When deploying an app (or triggering an update), IntuneGet supports four assignment intents that control how Intune installs the package:

Intent	Behavior
`Required`	Automatically installs the app on all targeted devices
`Available`	Makes the app available in Company Portal for users to install on demand
`Uninstall`	Removes the app from targeted devices
`Update Only`	Assigns as required but adds a requirement rule so that only devices where the app is already installed receive the update

Update Only for Discovered Apps

The Update Only intent is especially useful for discovered/unmanaged apps. It updates existing installations without force-installing the app on devices that do not already have it. See the Unmanaged Apps documentation for full details on how requirement rules are generated and the app-level caveat when mixing intents.