Use Microsoft Store Developer CLI (msstore) to configure Partner Center credentials, list Store apps, package and publish Windows submissions, check status, manage package flights, gradual rollouts, and CI/CD publishing for Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA apps. Use when asked to configure Store credentials, publish to Microsoft Store, check submission status, or automate Store releases.
Use msstore and its winapp store equivalent to authenticate with Partner Center, manage Microsoft Store apps, publish submissions, inspect flights, and automate release workflows.
When to invoke
"Configure msstore credentials for Partner Center."
"Publish this Windows app to the Microsoft Store."
"Check my Store submission status."
"Set up CI/CD for Store publishing."
"Manage package flights or gradual rollout with msstore."
Prerequisites and context
Requirement
Details
OS
Windows 10+, macOS, or Linux.
Runtime
.NET 9 Desktop Runtime on Windows, or .NET 9 Runtime on macOS/Linux.
Account
Partner Center account with appropriate permissions.
Azure app
Azure AD application with Partner Center API access.
Supported app types
Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
Install options
Microsoft Store, WinGet, or manual GitHub release download.
Install options:
winget install "Microsoft Store Developer CLI"
Use the Microsoft Store package at https://www.microsoft.com/store/apps/9P53PC5S0PHJ or manual releases at https://aka.ms/msstoredevcli/releases when WinGet is not appropriate.
Partner Center setup
Go to https://learn.microsoft.com/en-us/partner-center/ and open Partner Center.
Navigate to Account settings > User management > Azure AD applications.
Create an application and record Tenant ID, Client ID, and Client Secret.
Grant the application the Manager or Developer role.
Configure credentials with msstore reconfigure or environment variables.
Use winapp store when the workflow benefits from a unified CLI for both packaging and publishing. The winapp CLI supports this integration in v0.2.0+.
Store workflow coverage
Workflow
What to check
Configure credentials
Tenant ID, Client ID, Client Secret, Seller ID, and Partner Center role.
List applications
Product ID and app identity from msstore apps list.
Package for submission
App package meets Store validation for the target framework.
Publish submission
Package path, metadata, target product, and rollout intent.
Package flights
Flight ID exists and target audience is correct.
Gradual rollout
Rollout percentage is between 0 and 100.
CI/CD
Secrets stored in the CI secret store, not in source files.
Metadata updates
Submission metadata is intentional and reviewable.
Troubleshooting
Issue
Likely cause
Solution
Authentication failed
Bad credentials or expired secret
Verify with msstore info; re-run msstore reconfigure.
App not found
Wrong product ID or account
Run msstore apps list to verify.
Insufficient permissions
Azure AD app lacks Partner Center role
Grant Manager or Developer in Partner Center.
Package validation failed
Package does not meet Store requirements
Check Partner Center validation details.
Submission stuck
Status needs polling or review
Run msstore submission poll <productId>.
Flight not found
Wrong flight ID
Verify with msstore flights list <productId>.
Rollout percentage invalid
Value outside allowed range
Use a value from 0 to 100.
Init fails for PWA
URL or manifest problem
Ensure URL is publicly accessible and has a valid web app manifest.
Progressive disclosure and bundled resources
references/commands-and-workflows.md: detailed Microsoft Store CLI commands and publishing workflows. Open it when invoking msstore commands or following a publish/configuration workflow.
msstore is a cross-platformcommand-line interface; runtime wording may use macOS/Linux. The WinGet command may appear exactly as winget install "Microsoft Store Developer CLI".
Output template
## Microsoft Store CLI result
**Status:** complete | blocked
**Workflow:** `configure | list apps | publish | submission status | flight | rollout | CI/CD`
### Commands
| Command | Result | Evidence |
| --- | --- | --- |
| `msstore <command>` | `<pass/fail/not run>` | `<output summary>` |
### Store context
- Product ID: `<productId or unknown>`
- Flight ID: `<flightId or not applicable>`
- Credentials source: `environment | msstore config | not configured`
Quality gate
Required runtime, Partner Center account, and Azure AD application prerequisites were checked for the requested workflow.
Credentials used msstore reconfigure, winapp store reconfigure, or MSSTORE_TENANT_ID, MSSTORE_SELLER_ID, MSSTORE_CLIENT_ID, and MSSTORE_CLIENT_SECRET.
Secrets were not printed, committed, or included in output.
Product ID and flight ID were verified before status, publish, flight, or rollout operations.
Rollout percentages were validated as 0 through 100.
winapp store was used only when a unified packaging and publishing CLI was useful.
1---2name: msstore-cli-33description: Use Microsoft Store Developer CLI (msstore) to configure Partner Center credentials, list Store apps, package and publish Windows submissions, check status, manage package flights, gradual rollouts, and CI/CD publishing for Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA apps. Use when asked to configure Store credentials, publish to Microsoft Store, check submission status, or automate Store releases.4license: MIT5---67<!-- Generated from harness/github-copilot/plugins/dotnet-desktop-development/skills/msstore-cli/SKILL.md by harness/claude-code/scripts/convert_from_copilot.py. Edit the source, not this file. -->89# Microsoft Store Developer CLI1011Use `msstore` and its `winapp store` equivalent to authenticate with Partner Center, manage Microsoft Store apps, publish submissions, inspect flights, and automate release workflows.1213## When to invoke1415- "Configure msstore credentials for Partner Center."16- "Publish this Windows app to the Microsoft Store."17- "Check my Store submission status."18- "Set up CI/CD for Store publishing."19- "Manage package flights or gradual rollout with msstore."2021## Prerequisites and context2223| Requirement | Details |24| --- | --- |25| OS | Windows 10+, macOS, or Linux. |26| Runtime | .NET 9 Desktop Runtime on Windows, or .NET 9 Runtime on macOS/Linux. |27| Account | Partner Center account with appropriate permissions. |28| Azure app | Azure AD application with Partner Center API access. |29| Supported app types | Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications. |30| Install options | Microsoft Store, WinGet, or manual GitHub release download. |3132Install options:3334```bash35winget install "Microsoft Store Developer CLI"36```3738Use the Microsoft Store package at `https://www.microsoft.com/store/apps/9P53PC5S0PHJ` or manual releases at `https://aka.ms/msstoredevcli/releases` when WinGet is not appropriate.3940## Partner Center setup41421. Go to `https://learn.microsoft.com/en-us/partner-center/` and open Partner Center.432. Navigate to Account settings > User management > Azure AD applications.443. Create an application and record Tenant ID, Client ID, and Client Secret.454. Grant the application the Manager or Developer role.465. Configure credentials with `msstore reconfigure` or environment variables.4748## Credential configuration4950| Environment variable | Description |51| --- | --- |52| `MSSTORE_TENANT_ID` | Azure AD Tenant ID. |53| `MSSTORE_SELLER_ID` | Partner Center Seller ID. |54| `MSSTORE_CLIENT_ID` | Azure AD Application Client ID. |55| `MSSTORE_CLIENT_SECRET` | Client Secret. |5657Equivalent direct configuration:5859```bash60msstore reconfigure --tenantId xxx --clientId xxx --clientSecret xxx61winapp store reconfigure --tenantId xxx --clientId xxx --clientSecret xxx62```6364Do not print or commit `MSSTORE_CLIENT_SECRET`.6566## Command map6768| Task | `msstore` | `winapp store` equivalent |69| --- | --- | --- |70| Verify auth/account | `msstore info` | `winapp store info` |71| List apps | `msstore apps list` | `winapp store apps list` |72| Publish package/app folder | `msstore publish ./my-app` | `winapp store publish ./my-app` |73| Poll submission | `msstore submission poll <productId>` | `winapp store submission poll <productId>` |74| List flights | `msstore flights list <productId>` | `winapp store flights list <productId>` |7576Use `winapp store` when the workflow benefits from a unified CLI for both packaging and publishing. The winapp CLI supports this integration in v0.2.0+.7778## Store workflow coverage7980| Workflow | What to check |81| --- | --- |82| Configure credentials | Tenant ID, Client ID, Client Secret, Seller ID, and Partner Center role. |83| List applications | Product ID and app identity from `msstore apps list`. |84| Package for submission | App package meets Store validation for the target framework. |85| Publish submission | Package path, metadata, target product, and rollout intent. |86| Package flights | Flight ID exists and target audience is correct. |87| Gradual rollout | Rollout percentage is between 0 and 100. |88| CI/CD | Secrets stored in the CI secret store, not in source files. |89| Metadata updates | Submission metadata is intentional and reviewable. |9091## Troubleshooting9293| Issue | Likely cause | Solution |94| --- | --- | --- |95| Authentication failed | Bad credentials or expired secret | Verify with `msstore info`; re-run `msstore reconfigure`. |96| App not found | Wrong product ID or account | Run `msstore apps list` to verify. |97| Insufficient permissions | Azure AD app lacks Partner Center role | Grant Manager or Developer in Partner Center. |98| Package validation failed | Package does not meet Store requirements | Check Partner Center validation details. |99| Submission stuck | Status needs polling or review | Run `msstore submission poll <productId>`. |100| Flight not found | Wrong flight ID | Verify with `msstore flights list <productId>`. |101| Rollout percentage invalid | Value outside allowed range | Use a value from 0 to 100. |102| Init fails for PWA | URL or manifest problem | Ensure URL is publicly accessible and has a valid web app manifest. |103104## Progressive disclosure and bundled resources105106- `references/commands-and-workflows.md`: detailed Microsoft Store CLI commands and publishing workflows. Open it when invoking `msstore` commands or following a publish/configuration workflow.107108`msstore` is a `cross-platform` `command-line` interface; runtime wording may use `macOS/Linux`. The WinGet command may appear exactly as `winget install "Microsoft Store Developer CLI"`.109110## Output template111112```markdown113## Microsoft Store CLI result114115**Status:** complete | blocked116**Workflow:** `configure | list apps | publish | submission status | flight | rollout | CI/CD`117118### Commands119| Command | Result | Evidence |120| --- | --- | --- |121| `msstore <command>` | `<pass/fail/not run>` | `<output summary>` |122123### Store context124- Product ID: `<productId or unknown>`125- Flight ID: `<flightId or not applicable>`126- Credentials source: `environment | msstore config | not configured`127```128129## Quality gate130131- [ ] Required runtime, Partner Center account, and Azure AD application prerequisites were checked for the requested workflow.132- [ ] Credentials used `msstore reconfigure`, `winapp store reconfigure`, or `MSSTORE_TENANT_ID`, `MSSTORE_SELLER_ID`, `MSSTORE_CLIENT_ID`, and `MSSTORE_CLIENT_SECRET`.133- [ ] Secrets were not printed, committed, or included in output.134- [ ] Product ID and flight ID were verified before status, publish, flight, or rollout operations.135- [ ] Rollout percentages were validated as 0 through 100.136- [ ] `winapp store` was used only when a unified packaging and publishing CLI was useful.137138## References139140- [Microsoft Store Developer CLI Documentation](https://learn.microsoft.com/windows/apps/publish/msstore-dev-cli/overview)141- [CLI Commands Reference](https://learn.microsoft.com/windows/apps/publish/msstore-dev-cli/commands)142- [GitHub Repository](https://github.com/microsoft/msstore-cli)143- [Partner Center API](https://learn.microsoft.com/windows/uwp/monetize/using-windows-store-services)144- [App Submission API](https://learn.microsoft.com/windows/uwp/monetize/create-and-manage-submissions-using-windows-store-services)145- [Package Flights Overview](https://learn.microsoft.com/windows/uwp/publish/package-flights)146- [Gradual Package Rollout](https://learn.microsoft.com/windows/uwp/publish/gradual-package-rollout)147- [Partner Center](https://learn.microsoft.com/en-us/partner-center/)148- [Microsoft Store package](https://www.microsoft.com/store/apps/9P53PC5S0PHJ)149- [Manual releases](https://aka.ms/msstoredevcli/releases)
Run npx skillmds@latest add paulasilvatech/msstore-cli-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Use Microsoft Store Developer CLI (msstore) to configure Partner Center credentials, list Store apps, package and publish Windows submissions, check status, manage package flights, gradual rollouts, and CI/CD publishing for Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA apps. Use when asked to configure Store credentials, publish to Microsoft Store, check submission status, or automate Store releases. It is listed under Web & Frontend on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.
paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.
paulasilvatech