Prerequisites
Required permissions: Admin or Staff role with access to Endpoint Management > Software
Supported platforms: Windows, macOS, iOS, iPadOS, Android, Linux
Time estimate: a few minutes per app added
Additional requirements: a platform's Mobile Device Management (MDM) must be active before you can deploy apps to it
Before You Start
Software (Endpoint Management > Software) is where you keep a catalog of applications, add new ones, track their versions, and see where each one has been requested or installed. It covers Windows, macOS, iOS, iPadOS, Android and Linux.
Each platform supports its own acquisition sources — for example the Trio App Catalog or a Microsoft Store app for Windows, Apple Apps and Books (VPP) or a DMG/PKG upload for macOS, Managed Google Play or an APK/web app for Android, and APT or DNF packages for Linux. Trio shows only the sources that are actually connected for your tenant.
Step 1: Open the app catalog
Go to Endpoint Management > Software > Catalog.
The catalog lists every app you've added, with its platform, source, latest version, requirement level and current status.
Expected result: a table of your applications. Each row shows Application, Platform, Source, Latest version, Requirement and App status (for example current, update available, required missing or failed).
Step 2: Add an app
Click Add app.
Choose a platform, then an acquisition source for that platform. Sources marked connected are ready to use; an upload source needs a file (MSI/MSIX/EXE for Windows, DMG/PKG for macOS, IPA for iOS/iPadOS, APK for Android).
The wizard then asks for the app's details (name, publisher, description and version where the source doesn't already supply them) before you review and save it.
Expected result: the app appears in your catalog.
Troubleshooting this step:
Issue: a source shows "Unavailable in this path" or isn't listed → Solution: that source isn't connected for this platform yet; connect it in Platform setup, or pick a different source.
Issue: upload is rejected → Solution: confirm the file extension matches the platform (MSI/MSIX/EXE, DMG/PKG, IPA or APK) and is under the upload size limit.
Step 3: Check an app's versions
Open an app from the catalog, then its Versions tab. Each version shows its status (Ready, Processing, Failed or Archived), file size, SHA-256 checksum, and when it was added. Blueprints always install the latest ready version — versions can't be pinned per Blueprint. If a version's upload doesn't finish within 24 hours it's archived automatically; upload the file again to try once more.
Step 4: Deploy an app
From the catalog or an app's page, click Plan app change.
Choose the apps and the Blueprint or devices to apply the change to, then review and save.
Expected result: a deployment request is created. This is a request, not a confirmed install — check the app's Device reports tab or the App status page afterward to see what devices actually report.
Removing an app
Open the app and use Delete app. If it's required by one or more Blueprints, Trio tells you so and removes it from them first when you confirm; devices then stop receiving it through Trio.
Next Steps
Immediate actions:
Check App status regularly for failed installs or required apps still missing on some devices.
Check Sources & licenses if a source shows an expiring or missing connection — new apps from that source can't be added until it's fixed.
Troubleshooting
Symptom: a source I need isn't offered → Cause: that source isn't connected for this tenant/platform. → Solution: connect it in Platform setup, then try adding the app again.
Symptom: app status stays "required missing" → Cause: the device hasn't reported installing it yet, or can't reach the source. → Solution: check the app's Device reports tab for that device.
Symptom: a version shows "Failed" → Cause: the upload didn't finish or was rejected. → Solution: upload the file again as a new version.
This article was updated to match the current Software catalog, add-app, versions and delete flow. Screenshots are being added in a follow-up pass.