Skip to content

Commit 4ec3dd4

Browse files
Fix build suggestions: convert absolute learn.microsoft.com links to relative (Group D)
Co-authored-by: Copilot <[email protected]>
1 parent 111b3bc commit 4ec3dd4

5 files changed

Lines changed: 12 additions & 12 deletions

File tree

hub/apps/publish/analyze-app-performance/msi-exe.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@ ms.localizationpriority: medium
99

1010
# Analyze performance for MSI or EXE apps
1111

12-
In Partner Center, you have access to detailed analytics for your MSI or EXE applications that are published through the Microsoft Store. Use statistics and charts to monitor how these Microsoft Store–published apps are performing, including insights into customer reach, app health, usage, and customer feedback. You can view analytic reports directly in Partner Center, or [download the reports](https://learn.microsoft.com/partner-center/insights/download-analytic-reports) you need to analyze your data offline.
12+
In Partner Center, you have access to detailed analytics for your MSI or EXE applications that are published through the Microsoft Store. Use statistics and charts to monitor how these Microsoft Store–published apps are performing, including insights into customer reach, app health, usage, and customer feedback. You can view analytic reports directly in Partner Center, or [download the reports](/partner-center/insights/download-analytic-reports) you need to analyze your data offline.
1313

1414
To access analytics for MSI or EXE apps:
1515
1. Go to [Apps & games](https://partner.microsoft.com/dashboard/apps-and-games/overview) in Partner Center.
1616
3. Choose the MSI or EXE app you want to analyze.
1717
4. Select View Analytics to view the reports.
1818

1919
>[!Note]
20-
> This page applies only to MSI/EXE apps that are published via the Microsoft Store. For information on MSIX apps, check out [Analyze performance for MSIX apps and games.](https://learn.microsoft.com/windows/apps/publish/analyze-app-performance/msix)
20+
> This page applies only to MSI/EXE apps that are published via the Microsoft Store. For information on MSIX apps, check out [Analyze performance for MSIX apps and games.](/windows/apps/publish/analyze-app-performance/msix)
2121
2222
### View key analytics for all your apps
2323

hub/apps/publish/analyze-app-performance/msix.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,10 @@ ms.localizationpriority: medium
99

1010
# Analyze performance for MSIX apps and games
1111

12-
Use Partner Center analytics to understand how your MSIX-packaged apps and games published through the Microsoft Store are performing. Partner Center provides reports that show how many customers you are reaching, how they discover and acquire your Microsoft Store listing, how they use your app, and how reliably it runs on their devices. You can [view these reports](https://partner.microsoft.com/dashboard/insights/analytics/reports/summary) in Partner Center, or [export the data for analysis](https://learn.microsoft.com/partner-center/insights/download-analytic-reports) in your own tools.
12+
Use Partner Center analytics to understand how your MSIX-packaged apps and games published through the Microsoft Store are performing. Partner Center provides reports that show how many customers you are reaching, how they discover and acquire your Microsoft Store listing, how they use your app, and how reliably it runs on their devices. You can [view these reports](https://partner.microsoft.com/dashboard/insights/analytics/reports/summary) in Partner Center, or [export the data for analysis](/partner-center/insights/download-analytic-reports) in your own tools.
1313

1414
>[!Note]
15-
> This page applies only to MSIX apps that are published via the Microsoft Store. For information on MSI/EXE apps, check out [Analyze performance for MSI or EXE apps.](https://learn.microsoft.com/windows/apps/publish/analyze-app-performance/msi-exe)
15+
> This page applies only to MSIX apps that are published via the Microsoft Store. For information on MSI/EXE apps, check out [Analyze performance for MSI or EXE apps.](/windows/apps/publish/analyze-app-performance/msi-exe)
1616
1717
</br>
1818
You can watch the following video to understand how to use Analytic APIs.

hub/apps/publish/faq/submit-your-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ Search terms are not shown to users but play a crucial role in helping your app
160160
<details>
161161
<summary><strong>How can I manage who receives submission notifications in Partner Center?</strong></summary>
162162

163-
After publishing an app, the **owner** of your developer account is always notified about the publishing status and required actions via email and through the [Action Center](https://learn.microsoft.com/partner-center/action-center-overview) in Partner Center.
163+
After publishing an app, the **owner** of your developer account is always notified about the publishing status and required actions via email and through the [Action Center](/partner-center/action-center-overview) in Partner Center.
164164

165165
To ensure delivery of these critical notifications, the owner must verify their email address via [My Preferences](https://partner.microsoft.com/dashboard/actioncenter/mypreferences) in Action Center.
166166

hub/apps/publish/msstore-dev-cli/github-actions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,8 @@ To understand how to set up pre-requisites for the app update process, check out
1919
## Pre-requisite
2020

2121
1. Register as a Windows app developer in [Partner Center](https://storedeveloper.microsoft.com/).
22-
2. Have a tenant associated with your Partner Center account. You can achieve that by either [associating an existing Microsoft Entra ID in Partner Center](https://learn.microsoft.com/windows/apps/publish/partner-center/associate-existing-azure-ad-tenant-with-partner-center-account) or by [creating a new Microsoft Entra ID in Partner Center](https://learn.microsoft.com/windows/apps/publish/partner-center/create-new-azure-ad-tenant).
23-
3. [Register](https://learn.microsoft.com/entra/identity-platform/quickstart-register-app) an application in Microsoft Entra ID
22+
2. Have a tenant associated with your Partner Center account. You can achieve that by either [associating an existing Microsoft Entra ID in Partner Center](/windows/apps/publish/partner-center/associate-existing-azure-ad-tenant-with-partner-center-account) or by [creating a new Microsoft Entra ID in Partner Center](/windows/apps/publish/partner-center/create-new-azure-ad-tenant).
23+
3. [Register](/entra/identity-platform/quickstart-register-app) an application in Microsoft Entra ID
2424
4. Next, from the Microsoft Entra applications tab under User management page in the Account settings section of Partner Center, add the Microsoft Entra ID application that represents the app or service that you will use to access submissions for your Partner Center account. Make sure you assign this application the Manager role.
2525
5. The app you want to update must already be published and live in Microsoft Store.
2626
6. Required IDs and Secrets:
@@ -173,7 +173,7 @@ The above workflows will do the following in the background:
173173
* Authenticate your Microsoft Store Partner Center account using the secrets you configured (Tenant ID, Client ID, Client Secret, Seller ID).
174174
* Use the Microsoft Store Developer CLI (msstore) to obtain base metadata and publish the updated package or metadata to the Microsoft Store.
175175

176-
For more information on commands, refer [Microsoft Store Developer CLI (MSIX)](https://learn.microsoft.com/windows/apps/publish/msstore-dev-cli/overview).
176+
For more information on commands, refer [Microsoft Store Developer CLI (MSIX)](/windows/apps/publish/msstore-dev-cli/overview).
177177

178178
## [MSI/EXE](#tab/msiexe)
179179

@@ -340,7 +340,7 @@ The above workflows will do the following in the background:
340340
* Authenticate your Microsoft Store Partner Center account using the secrets you configured (Tenant ID, Client ID, Client Secret, Seller ID).
341341
* Use the Microsoft Store Developer CLI (msstore) to obtain base package info and metadata and publish the updated package or metadata to the Microsoft Store.
342342

343-
For more information on commands, refer [Microsoft Store Developer CLI (MSI/EXE)](https://learn.microsoft.com/windows/apps/publish/msstore-dev-cli/overview-exe).
343+
For more information on commands, refer [Microsoft Store Developer CLI (MSI/EXE)](/windows/apps/publish/msstore-dev-cli/overview-exe).
344344

345345
---
346346

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -185,9 +185,9 @@ Contact [developer support](https://developer.microsoft.com/windows/support/?tab
185185

186186
## Verifiable Credentials (VC) Vetting Service
187187

188-
* For more information on Verifiable Credentials, [see the FAQ](https://learn.microsoft.com/partner-center/enroll/get-verifiable-credentials)
189-
* Verifiable Credentials support [can be found here](https://learn.microsoft.com/partner-center/support/report-problems-with-partner-center#contact-support-using-partner-center-ai-assistant)
190-
* [Submit a help ticket here](https://learn.microsoft.com/partner-center/support/report-problems-with-partner-center#contact-support-using-partner-center-ai-assistant)
188+
* For more information on Verifiable Credentials, [see the FAQ](/partner-center/enroll/get-verifiable-credentials)
189+
* Verifiable Credentials support [can be found here](/partner-center/support/report-problems-with-partner-center#contact-support-using-partner-center-ai-assistant)
190+
* [Submit a help ticket here](/partner-center/support/report-problems-with-partner-center#contact-support-using-partner-center-ai-assistant)
191191

192192

193193
## Additional resources

0 commit comments

Comments
 (0)