Version 1.37.0 August 5, 2026

Release Date: August 5, 2026

Summary

This release adds two ways to target work more precisely. Group Automations, a preview feature, keeps a Microsoft Entra device group in sync with the devices that have a given app installed, refreshed daily from BI for Intune, so you can aim an app update at only the devices that need it instead of everyone. Reusable approval workflows let you define an approval process once and share it across apps, with a tenant default that new apps inherit automatically. The release also stops repeated sign-in prompts in the admin console and makes the App Catalog load more reliably.

New Features

• Group Automations (preview): device groups that follow installed software. Group Automations keeps a Microsoft Entra device group in sync with the devices that have a given app installed, refreshed once a day from BI for Intune. Point an App Update or a ring deployment at that group and only the devices that actually have the app receive it, instead of targeting All Devices or All Users. A new Group Automations tab holds a one-time BI for Intune connection (the Power BI workspace and semantic model IDs, with a Test connection button) and the list of automations. Each automation includes a device when its installed apps match all or any of a set of conditions on application name, publisher, and version, and targets an Entra group you create or reuse. A live preview shows how many devices match, listed by device name, before you save. Reconciliation runs once a day, tenant wide, one automation at a time; it adds and removes only the difference rather than rebuilding the group, and a run that matches zero devices or errors is skipped, so a data glitch cannot empty a group. As a preview feature it may change before general availability, and may be withdrawn if it does not meet our quality, performance, and scale expectations, so we do not recommend depending on it for critical production workloads yet. Requires BI for Intune with populated app inventory on a Power BI Pro workspace, App Store’s managed identity added to that workspace with Build permission, and the managed identity granted Device.Read.All (or Directory.Read.All) in Microsoft Graph so it can resolve a matched device to its Entra object.
• Reusable approval workflows. An approval workflow can now be defined once and shared across apps, instead of configured on every app. A new Approval Workflows page lists reusable, named workflows and lets you create, edit, set a default, and delete them, with a count of how many apps use each. One workflow is the tenant default, so any app that requires approval uses it automatically. Each app’s approval settings offer three choices: use the default workflow, use a specific shared workflow, or define a custom workflow just for that app. When a request is submitted, the effective workflow resolves in that order: the app’s custom override, then its selected shared workflow, then the tenant default, then a single approval stage using the global approver group.

Product Enhancements

• A new Automations area in the admin navigation groups Group Automations and Approval Workflows together, and the one-time BI for Intune connection now lives under Settings.
• The App Catalog is served from the published catalog index without a per-package GitHub sweep. The proactive enrichment that fetched a manifest for every catalog package on startup and daily refresh was redundant with the index and the packaging-time fetch, and could hit GitHub rate limits, so it is now off by default. It can be re-enabled with the Winget:GitHubEnrichmentEnabled setting if the index ever needs supplementing.

Bug Fixes

• Resolved repeated sign-in prompts in the admin console. When a page opened several requests at once and the access token had expired, each request could start its own sign-in, so you were prompted more than once in a row. Interactive sign-in is now handled a single time, so only one prompt is shown.
• The App Catalog seed import no longer fails when a package lists its installer as a single object instead of an array. One such entry previously aborted the entire seed import and left the catalog empty on first start; the import now accepts either shape.