Skip to content

Configure WinGet Integration

Configure WinGet Integration

The App Catalog is populated automatically from the PowerStacks catalog index, so browsing, searching, and publishing all work out of the box. These settings live in Admin > Settings > WinGet Integration. A GitHub token is optional: you only need one for the “Show More Results” deep search or for higher rate limits when publishing a lot of apps. Per-app installer manifests are fetched from Microsoft’s WinGet repository on GitHub only when you publish an app.

Without a token, the catalog still populates and normal browse, search, and publishing all work; each app you publish makes only a few GitHub requests, well within GitHub’s anonymous limit. A token adds two things: the “Show More Results” deep search, and higher rate limits for high-volume publishing.

Without a tokenWith a token
Browse, search, publishWorksWorks
GitHub API requests60 per hour5,000 per hour
”Show More Results” deep searchNot available (browse, cached results, and exact package-ID lookups like Google.Chrome still work)Full search across the WinGet repository in real time

The deep search needs a token because GitHub’s code search API requires authentication.

To create and add the token:

  1. Go to GitHub Settings > Developer settings > Personal access tokens > Tokens (classic).
  2. Select Generate new token > Generate new token (classic).
  3. Give it a descriptive name, for example “App Store for Intune WinGet”.
  4. Select the public_repo scope.
  5. Select Generate token and copy the value (it starts with ghp_).
  6. In the portal, go to Admin > Settings > WinGet Integration, paste the value into GitHub Personal Access Token, and select Save.

The token is stored in Azure Key Vault and is never shown in logs or the UI.

By default the catalog uses Microsoft’s official repository, https://github.com/microsoft/winget-pkgs. Organizations that maintain an internal mirror can point this at their own repository (format: https://github.com/owner/repo or owner/repo).