App Management
The App Management page (Apps > App Management in the admin area) is your central hub for managing which Intune apps are available in the portal and how they behave.
Syncing Apps from Intune
Section titled “Syncing Apps from Intune”- Select the Sync Apps from Intune button
- The portal fetches all mobile apps from your Intune tenant
- Apps are imported with their name, publisher, description, icon, and category
- New apps are hidden by default. You must make them visible for users to see them.
Apps you publish from the App Catalog or App Upload appear in App Management, hidden, as soon as packaging completes. You don’t need Sync Apps from Intune for them.
Incremental Sync: After the first full sync, subsequent syncs are incremental, only new and modified apps are fetched from Intune. Each successful sync records when it asked Intune for apps, and the next incremental sync asks only for apps whose lastModifiedDateTime is later than that. Icons are fetched in parallel (5 concurrent requests) for faster sync times.
Scheduled Background Sync: A background service automatically syncs apps on a schedule:
- Nightly full sync at 2:00 AM UTC, ensures consistency
- Hourly incremental sync, picks up new and changed apps quickly, and checks for apps deleted in Intune
- The manual Sync Apps from Intune button is still available for on-demand syncs, and also checks for deleted apps
Apps Deleted in Intune
Section titled “Apps Deleted in Intune”When an app is deleted directly in Intune, including through another App Store instance, App Store notices within an hour:
- An app App Store holds nothing for, such as one another tool or App Store instance published, is removed from App Management once it has been missing for 30 minutes on two checks.
- An app App Store holds groups, update applications, version history or requests for is kept, so they can be cleaned up. App Management labels it Deleted in Intune, and Reports > Store Health lists it under Apps deleted in Intune. It can’t be made available, App Store doesn’t check it for updates, and requests for it are not reported as installed. If it was already visible, it stays in the store with Get: the store tells users it can’t be installed right now, and a request for it is recorded as Failed, with the reason shown in the requester’s My Requests and in Approvals > All Requests. Publish it again from the App Catalog, or remove it with Delete from Intune. No group is deleted.
Apps That Can’t Deliver Requests
Section titled “Apps That Can’t Deliver Requests”An app in the store needs a deployment group and an Intune assignment to that group before a request for it can be delivered. Reports > Store Health lists every visible app that’s missing one under Apps that cannot deliver, with what’s missing: no deployment group, no Intune assignment, or reconciliation needed. Approving a request for one of these apps fails, and the store tells people it can’t be installed right now. To fix an app, open it in App Management and choose its deployment group in App settings, or publish it again. Then deliver any request that failed in the meantime with Retry on Approvals > All Requests.
After an upgrade from 1.38 or earlier. In version 1.38, making an app visible from App settings with Auto-create group created its deployment group and Intune assignment, and then removed the group from the app in the same save, so approvals for the app added nobody to the group. App Store restores the group from the Intune assignment it created, within five minutes of starting after the upgrade, every hour after that, and whenever you select Sync Apps from Intune, whose message then says how many groups it restored and how many requests are waiting for Retry. Requests version 1.38 approved for these apps but never delivered are then listed as Failed in Approvals > All Requests, with the reason, and you deliver each one with Retry. App Store doesn’t add anyone to a group on its own. Reports > Analytics > Audit Trail records each restored group (App.DeploymentGroupRestored) and each request found (Request.MarkedUndelivered), by App Store.
Pagination: The portal follows @odata.nextLink pagination from the Graph API, so tenants with more than 999 apps are fully supported.
Filtering the App List
Section titled “Filtering the App List”The filter bar above the app table has six axes (v1.26.0+). All filters compose with the search box and persist while you navigate the tab:
| Filter | Values | Default |
|---|---|---|
| Platform | All platforms / Windows / iOS / Android / macOS / Web (only platforms present in your tenant) | All platforms |
| Visibility | All / Visible only / Hidden only | All |
| Category | All categories / (per-tenant categories) | All categories |
| Source | All / Store / Intune | All |
| Purpose | Install / Update / All | Install |
| Tag | All tags / (per-tenant tags) | All tags |
| Search | Free-text match against app name, publisher and primary category | empty |
Source distinguishes apps published through the App Store catalog flow (where the portal owns the lifecycle) from apps that already existed in Intune and were synced into the portal. Source = Store shows only apps with sourceWingetPackageId set, these are the apps where Version and Rollback, ring-based update deployments, and the Publish wizard apply.
Purpose distinguishes the user-facing Install Win32 app from the paired Update Win32 app that drives the two-app update model. The default is Install so the table shows the user-facing apps you’d expect; flip to Update when you need to inspect Update apps directly (for example to verify an Update app’s group assignments or ring activation state). The flag is set automatically during Intune sync by joining against UpdateDeployment.UpdateIntuneAppId, there is no manual classification step.
App Table Columns
Section titled “App Table Columns”The app list table is read-only and informational. Select any row to open the app’s detail view where you can edit settings.
| Column | Description |
|---|---|
| App | App name, icon, and publisher |
| Platform | App platform badge (Windows, iOS, Android, macOS, Web) |
| Type | App type from Intune (e.g., Win32, Microsoft Store, iOS Store) |
| Assigned | Status badge showing whether a target group is configured (Yes/No/N-A) |
| Visible | Status badge showing whether users can see this app in the portal (Yes/No/N-A) |
| Approval | Status badge showing whether approval is required (Yes/No/N-A) |
| Date Added | When the app was first synced or published |
Supported App Types
Section titled “Supported App Types”The portal supports self-service deployment for specific app types. When syncing apps from Intune, each app is classified by platform and support status:
| Platform | Supported Types | Unsupported Types |
|---|---|---|
| Windows | Win32, Microsoft Store (New) | Windows Universal (LoB), MSI (LoB), AppX (LoB) |
| iOS | iOS Store, iOS VPP | iOS (LoB) |
| Android | Android Store, Managed Google Play, Android for Work | Android (LoB) |
| Web | Web Apps | - |
| macOS | - | All macOS app types |
Why some types are unsupported:
- Line of Business (LoB) apps require special handling during deployment that the portal cannot automate
- macOS apps have different deployment mechanisms that are not yet implemented
Unsupported apps appear in the admin UI with their type displayed and an “N/A” status badge. Admins can see these apps exist but cannot make them available for self-service.
Configuring Individual Apps
Section titled “Configuring Individual Apps”Select any app row in the table to open its detail view. The detail view has two sections accessible from the left navigation:
- Overview, quick summary cards showing platform, visibility, approval status, assignment type, date added, and version
- Properties, grouped property sections (described below), each with an Edit link
Editing App Settings
Section titled “Editing App Settings”In the detail view, the Visibility & Store Settings, Approval Settings, Assignment Settings, and Deployment Options sections each have an Edit link. Each one opens the same App settings wizard, starting on the matching step. Making an app available to users in the App Store needs several of them together (you can’t be visible without an assignment, and Win32 assignments need deployment options), so the wizard lets you set them together, and you commit them with Save on its last step, Review + Save.
The App settings wizard has 5 steps:
| Step | Title | Fields |
|---|---|---|
| 1 | Visibility & Store | Visible in Store, Featured App, Categories, Tags, App Icon, Cost |
| 2 | Approval | Requires approval, Require acknowledgment before requesting, Approval for this app |
| 3 | Assignment | Assignment type, Target group, Assignment filter |
| 4 | Deployment Options | Install behavior, Restart behavior, Notifications, Grace period (Win32 only) |
| 5 | Review + Save | Summary of all changes with diff highlighting |
For non-Win32 apps the Deployment Options step is skipped automatically, the wizard jumps from Assignment directly to Review + Save.
Visibility Settings
Section titled “Visibility Settings”- Yes: App appears in the user-facing app catalog
- No: App is hidden from users but still tracked in the system
- N/A: App type is not supported for self-service deployment
Use this to control which Intune apps are available for self-service requests. Apps that shouldn’t be requested (system apps, dependencies, etc.) should remain hidden.
Featured App decides whether the app is featured in the store and in Company Portal. App Store sends it to Intune as the app’s Show this as a featured app setting, and only when you change it. If Intune doesn’t accept the change, your other changes are saved, Featured App keeps its previous value, and the message says why.
Hiding an app:
When you set Visible in Store to No in the App settings wizard and save, the app disappears from the store. App Store keeps its Intune assignment and its deployment group, so people who already have the app keep it, and making the app visible again reuses the same group. To remove the app from Intune, and to choose which of its groups to delete, use Delete from Intune.
An app that requires approval can’t be hidden. Turn off Requires approval and save first, and then hide the app. Automatic deployment setup:
When you make an app visible with Auto-create group (recommended) selected on the Assignment step, the portal automatically:
-
Creates an Entra ID Security Group named
{GroupNamePrefix}{Vendor} {AppName}-{arch}-{locale}-Required- Example:
AppStore-Mozilla Firefox-x64-en-US-Required. App Store drops characters other than letters, numbers, spaces, and hyphens, then leaves out the vendor when the app name starts with it, and leaves out the architecture or locale when it isn’t known. - The prefix is configurable under Store Administration > Deployment (default:
AppStore-) - There is no version in the name: later versions of the app reuse the same group
- Example:
-
Creates an Intune App Assignment
- The app is assigned as Required to the new security group
- Assignment type (User or Device) is based on the app’s Assignment setting
This automation ensures that when a user’s request is approved, they simply need to be added to the group and Intune handles the deployment.
Making the app visible fails, and the app stays hidden, when:
- Auto-create Entra ID groups for app assignment is cleared under Store Administration > Deployment.
- A group with the generated name already exists, for example one you kept when you deleted the app earlier. App Store doesn’t adopt it: choose it with Use an existing group instead.
- The existing group you chose was deleted in Microsoft Entra ID.
Changing the deployment group: when you change an app’s target group, App Store creates the assignment to the new group and removes the old one, for a visible or a hidden app alike. App Store first checks that the group you chose still exists. If it was deleted in Microsoft Entra ID, nothing is changed, and the message says: “The selected group was not found in Microsoft Entra ID, so nothing was changed. If you just created it, wait a minute and try again. Otherwise choose another group, or choose Auto-create group.” If Intune refuses to remove the old assignment, the portal says so and keeps a record of it, instead of reporting success.
Categories
Section titled “Categories”An app can belong to more than one category. Categories group the catalog into sections on the store home page and drive the Category filter, so an app listed under two categories appears in both.
Edit categories in the App settings wizard’s Visibility & Store step. They work the same way tags do: start typing to reuse an existing category or add a new one, and each category shows as a removable chip.
Categories stay in sync with Microsoft Intune in both directions:
- Categories you set in App Management reach Intune on the next sync.
- Categories set directly in Intune appear in the portal after a sync.
- Each sync reconciles both sides against the last synced state, so a category added on one side is not overwritten by the other.
Approval Settings
Section titled “Approval Settings”- Yes: Requests go through the configured approval workflow before completion
- No: Requests are auto-approved and the user/device is immediately added to the target group
- N/A: App type is not supported
If an app requires approval but no workflow can decide its requests, App Management labels it Approval not set up, and new requests are refused. Open the app and select Choose a workflow under Approval Settings, or create a default workflow under Automations > Approval Workflows.
Approval can only be turned on for a visible app. Trying it on a hidden app fails with “Cannot enable approval for an app that is not visible. Please make the app visible first.” Approval can also be turned on only when a workflow that can decide requests applies to the app. Otherwise the save fails with “Approvers have not been configured. Configure an approval workflow before enabling approvals for this application.” See Resolution order.
Delete from Intune
Section titled “Delete from Intune”From the app detail view, the Delete from Intune button removes an app from both Intune and the portal entirely. It appears only for apps backed by a real Intune app. For a catalog entry that was never deployed (a placeholder with a winget- prefix), there is nothing to remove, so the button is hidden.
Confirmation flow:
- Step 1, “Are you sure you want to delete [app name] from Intune?”
- Select Delete to proceed, or Cancel to abort
- Step 2 (only when App Store has deployment groups recorded for the app), Delete configuration groups? lists each group with its origin, and none is selected.
- Select the groups you also want deleted from Microsoft Entra ID, then select the delete button, which counts them, for example Delete 2 selected groups. Or select Keep all groups.
- The step warns that deleting groups can be destructive: App Store doesn’t check whether a group is used by other apps, assignments, automations or services. Deleting a group that another app is assigned to removes that assignment too, so select only groups you’re sure about.
- If App Store can’t read the app’s groups, it stops without deleting anything and asks you to try again.
What gets deleted:
| Action | Always | Only for groups you select |
|---|---|---|
| Install application removed from Intune | Yes | - |
| Update applications removed from Intune | Yes | - |
| Intune assignment removed | Yes | - |
| All associated requests removed | Yes | - |
| App record removed from portal | Yes | - |
| Microsoft Entra ID security group deleted | - | Yes |
A published app can own more than one application in Intune: the install application, and an update application for each rollout still inside your Number of update apps to retain setting. App Store also deletes the update applications, because an update application left behind would keep distributing software for an app you just deleted. It deletes only the update applications it recorded creating for this app, never an application found by its name.
If Intune refuses to delete the app itself, App Store stops and changes nothing: the app, its groups, and its requests stay as they were. If Intune refuses to delete one of the update applications, the app is still deleted and the confirmation names the application that was left behind so you can remove it in Intune. That message is worth reading rather than dismissing: once the app record is gone, App Store has no record of that application either.
After deletion, the app is completely removed from the portal. To restore it, publish it again from the App Catalog. If you kept its deployment group, choose that group with Use an existing group on the Assignment step before you make the app visible: Auto-create group fails when a group with the generated name already exists.
When to use Delete from Intune:
- You need to republish an app with updated settings (e.g., different silent switches, updated installer)
- An app deployment is in a bad state and needs to be recreated
- You want to permanently remove an app from both Intune and the portal
App Property Reference
Section titled “App Property Reference”The App settings wizard is where you edit every configurable app property. This section describes each field, grouped by the property section it appears on. Open the wizard by selecting Edit on the Visibility & Store Settings, Approval Settings, Assignment Settings or Deployment Options section of an app’s detail view.
App Details Section
Section titled “App Details Section”| Field | Description |
|---|---|
| Cost | Optional cost to display on app cards (informational only, no billing). Enter a decimal value or leave empty for “Free”. |
| Categories | One or more categories shown on app cards and used by the Category filter. Edit them as chips: start typing to reuse an existing category or add a new one. Categories stay in sync with Intune in both directions. See Categories. |
| Tags | Up to 10 free-form labels for organizing and filtering the catalog. Start typing to reuse an existing tag, or enter a new one. Give tags colors under Store Administration > Tags so they show as colored chips. See App Tags. |
Assignment Settings Section
Section titled “Assignment Settings Section”| Field | Description |
|---|---|
| Assignment Type | User (add requester to group) or Device (add requester’s device to group) |
| Which device | For Device assignment only: which of the requester’s devices the app installs on. See Assignment type. |
| Target Group | Choose Auto-create group (recommended), or choose Use an existing group, type at least two characters of the group name, and select the group. To remove the selection, select x. Dynamic membership groups aren’t listed. |
| Assignment Filter | Choose Include filtered devices in assignment or Exclude filtered devices in assignment, and then select a filter, or leave Don’t apply a filter. The filter list needs the managed identity’s DeviceManagementConfiguration.Read.All permission. |
Win32 Deployment Options Section
Section titled “Win32 Deployment Options Section”These options appear only for Win32 apps and control Intune deployment behavior:
| Field | Description |
|---|---|
| Install Behavior | System - Install for all users or User - Install for the signed-in user only |
| Device Restart Behavior | How to handle restart after install: Determine behavior based on return codes, Allow restart, Suppress restart or Force restart |
| End User Notifications | What users see: Show all notifications, Show reboot notifications only or Hide all notifications |
| Delivery Optimization Priority | Not configured, Foreground or Background |
| Allow User to Uninstall | Whether users can uninstall from Company Portal. The detail view calls it Allow Uninstall. |
| Restart Grace Period | Turn on and set Grace Period (minutes), Countdown (minutes), Allow Snooze and Snooze Duration (minutes) before a forced restart |
On the Review + Save step, select Save to apply your changes, or select Cancel to discard them.
App Icon
Section titled “App Icon”Each app displays an icon in the catalog. Icons are typically synced from Intune, but some apps may be missing an icon or need a different one. Set the icon in the App settings wizard’s Visibility & Store step, which offers three options:
- Upload Icon uploads a PNG or JPEG file of 1 MB or less from your computer. Intune accepts only these two formats, so other files are refused.
- Browse Library shows all unique PNG and JPEG icons already used by other apps in the portal. Search by app name or publisher, then select an icon to apply it. This is useful when multiple apps share the same publisher icon, or when you want to reuse an existing icon without re-uploading.
- Reset to Default appears when the app has a stored icon. It removes the stored icon, and the next sync fetches the icon from Intune again.
Assignment Type
Section titled “Assignment Type”Determines what gets added to the Microsoft Entra ID group when a request is approved:
- User: The requesting user is added to the group (most common)
- Device: The user’s device is added to the group (useful for device-targeted deployments)
Which Device (Device Assignment)
Section titled “Which Device (Device Assignment)”Choosing Device reveals a Which device setting that decides which of the requester’s devices the app installs on.

