Generated banner for Msstore CLI
Generated logo for Msstore CLI

Msstore CLI

GitHubOfficialFirst committed by alvinashcraftDistributed by GitHub

  • Skill
  • Tool integration
  • Cloud and DevOps
  • MIT
  • No issues found

From the author

Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
— the description by alvinashcraft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Microsoft Store Developer CLI (msstore) provides a cross-platform interface for developers to interact with Partner Center APIs. It streamlines the lifecycle of Windows applications by enabling automated project initialization, packaging, submission, and flight management. Designed for integration into CI/CD pipelines, it supports various application frameworks including Windows App SDK, .NET MAUI, Flutter, Electron, React Native, and PWAs.

What it does

  • Configures and manages authentication credentials for Partner Center API access.
  • Initializes projects for Microsoft Store identity and packaging requirements.
  • Automates the packaging and publishing of application submissions.
  • Manages package flights for beta testing and gradual rollout configurations.
  • Retrieves application details and monitors submission status programmatically.
  • Integrates into automated CI/CD workflows for consistent release management.

When to use it

  • When you need to automate the release process of a Windows application to the Microsoft Store.
  • When managing beta testing groups or package flights via command line.
  • When setting up continuous deployment pipelines for Windows-based software.
  • When you need to programmatically update submission metadata or check status.

Advantages

  • Enables full automation of the Store publishing process.
  • Supports a wide range of modern application frameworks and cross-platform tools.
  • Facilitates CI/CD integration for faster release cycles.
  • Provides granular control over package rollouts and flight management.

Usage examples

“Initialize my WinUI project for the Microsoft Store.”
The CLI configures the project identity and prepares it for packaging and submission.
“Publish my application to the store with a 10 percent rollout.”
The tool submits the package and configures the store to release the update to 10 percent of users.
“Create a new beta flight for my application.”
The CLI creates a new flight group in the Partner Center for targeted testing.
“Check the status of my latest store submission.”
The tool returns the current processing status of the submission from the Partner Center.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/msstore-cli/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip msstore-cli.zip -d .agents/skills

Documentation by alvinashcraft

Microsoft Store Developer CLI (msstore)

The Microsoft Store Developer CLI (msstore) is a cross-platform command-line interface for publishing and managing applications in the Microsoft Store. It integrates with Partner Center APIs and supports automated publishing workflows for various application types.

When to Use This Skill

Use this skill when you need to:

  • Configure Store credentials for API access

  • List applications in your Store account

  • Check the status of a submission

  • Publish submissions to the Store

  • Package applications for Store submission

  • Initialize projects for Store publishing

  • Manage package flights (beta testing)

  • Set up CI/CD pipelines for automated Store publishing

  • Manage gradual rollouts of submissions

  • Update submission metadata programmatically

Prerequisites

  • Windows 10+, macOS, or Linux

  • .NET 9 Desktop Runtime (Windows) or .NET 9 Runtime (macOS/Linux)

  • Partner Center account with appropriate permissions

  • Azure AD app registration with Partner Center API access

  • msstore CLI installed via one of these methods:

    • Microsoft Store: Download

    • WinGet: winget install "Microsoft Store Developer CLI"

    • Manual: Download from GitHub Releases

Partner Center Setup

Before using msstore, you need to create an Azure AD application with Partner Center access:

  1. Go to Partner Center

  2. Navigate to Account settings > User management > Azure AD applications

  3. Create a new application and note the Tenant ID, Client ID, and Client Secret

  4. Grant the application appropriate permissions (Manager or Developer role)

Core Commands Reference

info - Print Configuration

Display the current credential configuration.

msstore info

Options:

OptionDescription
-v, --verbosePrint verbose output
reconfigure - Configure Credentials

Configure or update Microsoft Store API credentials.

msstore reconfigure [options]

Options:

OptionDescription
-t, --tenantIdAzure AD Tenant ID
-s, --sellerIdPartner Center Seller ID
-c, --clientIdAzure AD Application Client ID
-cs, --clientSecretClient Secret for authentication
-ct, --certificateThumbprintCertificate thumbprint (alternative to client secret)
-cfp, --certificateFilePathCertificate file path (alternative to client secret)
-cp, --certificatePasswordCertificate password
--resetReset credentials without full reconfiguration

Examples:

# Configure with client secret
msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET

# Configure with certificate
msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --certificateFilePath ./cert.pfx --certificatePassword MyPassword
settings - CLI Settings

Change settings of the Microsoft Store Developer CLI.

msstore settings [options]

Options:

OptionDescription
-t, --enableTelemetryEnable (true) or disable (false) telemetry
Set Publisher Display Name
msstore settings setpdn <publisherDisplayName>

Sets the default Publisher Display Name for the init command.

apps - Application Management

List and retrieve application information.

List Applications
msstore apps list

