diff --git a/hub/apps/publish/faq/get-started-with-the-microsoft-store.md b/hub/apps/publish/faq/get-started-with-the-microsoft-store.md index 2e45027ac1..e60ef151e6 100644 --- a/hub/apps/publish/faq/get-started-with-the-microsoft-store.md +++ b/hub/apps/publish/faq/get-started-with-the-microsoft-store.md @@ -162,6 +162,25 @@ For general questions, you can also use Microsoft Q&A forums or check the Learn +--- + +
+Does the Microsoft Store provide code signing for my app? Do I need my own code signing certificate? + +Yes, the Microsoft Store provides **automatic code signing** for all apps submitted for Store distribution. You do not need to purchase or provide your own code signing certificate, .pfx file, .cer file, or use a USB token/hardware security module (HSM) to submit apps to the Microsoft Store. + +Here's how it works: + +- **For Store submissions:** When you submit your MSIX package to the Microsoft Store, the package does not need to be signed with a trusted certificate. After your app passes certification, the Microsoft Store automatically signs your package with a Microsoft certificate during the publishing process, replacing any existing signature. This ensures customers can trust and install your app without security warnings. + +- **What you need:** Only the package files (.msix, .msixupload, .msixbundle, .appx, .appxupload, or .appxbundle) are required for submission. No code signing certificate is needed. + +- **For non-Store distribution:** If you plan to distribute your MSIX package outside the Microsoft Store (for example, for enterprise deployment, sideloading, or direct downloads), you will need to sign the package yourself with a valid code signing certificate before distribution. For more information, see [Sign an app package using SignTool](/windows/win32/appxpkg/how-to-sign-a-package-using-signtool). + +This automatic signing is one of the key benefits of publishing through the Microsoft Store, as it eliminates the need to purchase and manage your own code signing infrastructure for Store distribution. + +
+
> [!TIP] diff --git a/hub/apps/publish/publish-your-app/msix/app-certification-process.md b/hub/apps/publish/publish-your-app/msix/app-certification-process.md index b4b48f15d5..a0f8ccaf53 100644 --- a/hub/apps/publish/publish-your-app/msix/app-certification-process.md +++ b/hub/apps/publish/publish-your-app/msix/app-certification-process.md @@ -35,9 +35,11 @@ When your app passes certification, it's ready to move to the **Publishing** pro ## Publishing -Your app's packages are digitally signed to protect them against tampering after they have been released. Once this phase has begun, you can no longer cancel your submission or change its release date. +Your app's packages are digitally signed by Microsoft to protect them against tampering after they have been released. The Microsoft Store automatically signs all packages with a Microsoft certificate, which ensures that customers can trust and install your app without security warnings. -The publishing process take a few minutes and on an average, customers will be able to see the app’s listing within 15 minutes depending on their location. +You don't need to provide your own code signing certificate for Store distribution—the Store handles this automatically. Once this phase has begun, you can no longer cancel your submission or change its release date. + +The publishing process takes a few minutes and on average, customers will be able to see the app’s listing within 15 minutes depending on their location. ## In the Store diff --git a/hub/apps/publish/publish-your-app/msix/app-package-requirements.md b/hub/apps/publish/publish-your-app/msix/app-package-requirements.md index 546b12ab95..e8898231a7 100644 --- a/hub/apps/publish/publish-your-app/msix/app-package-requirements.md +++ b/hub/apps/publish/publish-your-app/msix/app-package-requirements.md @@ -27,7 +27,17 @@ When you create your package in Visual Studio, make sure you are signed in with When you build your app's UWP packages, Visual Studio can create an .msix or appx file, or a .msixupload or .appxupload file. For UWP apps, we recommend that you always upload the .msixupload or .appxupload file in the [Packages](./upload-app-packages.md) page. For more info about packaging UWP apps for the Store, see [Package a UWP app with Visual Studio](/windows/msix/package/packaging-uwp-apps). -Your app's packages don't have to be signed with a certificate rooted in a trusted certificate authority. +### Code signing for Microsoft Store submissions + +Your app's packages don't have to be signed with a certificate rooted in a trusted certificate authority when submitting to the Microsoft Store. The Microsoft Store will automatically sign your packages with a Microsoft certificate during the publishing process after your app passes certification. This means: + +- You don't need to purchase a code signing certificate for Store distribution +- You don't need a .pfx or .cer file to submit packages to the Store +- USB tokens or hardware security modules (HSMs) are not required for Store submissions +- The Store handles all code signing automatically, providing trust and security to customers + +> [!NOTE] +> If you are distributing your MSIX package outside the Microsoft Store (for example, for enterprise deployment or sideloading), you will need to sign the package yourself with your own code signing certificate. For more information, see [Sign an app package using SignTool](/windows/win32/appxpkg/how-to-sign-a-package-using-signtool). #### App bundles