| Option | What happens |
|---|---|
| Let the user choose | The user picks from their devices when they request the app. Only devices that run the app’s platform and can receive apps are offered, and for a Windows app, only devices whose processor the app’s Intune requirement serves. This is the default, and every app that existed before this setting is set to it, so nothing changed on upgrade. |
| The device they are using | Installs on the device the request came from, even when the user is not its primary user. This is what lets someone install on a shared or secondary machine, and it is the reason this setting exists. If the store cannot identify the device, the user is asked to choose. |
| Their primary devices | Installs on every device where the user is the primary user in Intune. Never installs on a device they are only signed in to. |
| Both | The device they are using, together with their primary devices. |
Only The device they are using falls back to asking. Their primary devices deliberately does not: choosing that option means excluding machines the user is merely sitting at, so falling back would install on exactly the device you excluded.
Whichever option applies, the resolved device or devices are added to the target Microsoft Entra ID group and Intune deploys the app to them.
Permissions. Device assignment depends on the managed identity holding Device.Read.All, which the setup script grants. Group membership is added by Entra directory object, so a device has to be resolved to one before the app can reach it.
When the user chooses the device:
- The browser reports its operating system (Windows, macOS, iOS, Android).
- The device list offers the user’s Intune devices on the app’s platform, so a Windows app doesn’t list a phone. For a Windows app assigned to devices, it also lists only devices whose processor the app’s Intune requirement serves: an ARM64 device is offered the app only when the app targets ARM64 devices only. A device whose processor Intune doesn’t report is offered only when the app’s requirement excludes ARM64 devices, and the dialog says that Intune installs the app only on the devices its requirement names. For a request made on someone’s behalf, it lists the devices of the person the app is for. Approval and Retry check the devices again, leave out any that the requirement doesn’t serve, and say which were left out and why.
- A device is preselected in two cases:
- The user has only one device. It’s preselected without a mark.
- Exactly one of the user’s devices runs the browser’s operating system. That device is marked “(Same operating system as this browser)”, and the dialog says “Selected because it runs the same operating system as the browser you are using.” This doesn’t apply to a request made on someone’s behalf, where the browser’s operating system preselects nothing.
- Otherwise nothing is preselected, the dialog says “Choose the device to install on.”, and the user chooses before they can submit.
Configuring Approval Workflows
Section titled “Configuring Approval Workflows”Approval is set in the App settings wizard’s Approval step: open the app, and under Approval Settings, select Edit. For the full steps, see Use the App settings wizard.
No Approval Required
Section titled “No Approval Required”For apps where Requires approval is off, requests are auto-approved immediately. No workflow configuration is needed.
Simple Approval
Section titled “Simple Approval”For apps that just need one group to sign off:
- Select Requires approval.
- In Approval for this app, choose Custom for this app, and add a single pooled stage that names the Entra ID security group that should decide.
- Any member of that group can approve.
Manager + Additional Approvers
Section titled “Manager + Additional Approvers”- Select Require manager approval first. It is already selected when Require manager approval by default is selected on Automations > Approval Workflows.
- Choose the workflow type:
- Linear: Specific users approve in sequence
- Pooled: Any member of specified groups can approve
- Add at least one stage. App Store doesn’t save a workflow with no stages, even when Require manager approval first is selected.
Conditional Stages (v1.8.2)
Section titled “Conditional Stages (v1.8.2)”Each approval stage can be made conditional, so it only applies when specific criteria are met:
- In the app’s Approval step, choose Custom for this app.
- Add a stage and assign an approver or group.
- Select Make this stage conditional.
- Add conditions using the condition builder:
- Select a condition type: App cost, App category, App platform, App publisher, or Requester department
- Choose an operator, for example equals, does not equal, contains, or is one of. The operators offered depend on the condition type.
- Enter the comparison value
- Add multiple conditions with AND/OR logic
- A human-readable summary of the conditions is shown on the stage card
See Approval Workflows for detailed condition types and operators.
See Approval Workflows for detailed workflow configuration options.
Version History and Rollback
Section titled “Version History and Rollback”The portal tracks version history for apps published from the App Catalog, so you can roll back to previous versions if a new version introduces issues.
Viewing Version History
Section titled “Viewing Version History”- In the admin area, select Apps > App Management.
- Find the app in the app table, and select its row to open the app’s detail view.
- On the Version & Rollback card, select View full history…. The version history lists every recorded version.