Lists all applications in your Partner Center account.

Get Application Details
msstore apps get <productId>

Arguments:

ArgumentDescription
productIdThe Store product ID (e.g., 9NBLGGH4R315)

Example:

# Get details of a specific app
msstore apps get 9NBLGGH4R315
submission - Submission Management

Manage Store submissions.

Sub-CommandDescription
statusGet submission status
getGet submission metadata and package info
getListingAssetsGet listing assets of a submission
updateMetadataUpdate submission metadata
pollPoll submission status until complete
publishPublish a submission
deleteDelete a submission
Get Submission Status
msstore submission status <productId>
Get Submission Details
msstore submission get <productId>
Update Metadata
msstore submission updateMetadata <productId> <metadata>

Where <metadata> is a JSON string with the updated metadata. Because JSON contains characters that shells interpret (quotes, braces, etc.), you must quote and/or escape the value appropriately:

  • Bash/Zsh: Wrap the JSON in single quotes so the shell passes it through literally.

    msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'
  • PowerShell: Use single quotes (or escape double quotes inside a double-quoted string).

    msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'
  • cmd.exe: Escape each inner double quote with a backslash.

    msstore submission updateMetadata 9NBLGGH4R315 "{\"description\":\"My updated app\"}"

Tip: For complex or multi-line metadata, save the JSON to a file and pass its contents instead to avoid quoting issues:

msstore submission updateMetadata 9NBLGGH4R315 "$(cat metadata.json)"

Options:

OptionDescription
-s, --skipInitialPollingSkip initial status polling
Publish Submission
msstore submission publish <productId>
Poll Submission
msstore submission poll <productId>

Polls until the submission status is PUBLISHED or FAILED.

Delete Submission
msstore submission delete <productId>

Options:

OptionDescription
--no-confirmSkip confirmation prompt
init - Initialize Project for Store

Initialize a project for Microsoft Store publishing. Automatically detects project type and configures Store identity.

msstore init <pathOrUrl> [options]

Arguments:

ArgumentDescription
pathOrUrlProject directory path or PWA URL

Options:

OptionDescription
-n, --publisherDisplayNamePublisher Display Name
--packageAlso package the project
--publishPackage and publish (implies --package)
-f, --flightIdPublish to a specific flight
-prp, --packageRolloutPercentageGradual rollout percentage (0-100)
-a, --archArchitecture(s): x86, x64, arm64
-o, --outputOutput directory for packages
-ver, --versionVersion to use when building

Supported Project Types:

  • Windows App SDK / WinUI 3

  • UWP

  • .NET MAUI

  • Flutter

  • Electron

  • React Native for Desktop

  • PWA (Progressive Web Apps)

Examples:

# Initialize WinUI project
msstore init ./my-winui-app

# Initialize PWA
msstore init https://contoso.com --output ./pwa-package

# Initialize and publish
msstore init ./my-app --publish
package - Package for Store

Package an application for Microsoft Store submission.

msstore package <pathOrUrl> [options]

Arguments:

ArgumentDescription
pathOrUrlProject directory path or PWA URL

Options:

OptionDescription
-o, --outputOutput directory for the package
-a, --archArchitecture(s): x86, x64, arm64
-ver, --versionVersion for the package

Examples:

# Package for default architecture
msstore package ./my-app

# Package for multiple architectures
msstore package ./my-app --arch x64,arm64 --output ./packages

# Package with specific version
msstore package ./my-app --version 1.2.3.0
publish - Publish to Store

Publish an application to the Microsoft Store.

msstore publish <pathOrUrl> [options]

Arguments:

ArgumentDescription
pathOrUrlProject directory path or PWA URL

Options:

OptionDescription
-i, --inputFilePath to existing .msix or .msixupload file
-id, --appIdApplication ID (if not initialized)
-nc, --noCommitKeep submission in draft state
-f, --flightIdPublish to a specific flight
-prp, --packageRolloutPercentageGradual rollout percentage (0-100)

Examples:

# Publish project
msstore publish ./my-app

# Publish existing package
msstore publish ./my-app --inputFile ./packages/MyApp.msixupload

# Publish as draft
msstore publish ./my-app --noCommit

# Publish with gradual rollout
msstore publish ./my-app --packageRolloutPercentage 10
flights - Package Flight Management

Manage package flights (beta testing groups).

Sub-CommandDescription
listList all flights for an app
getGet flight details
deleteDelete a flight
createCreate a new flight
submissionManage flight submissions
List Flights
msstore flights list <productId>
Get Flight Details
msstore flights get <productId> <flightId>
Create Flight
msstore flights create <productId> <friendlyName> --group-ids <group-ids>

Options:

