Merge pull request #5693 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-15 05:00 UTC

Author: learn-build-service-prod[bot]

hub/apps/publish/index.md

@@ -64,7 +64,8 @@ For more details, refer [steps to create company developer account](/windows/app
 
 For packaging your Win32 app as MSIX, follow these [steps](https://aka.ms/packagewin32asmsix).
 
-**Note:** If you distribute your application as a web download (EXE /MSI) and you are planning to distribute it as a packaged application (MSIX) in the Store, you might want to prevent users from installing both versions or migrate users from the unpackaged web version to the Store version. Learn more about [transitioning users from web unpackaged to Store packaged app](../distribute-through-store/how-to-transition-users-from-your-web-unpackaged-app-to-store-packaged-app.md).
+> [!NOTE]
+> If you distribute your application as a web download (EXE /MSI) and you are planning to distribute it as a packaged application (MSIX) in the Store, you might want to prevent users from installing both versions or migrate users from the unpackaged web version to the Store version. Learn more about [transitioning users from web unpackaged to Store packaged app](../distribute-through-store/how-to-transition-users-from-your-web-unpackaged-app-to-store-packaged-app.md).
 
 ## Choice of commerce platform
 

hub/apps/publish/publish-your-app/msi/publish-update-to-your-app-on-store.md

@@ -18,11 +18,9 @@ You can make changes to a published app at any time. To submit updates, go to th
 
 Go to the required sections like [Pricing and availability](./price-and-availability.md), [Properties](./enter-app-properties.md), [Age ratings](./age-ratings.md), [Packages](./upload-app-packages.md) and [Store listing](./create-app-store-listing.md) to make the changes you'd like and save them. Then click  **Publish** on Manage Store listing page.
 
-> [!NOTE]
->
-> ## Update package details
->
-> After updating/adding the new package details, click on Save draft. You will be back on Manage Packages page. In the list of packages, you will see your existing package or the new package has been added. Now, click on **Save All**. You will see a message that your package is uploading and after a successful upload, you will get a message as Saved Successfully.
 
+## Update package details
+
+After updating/adding the new package details, click on Save draft. You will be back on Manage Packages page. In the list of packages, you will see your existing package or the new package has been added. Now, click on **Save All**. You will see a message that your package is uploading and after a successful upload, you will get a message as Saved Successfully.
 > [!NOTE]
 > Any updates to EXE or MSI apps are subject to [Application Developer Agreement](/legal/windows/agreements/app-developer-agreement) and the [Microsoft Store Policies](../../store-policies.md), which may be updated from time to time. To add new functionalities that require written customer consent via your app update, you must provide notice to customers and get their written consent as required by law in the markets where you choose to distribute your app.

hub/apps/publish/publish-your-app/msi/reserve-your-apps-name.md

@@ -46,3 +46,12 @@ Choosing the right name for your app is important. Pick a name that will capture
 If this is unavoidable, use different logos and app images to make it easier to differentiate one app from another.
 
 **Do not include emojis in your name**. You will not be able to reserve a name that includes emojis or other unsupported characters.
+
+## Next steps for MSI/EXE app development
+
+After reserving your app name, you may want to explore technical implementation topics for your MSI or EXE application:
+
+- **UI controls and accessibility**: Learn about implementing docking controls, drag and drop, and other UI patterns. See [Control patterns and interfaces](../../../design/accessibility/control-patterns-and-interfaces.md) for UI Automation patterns including docking functionality.
+- **App updates**: Plan how your application will handle updates after publication. See [Publish update to your MSI/EXE app on the Store](./publish-update-to-your-app-on-store.md) for Store update guidance.
+- **Desktop app development**: Find comprehensive guidance for building Windows desktop applications at [Build desktop apps for Windows](../../../desktop/index.yml).
+- **Continue with app submission**: Once your name is reserved, proceed to [Create your MSI/EXE app submission](./create-app-submission.md) to begin the publishing process.

hub/apps/publish/publish-your-app/msix/create-app-submission.md

@@ -38,7 +38,7 @@ Items that you are required to provide or specify are noted below. Some areas ar
 | **Category**                 | **Required** |
 | **Subcategory**              | Not required |
 | **Secondary category**       | Not required |
-| **Privacy policy URL**       | **Required** if your app collects/trasmits personal information |  
+| **Privacy policy URL**       | **Required** if your app collects/transmits personal information |  
 | **Website**                  | Not required |
 | **Support contact info**     | **Required** if your product is available on Xbox. |
 | **Contact details**          | **Required** for business/company accounts |
@@ -62,6 +62,9 @@ Items that you are required to provide or specify are noted below. Some areas ar
 | **Gradual package rollout**    | Not required |                                |
 | **Mandatory update**           | Not required |                                |
 
+> [!NOTE]
+> The Packages section will show as "Incomplete" until all required fields are completed, even if individual packages show "Validated" status. Package validation confirms that uploaded files are valid, but section completion requires that all mandatory package-related configurations are set. For detailed guidance on package upload and validation, see [Upload app packages](./upload-app-packages.md).
+
 ### Store listings
 
 You'll need all the required info for at least one of the languages that your app supports. We recommend providing [Store listings](./create-app-store-listing.md) in all of the languages your app supports, and you can also provide Store listings in additional languages. To make it easier to manage multiple listings for the same product, you can import and export Store listings.
@@ -112,7 +115,6 @@ To add or remove:
 3. On the Notification audience overview page, add or remove audience
 
 > [!NOTE]
->
 > - The owner of your developer account is always notified and can’t be removed from the audience list.
 > - The audience list is product specific and applied to all submissions of the product. To modify the notification recipients for a different product, follow the steps above for each product.
 > - Add-on inherits parent product’s audience list and can’t be managed separately.

hub/apps/publish/publish-your-app/msix/import-and-export-store-listings.md

@@ -1,12 +1,12 @@
 ---
 description: Import and export store listings for your MSIX app so you can reuse them later
-title: Import and export store listings for MSIX app
+title: Import and export store listings for your MSIX app
 ms.date: 10/30/2022
 ms.topic: article
 ms.localizationpriority: medium
 ---
 
-# Import and export store listings for MSIX app
+# Import and export store listings for your MSIX app
 
 Instead of [entering info for your Store listings directly in Partner Center](./create-app-store-listing.md), you have the option to add or update info by exporting your listings in a .csv file, entering your info and assets, and then importing the updated file. You can use this method to create listings from scratch, or to update listings you’ve already created.
 

hub/apps/publish/publish-your-app/pwa/create-app-submission.md

@@ -112,7 +112,6 @@ To add or remove:
 3. On the Notification audience overview page, add or remove audience
 
 > [!NOTE]
->
 > - The owner of your developer account is always notified and can’t be removed from the audience list.
 > - The audience list is product specific and applied to all submissions of the product. To modify the notification recipients for a different product, follow the steps above for each product.
 > - Add-on inherits parent product’s audience list and can’t be managed separately.

hub/apps/publish/store-business-verification-reqs.md

@@ -86,7 +86,7 @@ Then, expand and edit the **Contact Info** section. Select **Update**.
 
 ![DUNS ID input location in Partner Center](images\account-verify-duns.png)
 
-* **Upload document:** You can choose this option if you don’t have a DUNS ID. Select type of the document you will upload from the list provided, then unload the file. upload the file. Note that approval may take significantly longer as the document must go through a review process. 
+* **Upload document:** You can choose this option if you don’t have a DUNS ID. Select type of the document you will upload from the list provided, then upload the file. Note that approval may take significantly longer as the document must go through a review process. 
 
 ![Upload Document location in Partner Center](images\account-verify-upload.png)
 
@@ -117,7 +117,7 @@ Submitted information should be checked for accuracy. Keep the following tips in
 * Some users experience the **Save** button being greyed out. This usually indicates a formatting error with the provided information.  Possible reasons include:
 	- Submitted zip codes must include spaces when necessary.
 	- Submitted Website URLs are required to start with `https://`.
-	- The primary contact (aka seller contact email provided should not be a generic email or a group aliass. An OTP (one time password) will be sent to verify the email is valid. We do not allow plus addressing ([email protected]) 
+	- The primary contact (aka seller contact email provided should not be a generic email or a group alias. An OTP (one time password) will be sent to verify the email is valid. We do not allow plus addressing ([email protected]) 
 	- If a primary contact email is updated, make sure to verify the email with OTP using ‘Verify email’ button. 
 	- If a new address is provided for customer contact information, it will likely need to be validated. Validate by clicking on the **Validate address** button that appears. If the button is not present, no action is required.  
 
@@ -162,7 +162,7 @@ Publishers rejected for any reason can learn the reason for rejection and the st
 
 If vetting is rejected, utilize the **Fix now** button in Partner Center to provide additional information. 
 
-![Fix rejeciton location in Partner Center](images\account-verify-fix-rejection.png)
+![Fix rejection location in Partner Center](images\account-verify-fix-rejection.png)
 
 There are different types of verifications: 
 

hub/apps/publish/store-policies.md

@@ -20,7 +20,7 @@ ms.assetid: F02A720E-2899-4863-8945-9AB99158BCA1
 > Some older versions of this agreement, along with summary of recent changes are available at [Change history for Microsoft Store Policies](store-policies-change-history.md).
 
 
-Thank you for your interest in developing products for the Microsoft Store<sup>1</sup>. "Product" means content in whatever form submitted including, but not limited to, apps, games, titles, add-ons, in-product consumables, subscriptions and any additional content soldor offered in any of our storefronts or within a Product. We’re committed to a diverse catalog of products for customers worldwide. Products on the Store must meet our certification standards, offer customers a truly useful and engaging experience, and provide a good fit for the Store.
+Thank you for your interest in developing products for the Microsoft Store<sup>1</sup>. "Product" means content in whatever form submitted including, but not limited to, apps, games, titles, add-ons, in-product consumables, subscriptions and any additional content sold or offered in any of our storefronts or within a Product. We’re committed to a diverse catalog of products for customers worldwide. Products on the Store must meet our certification standards, offer customers a truly useful and engaging experience, and provide a good fit for the Store.
 
 A few principles to get you started:
 

hub/apps/publish/store-policy-archive/store-policy-7-15.md

@@ -344,7 +344,6 @@ For products that are primarily gaming experiences or target Xbox consoles, the
 
 > [!NOTE]
 > Additional requirements for titles which use Xbox Live on PC/Mobile and/or the Creators program on Xbox consoles are available at https://aka.ms/xboxlivepolicy.
->
 > **February 10, 2022 Policy Note**: For game products targeting console developed through the Xbox Live Creators program, the requirement to integrate with XBL Services no longer applies. The specific policy (Policy 10.13.1) will be updated to reflect this change the next time the Store Policy document is updated, but effective as of this notice, the policy will no longer be enforced for the XBL Creators Program.
 
 **10.13.1**

hub/apps/windows-dotnet-maui/tutorial-graph-api.md

@@ -16,7 +16,7 @@ In this tutorial, you learn how to:
 > [!div class="checklist"]
 > * Set up your environment for .NET MAUI development and create a .NET MAUI project
 > * Register your client app in Azure
-> * Integrate with [Azure Identity](/graph/azuread-identity-access-management-concept-overview) and the Microsoft Graph SDK
+> * Integrate with [Azure Identity](/graph/identity-network-access-overview) and the Microsoft Graph SDK
 > * Update the user interface to display user information from [Microsoft Graph](/graph/)
 
 ## Prerequisites