How do I easily automate the publishing of a Microsoft Store app using Azure Devops pipelines?

sysadmin 40 Reputation points
2025-10-13T22:46:09.5533333+00:00

I have an app which I can manually deploy the store easily by using the Visual Studio "create app package" feature and I have this automatically deploying to the store.

Now, how can I make an Azure Devops pipeline do these exact same steps without requiring user interaction?

User's image

Windows development | Windows API - Win32
0 comments No comments
{count} votes

Answer accepted by question author
  1. Tom Tran (WICLOUD CORPORATION) 1,920 Reputation points Microsoft External Staff
    2025-10-14T04:23:17.01+00:00

    Hi @Sysadmin,

    Thanks for the details!

    How do I easily automate the publishing of a Microsoft Store app using Azure Devops pipelines?

    From what I can gather, Visual Studio simplifies packaging and publishing, but Azure DevOps can automate the same steps with the right tools and APIs. The process involves three main stages:


    1. Package Your App for Store Submission

    Visual Studio generates a .msixbundle or .msixupload for the Store. In Azure DevOps, configure your pipeline to build and package the app using MSBuild or the MSIX Packaging Extension:

    • Build the solution.
    • Generate the MSIX/AppX package for Store upload.

    Reference:


    2. Submit to Microsoft Store Automatically

    Visual Studio handles submission behind the scenes, but in a pipeline you use the Microsoft Store submission API via Partner Center or the Windows Store Publish extension to submit your package automatically. This requires:

    • Registering an Azure AD app for authentication.
    • Using the API to upload your .msixupload file and commit the submission.

    3. Optional: Certification Tests

    Visual Studio runs the Windows App Certification Kit before submission. You can add this step in your pipeline using its command-line interface.

    Reference: Run WACK tests from the command line


    In short: MSIX Packaging Extension creates the signed package → WACK validates the package for Store compliance → Submission API or Publish Extension uploads and commits the package to the Microsoft Store. These steps form a sequential pipeline: build → certify → publish. Once configured, the process runs end-to-end without manual interaction.


    I hope this answers your question!


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.