OptionDescription
-g, --group-idsFlight group IDs (comma-separated)
-r, --rank-higher-thanFlight ID to rank higher than
Delete Flight
msstore flights delete <productId> <flightId>
Flight Submissions
# Get flight submission
msstore flights submission get <productId> <flightId>

# Publish flight submission
msstore flights submission publish <productId> <flightId>

# Check flight submission status
msstore flights submission status <productId> <flightId>

# Poll flight submission
msstore flights submission poll <productId> <flightId>

# Delete flight submission
msstore flights submission delete <productId> <flightId>
Flight Rollout Management
# Get rollout status
msstore flights submission rollout get <productId> <flightId>

# Update rollout percentage
msstore flights submission rollout update <productId> <flightId> <percentage>

# Halt rollout
msstore flights submission rollout halt <productId> <flightId>

# Finalize rollout (100%)
msstore flights submission rollout finalize <productId> <flightId>

Common Workflows

Workflow 1: First-Time Store Setup
# 1. Install the CLI
winget install "Microsoft Store Developer CLI"

# 2. Configure credentials (get these from Partner Center)
msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET

# 3. Verify configuration
msstore info

# 4. List your apps to confirm access
msstore apps list
Workflow 2: Initialize and Publish New App
# 1. Navigate to project
cd my-winui-app

# 2. Initialize for Store (creates/updates app identity)
msstore init .

# 3. Package the application
msstore package . --arch x64,arm64

# 4. Publish to Store
msstore publish .

# 5. Check submission status
msstore submission status <productId>
Workflow 3: Update Existing App
# 1. Build your updated application
dotnet publish -c Release

# 2. Package and publish
msstore publish ./my-app

# Or publish from existing package
msstore publish ./my-app --inputFile ./artifacts/MyApp.msixupload
Workflow 4: Gradual Rollout
# 1. Publish with initial rollout percentage
msstore publish ./my-app --packageRolloutPercentage 10

# 2. Monitor and increase rollout
msstore submission poll <productId>

# 3. (After validation) Finalize to 100%
# This completes via Partner Center or submission update
Workflow 5: Beta Testing with Flights
# 1. Create a flight group in Partner Center first
# Then create a flight
msstore flights create <productId> "Beta Testers" --group-ids "group-id-1,group-id-2"

# 2. Publish to the flight
msstore publish ./my-app --flightId <flightId>

# 3. Check flight submission status
msstore flights submission status <productId> <flightId>

# 4. After testing, publish to production
msstore publish ./my-app
Workflow 6: CI/CD Pipeline Integration
# GitHub Actions example
name: Publish to Store

on:
  release:
    types: [published]

jobs:
  publish:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Setup .NET
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '9.0.x'
      
      - name: Install msstore CLI
        run: winget install "Microsoft Store Developer CLI" --accept-package-agreements --accept-source-agreements
      
      - name: Configure Store credentials
        run: |
          msstore reconfigure --tenantId ${{ secrets.TENANT_ID }} --sellerId ${{ secrets.SELLER_ID }} --clientId ${{ secrets.CLIENT_ID }} --clientSecret ${{ secrets.CLIENT_SECRET }}
      
      - name: Build application
        run: dotnet publish -c Release
      
      - name: Publish to Store
        run: msstore publish ./src/MyApp

Integration with winapp CLI

The winapp CLI (v0.2.0+) integrates with msstore via the winapp store subcommand:

# These commands are equivalent:
msstore reconfigure --tenantId xxx --clientId xxx --clientSecret xxx
winapp store reconfigure --tenantId xxx --clientId xxx --clientSecret xxx

# List apps
msstore apps list
winapp store apps list

# Publish
msstore publish ./my-app
winapp store publish ./my-app

Use winapp store when you want a unified CLI experience for both packaging and publishing.

Troubleshooting

IssueSolution
Authentication failedVerify credentials with msstore info; re-run msstore reconfigure
App not foundEnsure the product ID is correct; run msstore apps list to verify
Insufficient permissionsCheck Azure AD app role in Partner Center (needs Manager or Developer)
Package validation failedEnsure package meets Store requirements; check Partner Center for details
Submission stuckRun msstore submission poll <productId> to check status
Flight not foundVerify flight ID with msstore flights list <productId>
Rollout percentage invalidValue must be between 0 and 100
Init fails for PWAEnsure URL is publicly accessible and has valid web app manifest

Environment Variables

The CLI supports environment variables for credentials:

VariableDescription
MSSTORE_TENANT_IDAzure AD Tenant ID
MSSTORE_SELLER_IDPartner Center Seller ID
MSSTORE_CLIENT_IDAzure AD Application Client ID
MSSTORE_CLIENT_SECRETClient Secret

References

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "msstore-cli", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of alvinashcraftalvinashcraft
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/msstore-cli · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
alvinashcraft

AutoGineer is not affiliated with or endorsed by alvinashcraft or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download msstore-cli.zip