Skip to content

Commit eaf6ee3

Browse files
committed
Squashed commit of the following:
commit 8dc0d7d0ff1f69ebd387c9f8ecb72842da6bd7ca Author: alejogaletto <[email protected]> Date: Mon Jun 23 19:02:48 2025 +0200 Removed old FAQ section commit f0a1173f18042a062663ba16ca52e7d4f7bbbe4b Author: alejogaletto <[email protected]> Date: Mon Jun 23 18:30:23 2025 +0200 Addressing feedbacj commit 04a612e95eb5d722fc875660904a2a99ed16adc5 Author: alejogaletto <[email protected]> Date: Mon Jun 23 17:56:11 2025 +0200 Addressing feedback commit 4fb829cab2844074cbb3aef6c8e5e88cf886f223 Author: alejogaletto <[email protected]> Date: Fri Jun 13 20:23:45 2025 +0200 Corrected tables and toc file commit ebe23a94e462154a1230b14258b1f4d103708aa7 Author: alejogaletto <[email protected]> Date: Fri Jun 13 20:03:25 2025 +0200 Fixed warnings commit 321b27f4049427474cb71715a3efd8344768b7aa Author: alejogaletto <[email protected]> Date: Fri Jun 13 19:55:51 2025 +0200 Added tables commit eea8e1b31fd4b71b33e708608bdc8a2d2c64212b Author: alejogaletto <[email protected]> Date: Fri Jun 13 19:44:01 2025 +0200 Adding collapse table This reverts commit a7e6420539fefaf9ae8a14e3c2a651168396a11b. commit 44edff883a3ac0719d909c81c0dddc6c3d2a643d Author: alejogaletto <[email protected]> Date: Wed Jun 11 18:20:13 2025 +0200 Correcting titles to address Pwa feedback commit f6af90ad256c3abd17f84f5f42377765fc61e8a7 Author: alejogaletto <[email protected]> Date: Wed Jun 11 17:08:48 2025 +0200 Adding image asked per feedback commit e3229211352a5eae8d6cc190a03ecfe265c9e67e Author: alejogaletto <[email protected]> Date: Wed Jun 11 15:46:03 2025 +0200 Fixed new warning commit 89cd1b222a112e1cd9387e03093b2bcf0e7cc05c Author: alejogaletto <[email protected]> Date: Wed Jun 11 15:37:44 2025 +0200 Fxing warnings commit 9651ff5c362be85a048c97ca127e2a8b8faddfd5 Author: Alejo Galetto <[email protected]> Date: Tue Jun 10 19:01:16 2025 +0200 Update hub/apps/publish/publish-your-app/msix/add-and-edit-store-listing-info.md Co-authored-by: Copilot <[email protected]> commit ec7afbacced56506ba855801efce342f1ef2edd7 Author: Alejo Galetto <[email protected]> Date: Tue Jun 10 18:58:35 2025 +0200 Update hub/apps/publish/publish-your-app/msix/categories-and-subcategories.md Co-authored-by: Copilot <[email protected]> commit 80cd10a3cd438b1d8d6084ad5f1b53a0e7b21947 Author: alejogaletto <[email protected]> Date: Tue Jun 10 21:39:04 2025 +0200 Addressing feedback commit 4aa2aefd5fd036963a2596f29a0fdfb208a5170a Author: alejogaletto <[email protected]> Date: Tue Jun 10 11:15:55 2025 +0200 Updated images commit 163bd52b9099e3143078d33fa87c9666c2130e7c Author: alejogaletto <[email protected]> Date: Mon Jun 9 23:12:37 2025 +0200 Adding space commit a33358a943dd41ef65d79d05d5d24a24829817a2 Author: alejogaletto <[email protected]> Date: Fri Jun 6 16:54:57 2025 -0300 Fixed warning commit a9150a759512fb099a62716921846a935fe9590c Author: alejogaletto <[email protected]> Date: Fri Jun 6 16:48:59 2025 -0300 Fixing warnings commit 4a89af1dc02d5f82b6b2cdff3673f238dd5c21b0 Author: alejogaletto <[email protected]> Date: Fri Jun 6 16:40:01 2025 -0300 Changes to have the same structure as MSI commit 9f410a70c157ed2440bda2ebf081d5931a0a9de1 Author: alejogaletto <[email protected]> Date: Thu Jun 5 17:42:22 2025 -0300 fixing warnings commit 21e27b334ac549e2233a8695759bd0441f66a042 Author: alejogaletto <[email protected]> Date: Thu Jun 5 17:29:17 2025 -0300 Bringing changes from fork commit 43a4c56dedc2b7355752e11632912f29dff0d0b2 Author: alejogaletto <[email protected]> Date: Mon Jun 23 17:16:54 2025 +0200 Addressing feedback and adding questions commit 1400a19af93f6d74e74448ed76437331e9b8af5a Author: alejogaletto <[email protected]> Date: Thu Jun 19 19:43:08 2025 +0100 Fixing warnings commit f97775f35582b63a1bf4650a97520459d59cfd14 Author: alejogaletto <[email protected]> Date: Thu Jun 19 19:38:18 2025 +0100 Addressing warnings commit b20f6cffc2aedb3435c6bdeda8c29cfc1e04d16f Author: alejogaletto <[email protected]> Date: Thu Jun 19 18:51:00 2025 +0100 added new file and updated toc commit d2749b80cb2630a9216ccca9bc407e9614dd165c Author: alejogaletto <[email protected]> Date: Thu Jun 19 17:13:21 2025 +0100 Adding faq section still need to review
1 parent 768c0e8 commit eaf6ee3

