Merge pull request #5726 from MicrosoftDocs/IpsitaChoudhary-Update

GrantMeStrength · web-flow · commit 954b88ebc307 · 2025-08-25T11:02:20.000-07:00
Adding FAQ links in documentation
diff --git a/hub/apps/publish/analyze-app-performance/msi-exe.md b/hub/apps/publish/analyze-app-performance/msi-exe.md
@@ -24,3 +24,6 @@ In this section you'll find details about the info presented in each of the foll
 | [Usage report](../../../apps/publish/analyze-msi-exe/analyze-app-performance.md#usage-report)          | Shows details about how your customers are using your app over the selected period of time. |
 | [Health report](../../../apps/publish/analyze-msi-exe/analyze-app-performance.md#health-report)        | Shows data related to the performance and quality of your app, including crashes and unresponsive events. |
 | [Ratings & Reviews report](../../../apps/publish/analyze-msi-exe/ratings-reviews-performance.md)       | See the rating and reviews your customers have left for your app and provide responses to let customers know you’re listening to their feedback. |
+
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../faq/monitor-your-app-performance.md) section.
diff --git a/hub/apps/publish/analyze-app-performance/msix.md b/hub/apps/publish/analyze-app-performance/msix.md
@@ -3,7 +3,7 @@ description: Viewing analytics for your MSIX apps and games in Partner Center.
 title: Analyze performance for MSIX apps and games
 ms.date: 05/16/2024
 ms.topic: article
-keywords: windows 10, windows 11, windows, windows store, store, msix, uwp, pwa, unpackaged app, desktop app, traditional desktop app
+keywords: windows 10, windows 11, windows, windows store, store, msix, uwp, pwa, unpackaged app, desktop app, traditional desktop app, analytics, insights, Windows app analytics
 ms.localizationpriority: medium
 ---
 
@@ -36,3 +36,5 @@ In this section you'll find details about the info presented in each of the foll
 | [Reviews report](/partner-center/reviews-report)       | See the rating and reviews your customers have left for your app and provide responses to let customers know you’re listening to their feedback. |
 | [Insights report](/partner-center/insights-report)       | See meaningful insights about your app like significant changes(increases or decreases that we detected over the last 30 days in your acquisitions and health data. |
 
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../faq/monitor-your-app-performance.md) section.
diff --git a/hub/apps/publish/index.md b/hub/apps/publish/index.md
@@ -188,13 +188,14 @@ To understand how to use the Store web installer to distribute your app on web,
 
 >[!VIDEO https://learn-video.azurefd.net/vod/player?id=3fc3492e-c0b9-4760-a25b-7a424f69e8f3]
 
-For more information, please visit [Leverage Developer Tools](../publish/msstore-dev-cli/overview.md) section.
+For more information, please visit [Leverage Developer Tools](../publish/product-page-experiments.md) section.
 
 ## Appendix [MSIX/PWA]
 
 ### Useful links
 
 - [Microsoft Store Developer CLI documentation](../publish/msstore-dev-cli/overview.md)
+- [Frequently Asked Questions](../publish/faq/get-started-with-the-microsoft-store.md)
 - [Store Policies and Code of Conduct](../publish/store-policies-and-code-of-conduct.md)
 
 ### Troubleshooting
@@ -321,13 +322,13 @@ To understand how to use the Store web installer, check out the following video:
 
 >[!VIDEO https://learn-video.azurefd.net/vod/player?id=3fc3492e-c0b9-4760-a25b-7a424f69e8f3]
 
-For more information, please visit [Leverage Developer Tools](../publish/msstore-dev-cli/overview.md) section.
+For more information, please visit [Leverage Developer Tools](../../apps/distribute-through-store/how-to-use-store-web-installer-for-distribution.md) section.
 
 ## Appendix [MSI/EXE]
 
 ### Useful links
 
-- [Microsoft Store Developer CLI documentation](../publish/msstore-dev-cli/overview.md)
+- [Frequently Asked Questions](../publish/faq/get-started-with-the-microsoft-store.md)
 - [Store Policies and Code of Conduct](../publish/store-policies-and-code-of-conduct.md)
 
 ### Full app submission documentation
diff --git a/hub/apps/publish/msstore-dev-cli/overview.md b/hub/apps/publish/msstore-dev-cli/overview.md
@@ -10,6 +10,10 @@ ms.localizationpriority: medium
 
 The Microsoft Store Command Line Interface is a cross-platform (Windows, macOS, Linux) CLI that helps developers publish their applications to the Microsoft Store. It allows developers to locally configure their applications projects to publish to the Microsoft Store, as well as actually publish their applications' packages to the Microsoft Store, automatically calling the right [Partner Center APIs](/partner-center/develop/partner-center-rest-api-reference) to upload its packages.
 
+To understand how to use the Store Developer CLI, check out the following video:
+
+[!VIDEO https://learn-video.azurefd.net/vod/player?id=cbc4aad9-e79b-4ff6-a30b-c2399c2624a3]
+
 ## Prerequisites
 
 To use the Microsoft Store Developer CLI, you'll need to:
diff --git a/hub/apps/publish/partner-center/associate-existing-azure-ad-tenant-with-partner-center-account.md b/hub/apps/publish/partner-center/associate-existing-azure-ad-tenant-with-partner-center-account.md
@@ -45,4 +45,8 @@ To add and manage Partner Center account users in your tenant, sign in to Partne
 > [!NOTE]
 > Any user who has the **Manager** role for a Partner Center account can associate Microsoft Entra ID tenants with the account.
 
+
+> [!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../faq/manage-your-account.md) section
+
 You can associate multiple Microsoft Entra ID tenants to a single Partner Center account. To associate a new tenant, select **Associate another Microsoft Entra ID tenant**, then follow the steps indicated above. Note that you will be prompted for your credentials in the Microsoft Entra ID tenant that you want to associate.
diff --git a/hub/apps/publish/partner-center/manage-account-users.md b/hub/apps/publish/partner-center/manage-account-users.md
@@ -17,5 +17,8 @@ This section describes how to do the following:
 - [Add users, groups, and Microsoft Entra ID applications to your Partner Center account](add-users-groups-and-azure-ad-applications.md)
 - [Set roles and custom permissions for account users](set-custom-permissions-for-account-users.md)
 
+> [!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../faq/manage-your-account.md) section.
+
 > [!TIP]
 > These topics are specific to the Windows apps developer program in Partner Center, but associating a tenant and managing users works similarly for accounts in the Windows Hardware Developer Program (see [Dashboard Administration](/windows-hardware/drivers/dashboard/get-started-with-the-hardware-dashboard) for more info) or in the Windows Desktop Application Program (see [Windows Desktop Application Program](/windows/desktop/appxpkg/windows-desktop-application-program#add-and-manage-account-users) for more info).
diff --git a/hub/apps/publish/publish-your-app/add-on/publish-update-to-your-app-on-store.md b/hub/apps/publish/publish-your-app/add-on/publish-update-to-your-app-on-store.md
@@ -12,4 +12,7 @@ You can make changes to a published add-on at any time. Add-on changes are submi
 
 To submit updates, go to the add-on's page in Partner Center and click **Update**. This will create a new submission for the add-on, using the info from your previous submission as a starting point. Make the changes you'd like, and then click **Submit to the Store**.
 
-If you'd like to remove an add-on you've previously offered, you can do this by creating a new submission and changing the [Distribution and visibility](./price-and-availability.md) option to **Hidden in the Store** with the **Stop acquisition** option. Be sure to update your app's code as needed to remove references to the add-on.
+If you'd like to remove an add-on you've previously offered, you can do this by creating a new submission and changing the [Distribution and visibility](./price-and-availability.md) option to **Hidden in the Store** with the **Stop acquisition** option. Be sure to update your app's code as needed to remove references to the add-on.
+
+> [!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/manage-and-update-your-app.md) section.
diff --git a/hub/apps/publish/publish-your-app/msi/add-and-edit-store-listing-info.md b/hub/apps/publish/publish-your-app/msi/add-and-edit-store-listing-info.md
@@ -53,7 +53,7 @@ If you need to rename the app after it's already been published, you can select
 
 _Required_<br>_Character limit: 10,000 characters_
 
-The description field tells customers what your app does. See [Writing a great app description](/hub/apps/publish/faq/submit-your-app.md#write-a-great-app-description) for more information.
+The description field tells customers what your app does. See [Writing a great app description](../../../publish/faq/submit-your-app.md) for more information.
 
 ### What's new in this version
 
@@ -107,4 +107,4 @@ Specify any additional system requirements not listed on the [App properties pag
 This field is especially important if your app requires hardware that might not be available on every computer. For instance, if your app requires a 3D printer or a wearable device, enter those requirements here. The info you enter will be shown to customers viewing your app's Store listing, along with the requirements you indicated on the product's properties page.
 
 > [!NOTE]
-> The store automatically displays each feature in a bulleted list. Do not add bullets manually.
+> The store automatically displays each feature in a bulleted list. Do not add bullets manually.
diff --git a/hub/apps/publish/publish-your-app/msi/app-certification-process.md b/hub/apps/publish/publish-your-app/msi/app-certification-process.md
@@ -79,7 +79,7 @@ Review this list to help avoid issues that frequently prevent apps from getting
 - Provide any necessary info required to use your app, such as the username and password for a test account if your app requires users to log in to a service, or any steps required to access hidden or locked features.
 - Configure your app's installer to provide your app’s information such as ProductName, Publisher Name, Default Language, Version info (as applicable) in places where customers expect to find such information such as ‘Add/Remove Programs’ in Windows. This information is part of your app’s installer package. See [setting installer properties](/windows/win32/msi/property-reference#product-information-properties) for more details on how to set properties for your Windows installer
 - Include a privacy policy URL if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
-- Make sure that your app's description clearly represents what it does. For help, see our guidance on [writing a great app description](/hub/apps/publish/faq/submit-your-app.md#write-a-great-app-description).
+- Make sure that your app's description clearly represents what it does. For help, see our guidance on [writing a great app description](../../faq/submit-your-app.md)
 - Do not declare your app as accessible unless you have specifically engineered and tested it for accessibility scenarios.
 - Review the [Microsoft Store Policies](../../store-policies.md) to ensure your app meets all the requirements listed there.
 
@@ -97,3 +97,7 @@ When the certification process is complete, if it did not pass, you'll receive a
 Your app will be published after it is certified. When this phase has begun, you can no longer cancel your submission.
 
 We also conduct spot checks of apps after they've been published so we can identify potential problems and ensure that your app complies with all the [Microsoft Store Policies](../../store-policies.md). If we find any problems, you'll be notified about the issue and how to fix it, if applicable, or if it has been removed from the Microsoft Store.
+
+
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/get-your-app-certified.md) section.
diff --git a/hub/apps/publish/publish-your-app/msi/create-app-submission.md b/hub/apps/publish/publish-your-app/msi/create-app-submission.md
@@ -122,10 +122,13 @@ Each language has a separate store listing page. One listing page is required. I
 | **Applicable license terms**       | **Required** | Character limit: 10,000                                                                                               |
 | **Developed by**                   | Not required | Character limit: 255                                                                                                  |
 
+> [!TIP]
+> For detailed information about the **Store listings** fields, see the [Store listings](./add-and-edit-store-listing-info.md) section.
+
 Once you have completed all the sections, you can submit your app for certification by clicking on **Publish** button on the Store listing page or by clicking **Submit** button on the Application overview page.
 
 > [!NOTE]
 > You must have an active [developer account](https://developer.microsoft.com/store/register) in [Partner Center](https://partner.microsoft.com/dashboard) in order to submit apps to the Microsoft Store. All the users added to your developer account in Partner Center can submit EXE or MSI apps to the Microsoft Store. They can also modify all the existing EXE or MSI apps in Partner Center. The roles and permissions set for account users do not currently apply to EXE or MSI apps.
 
 > [!TIP]
-> For detailed information about the **Store listings** fields, see the [Store listings](./add-and-edit-store-listing-info.md) section.
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/submit-your-app.md) section.
diff --git a/hub/apps/publish/publish-your-app/msi/publish-update-to-your-app-on-store.md b/hub/apps/publish/publish-your-app/msi/publish-update-to-your-app-on-store.md
@@ -22,5 +22,9 @@ Go to the required sections like [Pricing and availability](./price-and-availabi
 ## 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.
+
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/manage-and-update-your-app.md) section.
+
 > [!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.
+> 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.
diff --git a/hub/apps/publish/publish-your-app/msix/add-and-edit-store-listing-info.md b/hub/apps/publish/publish-your-app/msix/add-and-edit-store-listing-info.md
@@ -57,7 +57,7 @@ If you haven't uploaded packages for the language you're working on, and you've
 
 The description field is where you can tell customers what your app does. This field is required, and will accept up to 10,000 characters of plain text.
 
-For some tips on making your description stand out, see [Write a great app description](/hub/apps/publish/faq/submit-your-app.md#write-a-great-app-description).
+For some tips on making your description stand out, see [Write a great app description](../../../publish/faq/submit-your-app.md).
 
 ### What's new in this version
 
@@ -128,4 +128,4 @@ If needed, you can describe the hardware configurations that your app requires t
 You can enter up to 11 items for both **Minimum hardware** and **Recommended hardware**. These are displayed to the customer as a bulleted list in your Store listing. Keep these brief, with just a few words (and no more than 200 characters) per item.
 
 > [!NOTE]
-> Your additional system requirements will appear bulleted in your Store listing, so don't add your own bullets.
+> Your additional system requirements will appear bulleted in your Store listing, so don't add your own bullets.
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
@@ -43,5 +43,8 @@ The publishing process take a few minutes and on an average, customers will be a
 
 After successfully going through the steps above, the submission's status will change from **Publishing** to **In the Store**. Your submission will then be available in the Microsoft Store for customers to download (unless you have chosen another [Discoverability](./visibility-options.md#discoverability) option).
 
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/get-your-app-certified.md) section.
+
 > [!NOTE]
 > We also conduct spot checks of apps after they've been published so we can identify potential problems and ensure that your app complies with all of the [Microsoft Store Policies](../../store-policies.md). If we find any problems, you'll be notified about the issue and how to fix it, if applicable, or if it has been removed from the Store.
diff --git a/hub/apps/publish/publish-your-app/msix/create-app-submission.md b/hub/apps/publish/publish-your-app/msix/create-app-submission.md
@@ -113,5 +113,8 @@ You'll need all the required info for at least one of the languages that your ap
 
 Once you have completed all the sections, you can submit your app for certification by clicking **Submit for certification** button on the Application overview page.
 
+> [!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/submit-your-app.md) section.
+
 > [!NOTE]
 > You must have an active [developer account](https://developer.microsoft.com/store/register) in [Partner Center](https://partner.microsoft.com/dashboard) in order to submit apps to the Microsoft Store. All the users added to your developer account in Partner Center can submit EXE or MSI apps to the Microsoft Store. They can also modify all the existing EXE or MSI apps in Partner Center. The roles and permissions set for account users do not currently apply to EXE or MSI apps.
diff --git a/hub/apps/publish/publish-your-app/msix/publish-update-to-your-app-on-store.md b/hub/apps/publish/publish-your-app/msix/publish-update-to-your-app-on-store.md
@@ -16,5 +16,8 @@ Go to the required sections like [Pricing and availability](./price-and-availabi
 
 :::image type="content" source="images/msix-submit-app-update.png" lightbox="images/msix-submit-app-update.png" alt-text="A screenshot showing the overview of Properties section showing support info.":::
 
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/manage-and-update-your-app.md) section.
+
 > [!NOTE]
-> To understand how the Store distributes an update, visit [Download and install package updates from the Store](/windows/uwp/packaging/self-install-package-updates#mandatory-package-updates).
+> To understand how the Store distributes an update, visit [Download and install package updates from the Store](/windows/uwp/packaging/self-install-package-updates#mandatory-package-updates).
diff --git a/hub/apps/publish/publish-your-app/pwa/app-certification-process.md b/hub/apps/publish/publish-your-app/pwa/app-certification-process.md
@@ -43,5 +43,8 @@ The publishing process take a few minutes and on an average, customers will be a
 
 After successfully going through the steps above, the submission's status will change from **Publishing** to **In the Store**. Your submission will then be available in the Microsoft Store for customers to download (unless you have chosen another [Discoverability](./visibility-options.md#discoverability) option).
 
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/get-your-app-certified.md) section.
+
 > [!NOTE]
 > We also conduct spot checks of apps after they've been published so we can identify potential problems and ensure that your app complies with all of the [Microsoft Store Policies](../../store-policies.md). If we find any problems, you'll be notified about the issue and how to fix it, if applicable, or if it has been removed from the Store.
diff --git a/hub/apps/publish/publish-your-app/pwa/create-app-submission.md b/hub/apps/publish/publish-your-app/pwa/create-app-submission.md
@@ -97,5 +97,8 @@ You'll need all the required info for at least one of the languages that your ap
 
 Once you have completed all the sections, you can submit your app for certification by clicking **Submit for certification** button on the Application overview page.
 
+>[!TIP]
+> To refer to common questions, please refer to [Frequently Asked Questions](../../faq/submit-your-app.md) section.
+
 > [!NOTE]
 > You must have an active [developer account](https://developer.microsoft.com/store/register) in [Partner Center](https://partner.microsoft.com/dashboard) in order to submit apps to the Microsoft Store. All the users added to your developer account in Partner Center can submit EXE or MSI apps to the Microsoft Store. They can also modify all the existing EXE or MSI apps in Partner Center. The roles and permissions set for account users do not currently apply to EXE or MSI apps.
diff --git a/hub/apps/publish/publish-your-app/pwa/publish-update-to-your-app-on-store.md b/hub/apps/publish/publish-your-app/pwa/publish-update-to-your-app-on-store.md
diff --git a/hub/apps/publish/toc.yml b/hub/apps/publish/toc.yml
