> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/secure/intune/apps.md). # Apps {% hint style="info" %} This page is a branch of Intune, covering the **Apps** policy category specifically. See that page first for how Templates, Baselines, and Policies relate to each other in general — everything below assumes that model. {% endhint %} The Apps category manages **mobile app deployments** — registering an app with Intune (store app, line-of-business package, web link, or built-in app) and assigning it to users or devices as required, available, or set to uninstall. {% hint style="warning" %} Augmentt ships **no built-in default templates** for Apps. Every app you deploy through Augmentt is either a built-in/store app referenced from the tenant's own Intune/store catalog, or a package your organization has captured as a template. {% endhint %} {% hint style="warning" %} Templating itself is currently **unavailable for any app type that requires an uploaded installer** — Win32 apps, Windows MSI line-of-business apps, AppX/Windows Universal AppX, macOS PKG/DMG/LOB apps, and iOS/Android line-of-business apps. If you pick one of these types in the Create Template modal, you'll see "Creating templates for line-of-business apps is not supported right now." Only pure-metadata apps — store apps, web links, and VPP apps — can be saved as templates today. {% endhint %} ## What this category controls Apps live under Graph `/deviceAppManagement/mobileApps`. Two app types are treated as **built-in** by Augmentt (`#microsoft.graph.managedIOSStoreApp`, `#microsoft.graph.managedAndroidStoreApp`) — for these, assignments aren't supported at creation time, and editing after deployment is limited to the role scope tags plus the template's own name/description in Augmentt (app metadata itself is managed in Intune, not here). Newly created (non-built-in) apps that aren't yet published go through a **publishing-state poll** before Augmentt attempts to assign them — Augmentt polls for up to 30 seconds for the app to reach `publishingState: published` before proceeding, since some app types require that before assignments can be applied. ## Configuration surface ### Supported app types Augmentt recognizes the full range of Microsoft Graph mobile app types, grouped by platform: **Windows** * Microsoft 365 Apps (Windows 10 and later) * Windows MSI line-of-business app * Windows app (Win32) * Microsoft Store app (new) * Microsoft Store for Business app (legacy) * Windows app (AppX) / Windows Universal AppX * Microsoft Edge (Windows 10 and later) * Windows web link **macOS** * macOS Office Suite * macOS app (PKG) / macOS app (DMG) * macOS line-of-business app * macOS volume purchase program (VPP) app * Microsoft Edge (macOS) * macOS web clip * Microsoft Defender for Endpoint (macOS) **iOS/iPadOS** * iOS store app / iOS line-of-business app / iOS volume purchase program (VPP) app * iOS/iPadOS web clip * Built-in iOS app (assignment-limited, as above) * Managed iOS line-of-business app **Android** * Android store app / Managed Google Play store app * Android Enterprise system app * Android line-of-business app * Android for Work app * Built-in Android app (assignment-limited, as above) * Managed Android line-of-business app **Cross-platform** * Web link ### App metadata and identity * App information: name, description, developer, owner, privacy information URL, information URL, "featured app" flag. * Identity: bundle ID (Apple), package ID (Android), product code / product version (Windows MSI). * Version: version name, version code/number, build number. * VPP token name (for volume-purchase-program apps). ### Device requirements * Minimum operating system (iOS/Android version, or minimum supported Windows release, e.g. `1607`). * Allowed processor architectures (32-bit / 64-bit / ARM64). * Minimum free disk space (MB), minimum memory (MB), minimum number of processors, minimum CPU speed (MHz). * iOS device-type applicability: iPad vs. iPhone/iPod. ### Install behavior (Win32/MSI/LOB apps) * Install command line and uninstall command line. * MSI-specific: command-line arguments, ignore-version-detection toggle (skip MSI product-version check). * Run-as account for the install. * Device restart behavior after install: suppress, force, or based on the installer's return code. * Restart grace period, restart countdown display timing, and whether the user can snooze the restart notification (with a configurable snooze duration). * Return codes — a JSON array mapping installer exit codes to outcome type (success, soft reboot, hard reboot, retry). * Detection rules — a JSON array of rules Intune uses to determine whether the app is already installed. ### Web link / store apps * App store URL / app URL, file name. * "Use managed browser" toggle (opens the link in the Edge managed browser instead of the system default). * Managed store apps don't support a custom description (inherited from the store listing). ### Assignment * Intent: required, available for enrolled devices, available without enrollment, or uninstall. * Target: all users, all devices, or specific groups, in included or excluded mode (a group can be reused as included in one assignment and excluded in another, but not both within the same assignment). * End-user notifications: show all toast notifications, hide all, or show only for computer restarts. * Installation deadline (as soon as possible, or a specific date/time) and time zone for that deadline (UTC or device time zone). * Available license count / total license count are surfaced as read-only, license-related metadata (VPP-backed apps). ## Resolves posture check(s) {% hint style="warning" %} No default templates ship for this category, and Augmentt's `SECURE_CHECK_TYPES` / `COMPLIANCE_AUDIT.*` posture-check engine has no dedicated Apps/mobile-app-deployment check. Apps deployment is an inventory/provisioning capability rather than a security-hardening one. {% endhint %} ## Related pages * Intune * App Protection * App Configuration --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdesk.augmentt.com/modules/secure/intune/apps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.