48 files changed

Lines changed: 1381 additions & 298 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
---
2+
description: FAQ for new developers starting with Microsoft Store.
3+
title: Get started with Microsoft Store - Frequently Asked Questions
4+
ms.date: 06/18/2025
5+
ms.topic: article
6+
ms.localizationpriority: medium
7+
---
8+
9+
# Get started with Microsoft Store - Frequently Asked Questions
10+
---
11+
<details>
12+
<summary><strong>What is the Microsoft Partner Center and why do I need a developer account to publish my app?</strong></summary>
13+
14+
Microsoft Partner Center is the online portal where you manage the submission, certification, and maintenance of your apps in the Microsoft Store. You must register for a developer account in Partner Center to publish apps to the Store – it’s a prerequisite before starting the app submission process.
15+
16+
Having a developer account gives you access to the Windows Apps & Games dashboard in Partner Center, where you will reserve your app name, upload packages, and track your app’s performance. Partner Center offers two types of developer accounts (Individual or Company) to accommodate different needs.
17+
18+
</details>
19+
20+
<details>
21+
<summary><strong>How do I register for a Microsoft Store developer account? What are the main steps?</strong></summary>
22+
23+
To open a developer account, you will sign up through Partner Center and provide some information. The process is straightforward:
24+
25+
- **Sign in with a Microsoft account:** Go to the Partner Center registration page and sign in with your Microsoft account (or create one if needed). This Microsoft account will be used to log in to your developer dashboard.
26+
- **Join the developer program:** During registration, select the Windows and Xbox program – this enrolls you as a Windows app developer.
27+
- **Choose account type and country:** Specify your account type (Individual or Company) and your country/region. Note that the country/region cannot be changed later.
28+
- **Provide publisher details:** Enter a Publisher Display Name – this is the name shown to customers in the Store. You’ll also provide contact info (address, email, etc.) for verification.
29+
- **Accept terms and pay the fee:** Accept the Microsoft App Developer Agreement and pay the one-time registration fee (approximately $19 USD for individuals or $99 USD for companies, depending on your country).
30+
- **Verify your email and account:** You’ll receive a verification email after payment. Confirm your email to finalize the account creation. Once complete, you can begin the app submission process.
31+
32+
</details>
33+
34+
<details>
35+
<summary><strong>What are the main benefits of distributing my app through the Microsoft Store?</strong></summary>
36+
37+
The Microsoft Store provides access to a vast user base of over a billion Windows customers across more than 200 markets and 100 languages. Beyond reach, the Store also offers various promotion and marketing tools such as:
38+
39+
- **Microsoft Store Ads** to target users by intent
40+
- **Curated collections** and **editorial features** that highlight apps in Store spotlight areas
41+
- Built-in **search discoverability** for relevant categories
42+
43+
These features help increase app visibility and drive downloads more effectively than standalone distribution.
44+
45+
</details>
46+
47+
<details>
48+
<summary><strong>How does publishing to the Store improve my app’s trust and security?</strong></summary>
49+
50+
All apps in the Microsoft Store undergo a thorough certification process, including:
51+
52+
- **Security scans** to check for malware or vulnerabilities
53+
- **Technical validation** for API usage and stability
54+
- **Content policy enforcement** to ensure user-safe experiences
55+
56+
Apps are digitally signed, encrypted, and run in a sandboxed environment to protect users. In addition, Microsoft Store handles **automatic updates**, so users always receive the latest secure version of your app without needing to manually reinstall.
57+
58+
</details>
59+
60+
<details>
61+
<summary><strong>What revenue and commerce options are available if I publish to the Store?</strong></summary>
62+
63+
Developers publishing non-gaming apps can use their **own commerce platform and keep 100% of the revenue**, or opt for Microsoft’s system with a competitive revenue share. Supported monetization models include:
64+
65+
- **In-app purchases**
66+
- **Subscriptions**
67+
- **Advertising**
68+
- **User tipping/donations**
69+
70+
This flexibility makes the Microsoft Store suitable for a wide range of app business models.
71+
72+
</details>
73+
74+
<details>
75+
<summary><strong>What analytics and insights can I access after publishing my app?</strong></summary>
76+
77+
Once your app is live, Partner Center provides robust analytics covering:
78+
79+
- **Acquisitions and installs**
80+
- **User engagement and usage**
81+
- **App health and crash data**
82+
- **Ratings and reviews**
83+
84+
You can filter by market, date, device type, and more. Data can be exported as CSV or TSV files for offline use, or accessed via APIs for integration into custom dashboards.
85+
86+
</details>
87+
88+
<details>
89+
<summary><strong>How does the Store support enterprise distribution and management?</strong></summary>
90+
91+
Developers can distribute apps privately to specific organizations using:
92+
93+
- **Microsoft Store for Business/Education** (for private listings)
94+
- **Microsoft Intune** (for managed deployments)
95+
- **Line-of-business (LOB)** licensing (for exclusive use inside an enterprise)
96+
97+
Apps can be distributed via **online or offline licenses**, providing flexibility for enterprise IT management.
98+
99+
</details>
100+
101+
<details>
102+
<summary><strong>How does publishing to the Store help with app updates and user migration?</strong></summary>
103+
104+
**A:** The Microsoft Store handles **automatic app updates**, ensuring that users always run the latest version. For developers moving from **web-distributed or unpackaged apps**, Microsoft provides:
105+
106+
- **Guidance for migration**
107+
- **Support for preventing dual installs**
108+
- **Tools to transition users seamlessly**
109+
110+
This helps simplify version management and reduces friction during upgrades or transitions from legacy installs.
111+
112+
</details>
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Get your app certified - FAQ
3+
description: This file contains detailed frequently asked questions for the "Get your app certified" section of the Microsoft Store documentation, specifically aimed at helping new developers understand the certification process in Partner Center. It is part of the broader FAQ content initiative to support app developers onboarding through Microsoft Learn.
4+
ms.date: 06/18/2025
5+
ms.topic: faq
6+
---
7+
8+
# Get your app certified
9+
10+
This FAQ is designed to help new developers understand what happens after submitting an app to the Microsoft Store, including how certification works, how long it takes, common reasons for failure, and how to prepare your app to pass certification successfully. This content was created as part of a structured effort to improve the "Submit and manage your apps" documentation on Microsoft Learn.
11+
12+
<details>
13+
<summary><strong>What is the app certification process, and how long does it take?</strong></summary>
14+
15+
After you submit your app to the Store, it enters the certification stage. Microsoft performs a series of checks on your app before it can be published. This typically takes up to three business days, though it can be quicker.
16+
17+
The process includes:
18+
- **Security testing:** Your app is scanned for malware and checked for security vulnerabilities.
19+
- **Technical compliance testing:** Ensures your app doesn’t crash or use prohibited APIs. The Store installs and runs your app to verify it behaves as expected.
20+
- **Content compliance check:** Microsoft reviews your app’s content and Store listing to ensure they comply with Store policies, including age rating and appropriate descriptions.
21+
22+
Once approved, your app typically becomes visible in the Store within about 15 minutes. You'll receive a notification, and your app’s status in the dashboard will show as “In Microsoft Store.”
23+
24+
</details>
25+
26+
<details>
27+
<summary><strong>What happens if my app fails certification?</strong></summary>
28+
29+
If your app fails certification, the submission will be marked as failed or blocked in Partner Center. You will receive a detailed certification report explaining why it failed—whether due to a technical issue or policy violation.
30+
31+
To proceed, review the failure report, fix the issues, and submit a new version. There is no extra cost to resubmit. Common issues include crashes, missing privacy policies, or inaccurate metadata.
32+
33+
</details>
34+
35+
36+
<details>
37+
<summary><strong>How can I improve my app’s chances of passing certification on the first try?</strong></summary>
38+
39+
Here are Microsoft’s best practices to help your app pass certification smoothly:
40+
41+
- **Submit only when ready:** Ensure your app is complete and free of placeholders or broken features.
42+
- **Use Windows App Certification Kit (WACK):** Run this tool locally to pre-test for issues Microsoft will check.
43+
- **Test across environments:** Validate your app on different devices, OS versions, and conditions (including offline).
44+
- **Handle offline scenarios:** Don’t let your app crash without internet—display proper error messages.
45+
- **Provide test info:** Share credentials or instructions in the “Notes for certification” if your app has locked features or requires sign-in.
46+
- **Include a privacy policy:** If your app accesses personal data or services, include a privacy policy URL and display it in the app.
47+
- **Write clear Store listings:** Make sure descriptions truthfully represent the app to avoid rejections for being misleading.
48+
- **Answer age rating questionnaire carefully:** Be truthful to avoid generating incorrect ratings.
49+
- **Accessibility claims:** Only mark your app as accessible if it genuinely meets accessibility standards.
50+
51+
Finally, **always check the latest Microsoft Store Policies** to ensure compliance with technical and content guidelines.
52+
53+
</details>
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Leverage Developer Tools - FAQ
3+
description: Learn how to monitor your app’s analytics, performance, and automate submissions using the Microsoft Store Developer CLI.
4+
ms.date: 06/18/2025
5+
ms.topic: faq
6+
---
7+
8+
# Leverage Developer Tools
9+
10+
This section answers frequently asked questions about using analytics in Partner Center and leveraging the Microsoft Store Developer CLI for publishing and automation.
11+
12+
---
13+
14+
<details>
15+
<summary><strong>What analytics and insights does Partner Center provide for my app after it’s published?</strong></summary>
16+
17+
Once your app is live, **Partner Center** provides a powerful analytics dashboard with detailed reports and data visualizations, covering:
18+
19+
- **Acquisitions (Installs):** Track how many users are downloading your app, where they're coming from (search, direct links, etc.), and which devices or OS versions they use.
20+
- **Usage:** See how users interact with your app, including session length, frequency of use, and custom telemetry events.
21+
- **Health (Quality):** Monitor app stability through crash reports and error tracking, with detailed stack traces and failure types.
22+
- **Ratings & Reviews:** View and respond to user feedback in the Store, including sorting and filtering by market or date.
23+
24+
All reports can be viewed online or exported as Excel/CSV files for further analysis. Developers can also access this data through APIs or CLI tools for integration with custom dashboards. These insights help identify areas for improvement, measure update impact, and better understand your audience.
25+
26+
</details>
27+
28+
---
29+
30+
<details>
31+
<summary><strong>What is the Microsoft Store Developer CLI and how can it help me?</strong></summary>
32+
33+
The **Microsoft Store Developer CLI** is a cross-platform command-line tool that allows developers to automate many Partner Center tasks, such as:
34+
35+
- Listing and retrieving app information
36+
- Uploading new packages
37+
- Updating Store metadata
38+
- Submitting and publishing app updates
39+
40+
This tool is particularly useful for **CI/CD pipelines**, where new builds can be automatically submitted and published. Authentication is done using Azure Active Directory credentials linked to your Partner Center account.
41+
42+
Although still in preview, the CLI offers a flexible alternative to the web UI and supports scripting workflows across Windows, macOS, and Linux. To use it, developers must first configure API access with appropriate permissions. With this tool, teams can significantly streamline and scale their release operations.
43+
44+
</details>
Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: Manage and Update Your App - FAQ
3+
description: Learn how to manage, update, and improve your Microsoft Store app after publishing. Topics include app submissions, rollouts, flights, metadata changes, and managing in-app purchases.
4+
ms.date: 06/18/2025
5+
ms.topic: faq
6+
---
7+
8+
# Manage and Update Your App
9+
10+
This section provides guidance for developers looking to update or manage their published Microsoft Store apps, including controlled rollouts, flights, listing changes, and in-app product updates.
11+
12+
---
13+
14+
<details>
15+
<summary><strong>How do I release an update or new version of my app on the Microsoft Store?</strong></summary>
16+
17+
To release an update, create a new submission in Partner Center for your app:
18+
19+
1. Go to your app's Overview page and select **Update** (or **Create a new submission**).
20+
2. Upload new app packages (e.g., MSIX, APPX), or modify listing info like pricing or descriptions.
21+
3. Submit the update for certification.
22+
23+
Once approved, the new version replaces the previous one in the Store. Existing users will receive the update via the Store automatically.
24+
25+
</details>
26+
27+
---
28+
29+
<details>
30+
<summary><strong>Can I gradually roll out an app update to a percentage of my users?</strong></summary>
31+
32+
Yes. Partner Center supports **gradual rollout** for updates:
33+
34+
- During the submission process, enable **Roll out update gradually** and set an initial percentage (e.g., 5%).
35+
- After publishing, increase the rollout percentage or halt it from the Overview page.
36+
- Halting stops further updates but doesn’t revert the app for users who already received it.
37+
38+
This helps catch issues early and ensures a more stable update for all users.
39+
40+
</details>
41+
42+
---
43+
44+
<details>
45+
<summary><strong>What are package flights and how can I test updates with a limited group of users?</strong></summary>
46+
47+
**Package flights** allow you to distribute test versions of your app to specific groups:
48+
49+
- Set up a flight group (e.g., internal testers).
50+
- Upload a new package for that group, separate from the public version.
51+
- Only designated users receive the update; others continue with the public release.
52+
53+
Flights go through certification but allow testing new features or bug fixes before wide release.
54+
55+
</details>
56+
57+
---
58+
59+
<details>
60+
<summary><strong>How can I change my app’s Store listing details or price after it’s published?</strong></summary>
61+
62+
To change listing details:
63+
64+
1. Create a new submission via the **Update** button in Partner Center.
65+
2. Modify description, screenshots, category, pricing, etc.
66+
3. No need to upload a new package if you're only editing metadata.
67+
68+
These changes still go through certification before being published to ensure Store policy compliance.
69+
70+
</details>
71+
72+
---
73+
74+
<details>
75+
<summary><strong>My app has in-app products (add-ons). How do I manage or update those after publishing?</strong></summary>
76+
77+
To manage add-ons:
78+
79+
- Go to the **Add-ons** section in Partner Center.
80+
- Select the add-on, click **Update**, and start a new submission to change its listing, price, or content.
81+
82+
Add-on updates are certified like app updates. You can also track performance using the **Add-on acquisitions** report. Always keep your in-app product listings accurate and policy-compliant.
83+
84+
</details>
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Manage Your Account - FAQ
3+
description: Learn how to manage your Microsoft Store developer account, including payout setup, user roles, and updating account information.
4+
ms.date: 06/18/2025
5+
ms.topic: faq
6+
---
7+
8+
# Manage Your Account
9+
10+
This section covers frequently asked questions about managing your Microsoft Partner Center account, including payouts, adding users, and keeping your developer information current.
11+
12+
---
13+
14+
<details>
15+
<summary><strong>How do I set up my payout and tax information to get paid from my app’s earnings?</strong></summary>
16+
17+
To receive payments for your app sales or in-app purchases, you must complete your **Payout and Tax Profile** in Partner Center:
18+
19+
1. Sign in to Partner Center and click the **gear icon (Settings)**.
20+
2. Navigate to **Account settings > Payout and tax profile**.
21+
3. Enter your bank information and complete required tax documentation (e.g., Tax ID, W-8/W-9 forms).
22+
23+
Microsoft will validate the data you provide. Until confirmed, your payout status may show as “Action required.” Developer payouts are typically issued monthly, assuming the minimum threshold is met. Be sure to update this profile if your bank or tax info changes to avoid interruptions.
24+
25+
</details>
26+
27+
---
28+
29+
<details>
30+
<summary><strong>Can I add other team members or co-developers to help manage my apps in Partner Center?</strong></summary>
31+
32+
Yes, but only for **Company accounts** (linked to Azure Active Directory). To add users:
33+
34+
1. Go to **Account settings > Users** in Partner Center.
35+
2. Add existing Azure AD users or invite others by email.
36+
3. Assign them specific roles or custom permissions based on their responsibilities.
37+
38+
For example, grant permission to submit apps without making someone a full admin. **Individual accounts** do not support multiple users. Always follow the **principle of least privilege** when assigning roles.
39+
40+
</details>
41+
42+
---
43+
44+
<details>
45+
<summary><strong>What if I need to update my developer account info or if my publisher name changes?</strong></summary>
46+
47+
You can update contact details like **email, phone number, and business address** in your **Account settings**. However:
48+
49+
- Your **publisher display name**, **account type**, and **country/region** cannot be changed after registration.
50+
- For major changes like a rebrand or publisher name update, you’ll likely need to contact Microsoft support and may be required to create a new account.
51+
52+
Keep your tax and payout info updated to avoid any delays in receiving earnings. Accurate contact details also ensure you don’t miss important notices from Microsoft.
53+
54+
</details>

0 commit comments

Comments
 (0)