Understanding Version Status
Section titled “Understanding Version Status”Each version in the history shows a status badge:
| Status | Description |
|---|---|
| Current | The version currently deployed in Intune |
| Archived | A previous version that was deployed. It offers Rollback when its package is still kept |
Version Information Displayed
Section titled “Version Information Displayed”For each version, you’ll see:
- Version number - The semantic version (e.g., “1.2.3”)
- Recorded date - When this version was detected/published
- Updated by - User who published this version (if available)
- Installer size - Size of the installer package
- Release notes - Change summary for this version
- Package ID - WinGet package identifier (e.g., “7zip.7zip”)
Rolling Back to a Previous Version
Section titled “Rolling Back to a Previous Version”If a new app version causes issues, you can roll back to a previous version. To restore the version just before the current one, select Roll back to previous version on the app’s Version & Rollback card and confirm; the confirmation names the version it restores. To choose another version:

- Open the version history for the app (see Viewing Version History).
- Find the version you want to roll back to. It must be Archived and show a Rollback button.
- Select Rollback on that version.
- Select Confirm Rollback to proceed.
- App Store:
- Takes the selected version’s package from the packages it keeps for rollback, and checks it against the digest recorded when it was kept
- Restores it as the content of the app’s install app in Intune, with that version’s App version, setup file, install and uninstall commands and detection rule, and checks that Intune kept them
- Marks the selected version Current
- Stops the rollouts of newer versions and withdraws their updater apps
- Declines the version you rolled back from and pauses automatic deployment (see below)
The install app keeps serving the current content until the restored content is committed, so devices never go without an assigned version. New installs then receive the restored version. Devices that already have the newer version keep it: Intune doesn’t uninstall it.
Which versions you can roll back to. Rollback returns only to an earlier version whose package App Store still keeps, that wasn’t withdrawn by a rollback, and whose updater app you didn’t delete. Number of rollback versions to retain sets how many packages are kept. When earlier versions exist but none can be restored, the app’s page says why. For an app published before version 1.39, including one published with version 1.38, the next update keeps the package of the version it replaces only if the packaging job that published that version is still listed under Packaging Jobs on the App Catalog page.
What a rollback reports:
- If the previous version changed after you confirmed, for example because an update finished or another administrator rolled the app back, nothing is rolled back, and the page says “Nothing was rolled back” and names the version that is now the previous one.
- One rollback of an app runs at a time. A second rollback of the same app is refused with a message while the first is still running.
- Known issue in version 1.39.0: a rollback can take about a minute, shows no progress, and leaves Roll back to previous version available. A second click is refused, and its “Nothing was rolled back” message replaces the card’s text although the first rollback succeeded. Nothing is rolled back twice. Select the button once and wait. If the card says nothing was rolled back, refresh the page and read Current Version before you try again.
- If a rollback takes so long that the page loses App Store’s answer, the page says the rollback may still be running. Refresh the page before you roll back again.
- If the rollback fails, the message says that it’s incomplete and what was written to Intune. Roll back again once Intune can be reached to repair it.
- If another change overtook the rollback in Intune, the message says that the app needs attention, and it stays on the app’s page.
Every rollback is written to the audit log.
A Rollback Pauses Automatic Updates for That App
Section titled “A Rollback Pauses Automatic Updates for That App”Rolling back says the newer version is bad, so App Store stops deploying newer versions of that app automatically:
- Automatic deployment is paused for that app, whatever the global or per-app auto-deploy setting says. In App Updates, the app’s row says Auto-deploy paused since and the date of the rollback, followed by (rollback), for example Auto-deploy paused since 10/20/2026 (rollback). Its detail view shows Paused by rollback under Auto-Deploy Updates, with the reason.
- Update checks carry on. When a version newer than the one you rolled back from is published, it appears in App Updates as normal, and you can select Deploy Update by hand. Doing so doesn’t end the pause.
- The version you rolled back from is declined: it shows as Declined and is never offered or deployed automatically. To deploy it anyway, select Deploy anyway and confirm that you are overriding the decline. This doesn’t end the pause either.
- A restart, a manual deployment or a later update check doesn’t end the pause.
To end the pause, select Resume Auto-Deploy on the app’s row or in its detail view, then confirm. Resuming is recorded in the audit log with who did it. It doesn’t un-decline the version you rolled back from.
Version History Limitations
Section titled “Version History Limitations”- WinGet apps only: Version history is only tracked for apps published from the App Catalog
- Manual Intune apps: Apps added directly to Intune (not via portal) do not have version history
- Retention: By default, App Store keeps the packages of three earlier versions you can roll back to (range 1 to 10). A version withdrawn by a rollback doesn’t count. Lowering the number permanently deletes the packages outside the new count, at each app’s next update. Change it with Number of rollback versions to retain, in Update Settings on the App Updates page. See Update retention.
Troubleshooting Rollback Issues
Section titled “Troubleshooting Rollback Issues”Roll back to previous version is unavailable, or a version has no Rollback button:
- Only Archived versions whose package App Store still keeps can be rolled back to. A version outside Number of rollback versions to retain has no package any more, and lowering that setting deletes packages permanently at each app’s next update.
- A version withdrawn by a rollback, or whose updater app you deleted, isn’t offered.
- The app’s page says why when earlier versions exist but none can be restored.
Rollback fails:
- Check that the App Service’s managed identity has the Microsoft Graph permission
DeviceManagementApps.ReadWrite.All - Read the message: it says what was written to Intune. Roll back again once Intune can be reached.
- Review the application logs for detailed error messages
Version history is empty:
- Version history only tracks apps published through the portal
- If you synced an existing Intune app, its pre-sync versions are not tracked
- Version history starts at an app’s first update. Until then, the version history shows no versions.