diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 4c4d0a3955..466a302978 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -7691,8 +7691,8 @@ "redirect_document_id": false }, { - "source_path": "uwp/publish/app-management-and-services.md", - "redirect_url": "/windows/apps/publish/app-management-and-services", + "source_path": "uwp/publish/product-management.md", + "redirect_url": "/windows/apps/publish/product-management", "redirect_document_id": false }, { @@ -7790,11 +7790,6 @@ "redirect_url": "/windows/apps/publish/make-your-app-easier-to-promote", "redirect_document_id": false }, - { - "source_path": "uwp/publish/organizational-licensing.md", - "redirect_url": "/windows/apps/publish/organizational-licensing", - "redirect_document_id": false - }, { "source_path": "uwp/publish/package-flights.md", "redirect_url": "/windows/apps/publish/package-flights", diff --git a/hub/apps/publish/beta-testing-and-targeted-distribution.md b/hub/apps/publish/beta-testing-and-targeted-distribution.md deleted file mode 100644 index cbdc6c2f74..0000000000 --- a/hub/apps/publish/beta-testing-and-targeted-distribution.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: Partner Center gives you several options to let testers try out your app before you offer it to the public. -title: Beta testing and targeted distribution -ms.assetid: 38E4ED22-D6C1-40D8-9B16-6B3E51BD962E -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp, beta test, limited distribution, beta, betas, testing, testers -ms.localizationpriority: medium ---- -# Beta testing and targeted distribution - -No matter how carefully you test your app, there’s nothing like the real-world test of having other people use it. Your testers may discover issues that you’ve overlooked, such as misspellings, confusing app flow, or errors that could cause the app to crash. You’ll then have a chance to fix those problems before you release the submission to the public, resulting in a more polished final product. - -Partner Center gives you several options to let testers try out your app before you offer it to the public. - -Whichever method you choose, here are some things to keep in mind as you beta test your app. - -- You can’t revoke access to the app after a tester has downloaded it. Once they have downloaded the app, they can continue to use it, and they’ll get any updates that you subsequently publish. -- You will need to determine how you’d like to collect feedback from your testers. Consider providing a link that lets your testers easily give feedback via email (or via [Feedback Hub](/windows/uwp/monetize/launch-feedback-hub-from-your-app), if confidentiality is not a concern). -- You can review [analytic reports](analytics.md) for your app, including usage and health reports and any ratings or reviews left by your testers. -- You can include add-ons when you distribute your app to testers. Since you probably don’t want to charge them money for an add-on, you can [generate promotional codes](generate-promotional-codes.md) and distribute them to your testers to let them get the add-on for free, or you can set the price for the add-on to **Free** during testing (then before you make the app available to other customers, create a new submission for the add-on to change its price). Note that each add-on can only be purchased once per Microsoft account, so the same tester won't be able to test the add-on acquisition process more than one time. -- You can give your testers an updated version of your app at any time by creating a new submission with new packages. Your testers will get the update after it goes through the certification process, just like they got the original package, but no one else will be able to get it (unless you make additional changes, such as moving an app from **Private audience** to **Public audience** or changing the membership of groups who can get it). - -## Private audience - -If you want to let testers use your app before it’s available to others, and make sure that no one else can see its listing, use the **Private audience** option under [Visibility](publish-your-app/msix/visibility-options.md) (on the **Pricing and availability** page of your submission). This is the only method that lets you distribute your app to testers while completely preventing anyone else from seeing the app’s Store listing, even if they were able to type in its direct link. - -The **Private audience** option can only be used when you have not already published your app to a public audience. You can use this option with apps targeting any OS version, but your testers must be running Windows 10, version 1607 or later (including Xbox), and must be signed in with the Microsoft account associated with the email address that you provide. - -For more info, see [Private audience](publish-your-app/msix/visibility-options.md#audience). - - -## Package flights - -If you have published your app already, you can create package flights to distribute a different set of packages to the people that you specify. You can even create multiple package flights for the same app to use with different groups of people. This is a great way to try out different packages simultaneously, and you can pull packages from a flight into your non-flighted submission if you decide the packages are ready to distribute to everyone. - -Package flights can be used with apps targeting any OS version, but your testers can only get the app if they are running Windows.Desktop build 10586 or later or Xbox One. - -For more info, see [Package flights](package-flights.md). - -## Hiding the app in the Store and using promotional codes - -This option offers another way to limit distribution of an app to only a certain group of testers, while preventing anyone else from discovering your app in the Store (or acquiring it without a promotional code). However, unlike the private audience option, it could be possible for anyone to see your app’s listing if they have the direct link. If confidentiality is critical for your submission, we recommend publishing to a private audience instead. - -Hiding the app and using promotional codes can be used with apps targeting any OS version, but your testers can only get the app if they are running Windows 10 or Windows 11. - -To use this option: - -- In the **Visibility** section of the **Pricing and availability** page, under [Discoverability](publish-your-app/msix/visibility-options.md#discoverability), select **Make this product available but not discoverable in the Store**. Choose the option for **Stop acquisition: Any customer with a direct link can see the product’s Store listing, but they can only download it if they owned the product before, or have a promotional code and are using a Windows 10 or Windows 11 device**. -- After the app passes certification, [generate promotional codes](generate-promotional-codes.md) for the app and distribute them to your testers. You can generate codes that allow up to 1600 redemptions for a single app in a six month period. These codes will give your testers a direct link to the app’s listing, and will allow them to download it for free, even if you have set a price for it when you created your submission. -- When you're ready to make your app available to the public, create a new submission and change the **Visibility** option to **Make this product available and discoverable in the Store** (along with any other changes you'd like). - - -## Targeted distribution with a link to your app's listing - -With this, no customers will be able to find the app by searching or browsing the Store, but anyone with the direct link to its Store listing can download it on a device running on Windows 10 or Windows 11. Keep in mind that in order for your testers to download the app at no cost, you must set its price to **Free**. - -To use this option: -- In the **Visibility** section of the **Pricing and availability** page, under [Discoverability](publish-your-app/msix/visibility-options.md#discoverability), select **Make this product available but not discoverable in the Store**. Choose the option for **Direct link only: Any customer with a direct link to the product’s listing can download it, except on Windows 8.x.**. -- After your product has been published, distribute the link (the **URL** on the [App identity page](view-app-identity-details.md)) to your testers so they can try it out. -- When you're ready to make your app available to the public, create a new submission and change the **Visibility** option to **Make this product available and discoverable in the Store** (along with any other changes you'd like). - diff --git a/hub/apps/publish/create-a-custom-app-promotion-campaign.md b/hub/apps/publish/create-a-custom-app-promotion-campaign.md index 81d0e64778..525fc0362b 100644 --- a/hub/apps/publish/create-a-custom-app-promotion-campaign.md +++ b/hub/apps/publish/create-a-custom-app-promotion-campaign.md @@ -1,5 +1,5 @@ --- -description: In addition to creating an ad campaign for your app that will run in Windows apps, you can promote your app using other channels. +description: How to promote your app using other channels. title: Create a custom app promotion campaign ms.assetid: 7C9BF73E-B811-4FC7-B1DD-4A0C2E17E95D ms.date: 10/30/2022 @@ -9,14 +9,12 @@ ms.localizationpriority: medium --- # Create a custom app promotion campaign -In addition to creating an [ad campaign for your app](/windows/uwp/monetize/index) that will run in Windows apps, you can also promote your app using other channels. For example, you can promote your app using a third-party app marketing provider, or you might post links to your app on social media sites. These activities are called *custom campaigns*. - -If you run custom campaigns for your app, you can track the relative performance of each campaign by creating a different URL for each custom campaign, where each URL contains a different *campaign ID*. When a customer running Windows 10 clicks a URL that contains a campaign ID, Microsoft associates the click with the corresponding custom campaign and makes this data available to you in [Partner Center](https://partner.microsoft.com/dashboard). +To track the performance of each custom campaign, create a unique URL with a different campaign ID. When a Windows 10 user clicks one of these URLs, Microsoft links the click to that campaign and provides the data in [Partner Center](https://partner.microsoft.com/dashboard). > [!IMPORTANT] > This data is only tracked for customers on Windows 10. Customers using other operating systems can still follow the link to your app's listing, but data about those customers' activities will not be included. -There are two main types of data associated with custom campaigns: *page views* for your app's Store listing, and *conversions*. A conversion is an app acquisition that results from a customer viewing your app's Store listing page from a URL that includes a custom campaign ID. For more details about conversions, see [Understanding how app acquisitions qualify as conversions](#understanding-how-acquisitions-qualify-as-conversions) in this topic. +Custom campaign data includes page views of your app’s Store listing and conversions. A conversion occurs when a user acquires your app after viewing its Store page via a campaign-specific URL. For more on conversions, see [Understanding how app acquisitions qualify as conversions](#understanding-how-acquisitions-qualify-as-conversions) in this topic. You can retrieve custom campaign performance data for your app in the following ways: diff --git a/hub/apps/publish/create-customer-groups.md b/hub/apps/publish/create-customer-groups.md index ecf694d66c..845f773dfd 100644 --- a/hub/apps/publish/create-customer-groups.md +++ b/hub/apps/publish/create-customer-groups.md @@ -13,7 +13,49 @@ You can create *customer groups* that include a subset of your app's customers. To view and create customer groups, expand **Engage** in the left navigation menu of [Partner Center](https://partner.microsoft.com/dashboard), then select **Customer groups**. -Currently, two types of customer groups are supported: +- **Known user groups.** These are groups of specific customers, created from the email addresses associated with their Microsoft accounts. Known user groups are most often used with [package flighting](package-and-distribution.md#package-flights) in order to deliver specific packages to customers in that group, or for distribution of a submission to a [private audience](publish-your-app/msix/visibility-options.md#audience). For more info, see [Create known user groups](#create-known-user-groups). -- **Segments.** These are dynamically-created groups of Windows 10 or Windows 11 customers who meet the demographic or revenue criteria that you choose. Segments are typically used with [push notifications](send-push-notifications-to-your-apps-customers.md) or [targeted offers](use-targeted-offers-to-maximize-engagement-and-conversions.md). For more info, see [Create customer segments](create-customer-segments.md). -- **Known user groups.** These are groups of specific customers, created from the email addresses associated with their Microsoft accounts. Known user groups are most often used with [package flighting](package-flights.md) in order to deliver specific packages to customers in that group, or for distribution of a submission to a [private audience](publish-your-app/msix/visibility-options.md#audience). For more info, see [Create known user groups](create-known-user-groups.md). +## App statistics + +The **App statistics** section on the segment provides some info about your app, as well as the size of the segment you just created. + +Note that **Available app customers** does not reflect the actual number of customers who have acquired your app, but only the number of customers that are available to be included in segments (that is, customers that we can determine meet age requirements, have acquired your app on Windows 10 or Windows 11, and who are associated with a valid Microsoft account). + +If you view the results and **Customers in this segment** says **Small**, the segment doesn't include enough customers and the segment is marked as inactive. Inactive segments can't be used for notifications or other features. You might be able to activate and use a segment by doing one of the following: + +- In the **Define inclusion conditions** section, adjust the filter criteria so the segment includes more customers. +- On the **Customer groups** page, in the **Inactive segments** section, select **Refresh** to see if the segment now contains enough customers (for example, if more customers who meet your segment criteria have downloaded your app since you first created the segment, or if more existing customers now meet your segment criteria). + +## Create known user groups + +Known user groups let you add specific people to a group, using the email address associated with their Microsoft account. These known user groups are most often used to distribute specific packages to a selected group of people with [package flights](package-and-distribution.md#package-flights), or for distribution of a submission to a [private audience](publish-your-app/msix/visibility-options.md#audience). They can also be used for engagement campaigns, such as sending [targeted offers](use-targeted-offers-to-maximize-engagement-and-conversions.md) to a group of specific customers. + +In order to be counted as a member of the group, each person must be authenticated with the Store using the Microsoft account associated with the email address you provide. To download the app with package flighting, group members must be using a version of Windows 10 or Windows 11 that supports package flights (Windows.Desktop build 10586 or later or Xbox One). With private audience submissions, group members must be using Windows 10, version 1607 or later (including Xbox One). + +## To create a known user group + +1. In [Partner Center](https://partner.microsoft.com/dashboard), expand **Engage** in the left navigation menu and then select **Customer groups**. +2. In the **My customer groups** section, select **Create new group**. +3. On the next page, enter a name for your group in the **Group name** box. +4. Ensure that the **Known user group** radio button is selected. +5. Enter the email addresses of the people you'd like to add to the group. You must include at least one email address, with a maximum of 10,000. You can enter email addresses directly into the field (separated by spaces, commas, semicolons, or line breaks), or you can click the **Import .csv** link to create the flight group from a list of email addresses in a .csv file. +6. Select **Save**. + +The group will now be available for you to use. + +You can also create a known user group by selecting **Create a flight group** from the [package flight](package-and-distribution.md#package-flights) creation page. Note that you'll need to re-enter any info you've already provided in the package flight creation page if you do this. + +> [!IMPORTANT] +> When using known user groups with package flighting, be sure that you have obtained any necessary consent from people that you add to your group, and that they understand that they will be getting packages that are different from your non-flighted submission. + +## To edit a known user group + +You cannot remove a known user group from Partner Center (or change its name) after it's been created, but you can edit its membership at any time. + +To review and edit your known user groups, expand the **Engage** menu in the left navigation menu and select **Customer groups**. Under **My customer groups**, select the name of the group you want to edit. You can also edit a known user group from the package flight creation page by selecting **View and manage existing groups** when creating a new flight, or by selecting the group's name from a package flight's overview page. + +After you've selected the group you want to edit, you can add or remove email addresses directly in the field. + +For larger changes, select **Export .csv** to save your group membership info to a .csv file. Make your changes in this file, then click **Import .csv** to use the new version to update the group membership. + +Note that it may take up to 30 minutes for membership changes to be implemented. You don't need to publish a new submission in order for new group members to be able to access your submission through package flights or private audience; they will have access as soon as the changes are implemented. diff --git a/hub/apps/publish/create-customer-segments.md b/hub/apps/publish/create-customer-segments.md deleted file mode 100644 index 7aebf202fa..0000000000 --- a/hub/apps/publish/create-customer-segments.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: Learn how to create customer segments so you can target a subset of your customer base for promotional or engagement purposes. -title: Create customer segments -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp, segment, segments, targeted group, customers -ms.assetid: 58185f6c-d61f-478b-ab24-753d8986cd5a -ms.localizationpriority: medium ---- -# Create customer segments - -There are times when you may want to target a subset of your customer base for promotional and engagement purposes. You can accomplish this in [Partner Center](https://partner.microsoft.com/dashboard) by creating a type of [customer group](create-customer-groups.md) known as a *segment* that includes the Windows 10 or Windows 11 customers who meet the demographic or revenue criteria that you choose. - -For example, you could create a segment that includes only customers who are age 50 or older, or that includes customers who’ve spent more than $10 in the Microsoft Store. You could also combine these criteria and create a segment that includes all customers over 50 who have spent more than $10 in the Store. - -We provide a few segment templates to help get you started, but you can define and combine the criteria however you'd like. - -> [!TIP] -> Segments can be used to send [targeted notifications](send-push-notifications-to-your-apps-customers.md) or [targeted offers](use-targeted-offers-to-maximize-engagement-and-conversions.md) to a group of customers as part of your engagement campaigns. - -Things to keep in mind about customer segments: -- After you save a segment, it takes 24 hours before you’ll be able to use it for [targeted push notifications](send-push-notifications-to-your-apps-customers.md). -- Segment results are refreshed daily, so you may see the total count of customers in a segment change from day to day as customers drop in or out of the segment criteria. -- Most segment attributes are calculated using all historical data, although there are some exceptions. For example, **App acquisition date**, **Campaign ID**, **Store page view date**, and **Referrer URI domain** are limited to the last 90 days of data. -- Segments only include customers who acquired your app on Windows 10 or Windows 11 while signed in with a valid Microsoft account. -- Segments do not include any customers who are younger than 17 years old. - -## To create a customer segment - -1. In [Partner Center](https://partner.microsoft.com/dashboard), expand **Engage** in the left navigation menu and then select **Customer groups**. -2. On the **Customer groups** page, do one of the following: - - In the **My customer groups** section, select **Create new group** to define a segment from scratch. On the next page, select the **Segment** radio button. - - In the **Segment templates** section, select **Copy** next to one of the predefined segments (that you can use as is or modify to suit your needs). -3. In the **Group name** box, enter a name for your segment. -4. In the **Include customers from this app** list, select one of your apps to target. -5. In the **Define inclusion conditions** section, specify the filter criteria for the segment. - - You can choose from a variety of filter criteria, including **Acquisitions**, **Acquisition source**, **Demographic**, **Rating**, **Churn prediction**, **Store purchases**, **Store acquisitions**, and **Store spend**. - - For example, if you wanted to create a segment that only included your app customers who are 18- to 24-years old, you’d select the filter criteria [**Demographic**] [**Age group**] [**is**] [**18 to 24**] from the drop-down lists. - - You can build more complex segments by using AND/OR queries to include or exclude customers based on various attributes. To add an OR query, select **+ OR statement**. To add an ADD query, select **Add another filter**. - - So, if you wanted to refine that segment to only include male customers who are in the specified age range, you would select **Add another filter** and then select the additional filter criteria [**Demographic**] [**Gender**] [**is**] [**Male**]. For this example, the **Segment definition** would display **Age group == 18 to 24 && Gender == Male**. - - ![Example of filter criteria for a segment](images/create-segment-inclusions.png) -6. Select **Save**. - -> [!IMPORTANT] -> You won't be able to use a segment that includes too few customers. If your segment definition does not include enough customers, you can adjust the segment criteria, or try again later, when your app may have acquired more customers that meet your segment criteria. - - -## App statistics - -The **App statistics** section on the segment provides some info about your app, as well as the size of the segment you just created. - -Note that **Available app customers** does not reflect the actual number of customers who have acquired your app, but only the number of customers that are available to be included in segments (that is, customers that we can determine meet age requirements, have acquired your app on Windows 10 or Windows 11, and who are associated with a valid Microsoft account). - -If you view the results and **Customers in this segment** says **Small**, the segment doesn't include enough customers and the segment is marked as inactive. Inactive segments can't be used for notifications or other features. You might be able to activate and use a segment by doing one of the following: - -- In the **Define inclusion conditions** section, adjust the filter criteria so the segment includes more customers. -- On the **Customer groups** page, in the **Inactive segments** section, select **Refresh** to see if the segment now contains enough customers (for example, if more customers who meet your segment criteria have downloaded your app since you first created the segment, or if more existing customers now meet your segment criteria). diff --git a/hub/apps/publish/create-known-user-groups.md b/hub/apps/publish/create-known-user-groups.md deleted file mode 100644 index 58615691d9..0000000000 --- a/hub/apps/publish/create-known-user-groups.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -description: Learn how to create known user groups to use for package flighting and more. -title: Create known user groups -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp, targeted group, customers, flight group, user groups, known users -ms.localizationpriority: medium ---- -# Create known user groups - -Known user groups let you add specific people to a group, using the email address associated with their Microsoft account. These known user groups are most often used to distribute specific packages to a selected group of people with [package flights](package-flights.md), or for distribution of a submission to a [private audience](publish-your-app/msix/visibility-options.md#audience). They can also be used for engagement campaigns, such as sending [targeted notifications](send-push-notifications-to-your-apps-customers.md) or [targeted offers](use-targeted-offers-to-maximize-engagement-and-conversions.md) to a group of specific customers. - -In order to be counted as a member of the group, each person must be authenticated with the Store using the Microsoft account associated with the email address you provide. To download the app with package flighting, group members must be using a version of Windows 10 or Windows 11 that supports package flights (Windows.Desktop build 10586 or later or Xbox One). With private audience submissions, group members must be using Windows 10, version 1607 or later (including Xbox One). - -## To create a known user group - -1. In [Partner Center](https://partner.microsoft.com/dashboard), expand **Engage** in the left navigation menu and then select **Customer groups**. -2. In the **My customer groups** section, select **Create new group**. -3. On the next page, enter a name for your group in the **Group name** box. -4. Ensure that the **Known user group** radio button is selected. -5. Enter the email addresses of the people you'd like to add to the group. You must include at least one email address, with a maximum of 10,000. You can enter email addresses directly into the field (separated by spaces, commas, semicolons, or line breaks), or you can click the **Import .csv** link to create the flight group from a list of email addresses in a .csv file. -6. Select **Save**. - -The group will now be available for you to use. - -You can also create a known user group by selecting **Create a flight group** from the [package flight](package-flights.md) creation page. Note that you'll need to re-enter any info you've already provided in the package flight creation page if you do this. - -> [!IMPORTANT] -> When using known user groups with package flighting, be sure that you have obtained any necessary consent from people that you add to your group, and that they understand that they will be getting packages that are different from your non-flighted submission. - -## To edit a known user group - -You cannot remove a known user group from Partner Center (or change its name) after it's been created, but you can edit its membership at any time. - -To review and edit your known user groups, expand the **Engage** menu in the left navigation menu and select **Customer groups**. Under **My customer groups**, select the name of the group you want to edit. You can also edit a known user group from the package flight creation page by selecting **View and manage existing groups** when creating a new flight, or by selecting the group's name from a package flight's overview page. - -After you've selected the group you want to edit, you can add or remove email addresses directly in the field. - -For larger changes, select **Export .csv** to save your group membership info to a .csv file. Make your changes in this file, then click **Import .csv** to use the new version to update the group membership. - -Note that it may take up to 30 minutes for membership changes to be implemented. You don't need to publish a new submission in order for new group members to be able to access your submission through package flights or private audience; they will have access as soon as the changes are implemented. diff --git a/hub/apps/publish/distribute-lob-apps-to-enterprises.md b/hub/apps/publish/distribute-lob-apps-to-enterprises.md deleted file mode 100644 index 414fd91a82..0000000000 --- a/hub/apps/publish/distribute-lob-apps-to-enterprises.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -description: You can publish line-of-business (LOB) apps directly to enterprises for volume acquisition via the Microsoft Store for Business or Microsoft Store for Education, without making the apps broadly available in the Store. -title: Distribute LOB apps to enterprises -ms.assetid: 2050126E-CE49-4DE3-AC2B-A572AC895158 -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp, lob, line-of-business, enterprise apps, store for business, store for education, enterprise -ms.localizationpriority: medium ---- - -# Distribute LOB apps to enterprises - -You have several options for distributing line of business (LOB) apps to your organization’s users using [MSIX packages](/windows/msix/) without making the apps broadly available to the public. You can use device management tools, configure an App Installer-based deployment, sideload the apps directly, or publish the apps to the Microsoft Store for Business or Microsoft Store for Education. - -## Microsoft Endpoint Configuration Manager and Microsoft Intune - -If your organization uses Microsoft Endpoint Configuration Manager or Microsoft Intune to manage devices, you can deploy LOB apps using these tools. For more information, see these articles: - -* [Introduction to application management in Configuration Manager](/configmgr/apps/understand/introduction-to-application-management) -* [Overview of the app lifecycle in Microsoft Intune](/intune/apps/app-lifecycle) - -## App Installer - -App Installer enables Windows 10 or Windows 11 apps to be installed by double-clicking an MSIX app package directly, or by double-clicking an .appinstaller file that installs the app package from a web server. This means that users don't need to use PowerShell or other developer tools to install LOB apps. App Installer can also install app packages that include optional packages and related sets. - -App Installer can be downloaded for offline use in the enterprise from Microsoft Store for Business [web portal](https://businessstore.microsoft.com/store/details/app-installer/9NBLGGH4NNS1). For more information about App Installer, see [Install Windows 10 or Windows 11 apps with App Installer](/windows/msix/app-installer/app-installer-root). - -## Sideloading - -Another option for distributing LOB apps directly to users in your organization is sideloading. This option is similar to App Install-based deployment in that it enables users to install MSIX app packages directly. Starting in Windows 10 version 2004, sideloading is enabled by default and users can install apps by double-clicking signed MSIX app packages. On Windows 10 version 1909 and earlier, sideloading requires some additional configuration and the use of a PowerShell script. For more info, see [Sideload LOB apps in Windows 10 or Windows 11](/windows/application-management/sideload-apps-in-windows-10). - -## Microsoft Store for Business or Microsoft Store for Education - -> [!NOTE] -> Microsoft [has announced](/lifecycle/announcements/microsoft-store-for-business-education-retiring) the retirement of the Microsoft Store for Business and Microsoft Store for Education in 2023. The instructions below are therefore no longer valid. For the replacement, please refer to [Add a Windows line-of-business app to Microsoft Intune](/mem/intune/apps/lob-apps-windows). - -You can publish line-of-business (LOB) apps directly to enterprises for volume acquisition via Microsoft Store for Business or Microsoft Store for Education, without making the apps broadly available in the Store. When using this option, the apps are signed by the Store and must comply with the standard Store Policies. - -> [!NOTE] -> At this time, only free apps can be distributed exclusively to enterprises via Microsoft Store for Business or Microsoft Store for Education. If you submit a paid app as LOB, it will not be available to the enterprise.  - -> [!IMPORTANT] -> You cannot use the [Microsoft Store submission API](/windows/uwp/monetize/create-and-manage-submissions-using-windows-store-services) to publish LOB apps directly to enterprises. All submissions for LOB apps must be published through Partner Center. - -### Set up the enterprise association - -The first step in publishing LOB apps exclusively to an enterprise is to establish the association between your account and the enterprise’s private store. - -> [!IMPORTANT] -> This association process must be initiated by the enterprise, and must use the email address associated with the Microsoft account that was used to create the developer account. For more info, see [Working with line-of-business apps](/microsoft-store/working-with-line-of-business-apps). - -When an enterprise chooses to invite you to publish apps for their exclusive use, you’ll get an email that includes a link to confirm the association. You can also confirm these associations by going to the **Enterprise associations** section of your **Account settings** (as long as you are signed in with the Microsoft account that was used to open the developer account). - -To confirm the association, click **Accept**. Your account will then be able to publish apps for that enterprise’s exclusive use. - -### Submit LOB apps - -Once you’re ready to publish an app for an enterprise’s exclusive use, the process is similar to the app submission process. The app goes through the same [certification process](publish-your-app/msix/app-certification-process.md), and must comply with all [Microsoft Store Policies](store-policies.md). There are just a few parts of the process that are different. - -#### Visibility - -After you've set up an enterprise association, every time you submit an app you’ll see a drop-down box in the **Visibility** section of the submission’s **Pricing and availability** page. By default, this is set to **Retail distribution**. To make the app exclusive to an enterprise, you’ll need to choose **Line-of-business (LOB) distribution**. - -Once **Line-of-business (LOB) distribution** is selected, the usual **Visibility** options will be replaced with a list of the enterprises to which you can publish exclusive apps. No one outside of the enterprise(s) you select will be able to view or download the app. - -You must select at least one enterprise in order to publish an app as line-of-business. - - - -#### Organizational licensing - -By default, the box for **Store-managed (online) volume licensing** is checked when you submit an app. When publishing LOB apps, this box must remain checked so that the enterprise can acquire your app in volume. This will not make the app available to anyone outside of the enterprise(s) that you selected in the **Distribution and visibility** section. - -If you’d like to make the app available to the enterprise via disconnected (offline) licensing, you can check the **Disconnected (offline) licensing** box as well. - -For more info, see [Organizational licensing options](organizational-licensing.md). - -#### Age ratings - -For LOB apps, the [age ratings](publish-your-app/msix/age-ratings.md) step of the submission process works the same as for retail apps, but you also have an additional option that allows you to indicate the Store age rating of your app manually rather than completing the questionnaire or importing an existing IARC rating ID. This manual rating can only be used with LOB distribution, so if you ever change the **Visibility** setting of the app to **Retail distribution**, you'll need to take the age ratings questionnaire before you can publish the submission. - -### Enterprise deployment of LOB apps - -After you click **Submit to the Store**, the app will go through the certification process. Once it’s ready, an admin for the enterprise must add it to their private store in the Microsoft Store for Business or Microsoft Store for Education portal. The enterprise can then deploy the app to its users. - -> [!NOTE] -> In order to get your LOB app, the organization must be located in a [supported market](/windows/whats-new/windows-store-for-business-overview#supported-markets), and you must not have [excluded that market](publish-your-app/msix/market-selection.md) when submitting your app. - -For more info, see [Working with line-of-business apps](/microsoft-store/working-with-line-of-business-apps) and [Distribute apps using your private store](/microsoft-store/distribute-apps-from-your-private-store). - -### Update LOB apps - -To publish updates to an app that you’ve already published as LOB, simply create a new submission. You can upload new packages or make any other changes, then click **Submit to the Store** to make the updated version available. Be sure to keep the enterprise selections in **Visibility** the same, unless you intentionally want to make changes such as selecting an additional enterprise to acquire the app, or removing one of the enterprises to which you’d previously distributed it. - -If you want to stop offering an app that you’ve previously published as line-of-business, and prevent any new acquisitions, you’ll need to create a new submission. First, you’ll need to change your **Visibility** selection from **Line-of-business (LOB) distribution** to **Retail distribution**. Then, in the [Discoverability](publish-your-app/msix/visibility-options.md#discoverability) section, choose **Make this product available but not discoverable in the Store** with the **Stop acquisition** option. - -After the submission goes through the certification process, the app will no longer be available for new acquisitions (although anyone who already has it will continue to be able to use it). - -> [!NOTE] -> When changing an app to **Retail distribution**, you'll need to complete the [age ratings questionnaire](publish-your-app/msix/age-ratings.md) if you haven't done so already, even if the app will not be available for new acquisitions. diff --git a/hub/apps/publish/engage-with-your-customers.md b/hub/apps/publish/engage-with-your-customers.md index 932c324bde..94d7b94eec 100644 --- a/hub/apps/publish/engage-with-your-customers.md +++ b/hub/apps/publish/engage-with-your-customers.md @@ -17,19 +17,6 @@ Drive customer engagement and satisfaction by using features like push notificat ![Define customer segments](images/engage-pie-chart.png) :::column-end::: :::column span="2"::: -**Define customer segments** - -Use the dashboard to define segments of your app’s customers, based on demographic or revenue criteria that you choose. - -[Define segments](create-customer-segments.md) - :::column-end::: -:::row-end::: - -:::row::: - :::column::: - ![Targeted Offers](images/engage-phone-truck.png) - :::column-end::: - :::column span="2"::: **Targeted Offers** Show attractive, personalized content to specific segments of your customers to increase engagement, retention, and monetization. @@ -71,26 +58,6 @@ Run experiments in your apps to measure the effectiveness of feature changes bef ![App feedback](images/engage-feedback.png) :::column-end::: :::column span="2"::: -**App feedback** - -Invite your Windows 10 or Windows 11 customers to tell you what they think by directing them to the Feedback Hub, where they can submit problems, suggestions, and upvotes. Then review and respond to their feedback in the dashboard. - -[Get feedback](respond-to-customer-feedback.md) - :::column-end::: -:::row-end::: - -:::row::: - :::column::: - ![Respond to reviews](images/ads-community-campaign.png) - :::column-end::: - :::column span="2"::: -**Respond to reviews** - -Follow up and connect with your customers by responding publicly or privately to their reviews. You can submit your responses either in the dashboard or by using our REST API. - -[Respond to reviews](respond-to-customer-reviews.md) - :::column-end::: -:::row-end::: ## Engagement analytics diff --git a/hub/apps/publish/generate-preinstall-packages-for-oems.md b/hub/apps/publish/generate-preinstall-packages-for-oems.md deleted file mode 100644 index 9c1eac4732..0000000000 --- a/hub/apps/publish/generate-preinstall-packages-for-oems.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -description: If your developer account has been granted the appropriate permissions, you can generate and download preinstall packages so that an OEM can include your app in their OS image. -title: Generate preinstall packages for OEMs -ms.assetid: AC3A45E8-7BBD-44E9-B2D3-B74B7C9B2BC9 -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp -ms.localizationpriority: medium ---- -# Generate preinstall packages for OEMs - -If your developer account has been granted the appropriate permissions, you can generate and download preinstall packages so that an OEM can include your app in their OS image. Preinstall permissions are only enabled on developer accounts that are sponsored by OEMs. - -## Important preinstall policy & limitations - -Preinstall apps must be certified through [Partner Center](https://partner.microsoft.com/dashboard) to have the latest Store license so that they are able to connect to the Store and receive app updates. - -Any app that is preinstalled must be and remain free in all markets. - -## Generating preinstall packages - -Once an account has been enabled with preinstall permissions, complete the following steps: - -1. In Partner Center, navigate to the app that is to be preinstalled. -1. In the left navigation menu, expand **App management** and select **Current packages**. -1. In the **Request packages for OS preinstallation** section, select **Enable downloadable packages**. -1. In the confirmation dialog will, select **Enable**. -1. Find the package that you want to download and select the appropriate **Generate package** link. - - > [!NOTE] - > Generation time for preinstall packages will vary depending on the size of the package you have selected. You can leave this page and come back later, or you can leave the page open while your package is being generated. - -1. After the package has been generated, a link to **Download package** will appear. Select this link to download the .zip file. - -You can then provide the .zip file to the OEM for inclusion in their OS image. - -## Support - -If you have further questions about generating preinstall packages, please email . diff --git a/hub/apps/publish/generate-promotional-codes.md b/hub/apps/publish/generate-promotional-codes.md index 28effdfe3d..15295fa829 100644 --- a/hub/apps/publish/generate-promotional-codes.md +++ b/hub/apps/publish/generate-promotional-codes.md @@ -10,7 +10,7 @@ ms.localizationpriority: medium # Generate promotional codes -[Partner Center](https://partner.microsoft.com/dashboard) lets you generate promotional codes for an app or add-on that you have published in the Microsoft Store. Promotional codes are an easy way to give influential users free access to your app or add-on. You might also use promotional codes to address customer service scenarios by giving users free access to your app or add-on, or for [beta testing](beta-testing-and-targeted-distribution.md). +[Partner Center](https://partner.microsoft.com/dashboard) lets you generate promotional codes for an app or add-on that you have published in the Microsoft Store. Promotional codes are an easy way to give influential users free access to your app or add-on. You might also use promotional codes to address customer service scenarios by giving users free access to your app or add-on, or for [beta testing](package-and-distribution.md#beta-testing-and-targeted-distribution). Each promotional code has a corresponding unique redeemable URL that a customer can click in order to redeem the code and install your app or add-on from the Microsoft Store. Note that your app must pass the final publishing phase of the [app certification process](publish-your-app/msix/app-certification-process.md) before customers can redeem a promotional code to install it. diff --git a/hub/apps/publish/gradual-package-rollout.md b/hub/apps/publish/gradual-package-rollout.md deleted file mode 100644 index 0c321d1a2c..0000000000 --- a/hub/apps/publish/gradual-package-rollout.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -description: When you publish an update to a submission, you can choose to gradually roll out the updated packages to a percentage of customers who have your package installed on Windows 10 or Windows 11 (including Xbox). -title: Gradual package rollout -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp -ms.assetid: 65d578a6-4e26-484c-90af-b2cd916f3634 -ms.localizationpriority: medium ---- -# Gradual package rollout - -When you publish an update to a submission, you can choose to gradually roll out the updated packages to a percentage of customers who have your package installed on Windows 10 or Windows 11 (including Xbox). This allows you to monitor feedback and analytic data for the specific packages to make sure you’re confident about the update before rolling it out more broadly. You can increase the percentage (or halt the update) any time without having to create a new submission. - -> [!IMPORTANT] -> Your rollout selections apply to all of your packages, but will only apply to your customers running OS versions that support package flights (Windows.Desktop build 10586 or later and Xbox), including any customers who get the app via [Store-managed (online) licensing](organizational-licensing.md) via [Microsoft Store for Business](https://businessstore.microsoft.com/store) or [Microsoft Store for Education](https://educationstore.microsoft.com/store). When using gradual package rollout, customers on earlier OS versions will not get packages from the latest submission until you finalize the package rollout as described below. - -Note that all of your customers will see the Store listing details that you entered with your latest submission. The rollout settings only apply to the packages that customers install, for updates to existing customers. - -> [!TIP] -> Package rollout distributes packages to a random selection of customers who have your package installed -in the percentages that you specify. To distribute specific packages to selected customers that you specify, you can use package flights. You can also combine rollout with your package flights if you want to gradually distribute an update to one of your flight groups. - - -## Setting the rollout percentage - -You can select to roll out your update on the **Packages** page of an updated submission. To do so, check the box that says **Roll out update gradually after this submission is published (to Windows 10 or Windows 11 customers only)**. Then enter the percentage of customers who should get the update when the submission is first published. For example, you might enter 5 if you want to start by rolling the update out to only a small percentage of your app’s existing customers who have already installed this app. - -Click **Update** to save your selections. After your app completes the certification process, the packages will be distributed to existing customers according to the percentage that you specified for updates. - - -## Adjusting the rollout after the submission is published - -To adjust the rollout after the submission has been published, go to your app’s Overview page. You can drag the selector to change the percentage of customers getting the packages from your newest submission. Click **Update** to save your selections. The packages will then start to be distributed to existing customers who have your package installed according to the percentage that you specified for updates. - - -## Completing the rollout - -Before you can create a new submission, you'll need to complete the package rollout. You can **finalize** the rollout and distribute the latest packages to all of your customers, or **halt** the rollout to stop distributing the latest packages. - -If you have confidence in the update and would like to make it available to all of your customers, click **Finalize package rollout** to distribute the newest packages to all of your customers. - -> [!TIP] -> Changing the rollout percentage to 100% does not ensure that all of your customers will get the packages from the latest submissions, because some customers may be on OS versions that don’t support rollout. You must finalize the rollout in order to stop distributing the older packages and update all existing customers to the newer ones. - -If you find that there are problems with the update and you don’t want to distribute it any further, you can click **Halt package rollout** to stop distributing packages from the latest submission. Once you halt a package rollout, those packages will no longer be distributed to any customers; only the packages from the previous submission will be used for any new or updating customers. However, any customers who already had the newer packages will keep those packages; they won’t be rolled back to the previous version. To provide an update to these customers, you’ll need to create a new submission with the packages you’d like them to get. Note that if you use a gradual rollout in your next submission, customers who had the package you halted will be offered the new update in the same order they were offered the halted package. The new rollout will be between your last finalized submission and your newest submission; once you halt a package rollout, those packages will no longer be distributed to any customers. diff --git a/hub/apps/publish/msstore-dev-cli/overview.md b/hub/apps/publish/msstore-dev-cli/overview.md index 2144010047..4b4685ad65 100644 --- a/hub/apps/publish/msstore-dev-cli/overview.md +++ b/hub/apps/publish/msstore-dev-cli/overview.md @@ -55,3 +55,5 @@ These are the Microsoft Store Developer CLI (preview) available commands: | [init](./commands.md#init-command) | Helps you setup your application to publish to the Microsoft Store. | | [package](./commands.md#package-command) | Helps you package your Microsoft Store Application as an MSIX. | | [publish](./commands.md#publish-command) | Publishes your application to the Microsoft Store. | + +For more info, see: [Commands](commands.md). \ No newline at end of file diff --git a/hub/apps/publish/organizational-licensing.md b/hub/apps/publish/organizational-licensing.md deleted file mode 100644 index 0a6477c754..0000000000 --- a/hub/apps/publish/organizational-licensing.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -description: You can indicate whether and how your app can be offered for volume purchases through the Microsoft Store for Business and Microsoft Store for Education in the Organizational licensing section of an app submission. -title: Organizational licensing options -ms.assetid: 1EB139B0-67E7-4F66-AAEF-491B1E52E96F -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp, store for business, store for education, organizational, volume licensing, enterprise, education store, business store, volume purchase, bulk -localizationpriority: high - ---- - -# Organizational licensing options - -You can indicate whether and how your app can be offered for volume purchases through Microsoft Store for Business and Microsoft Store for Education in the **Organizational licensing** section of the [Pricing and availability](publish-your-app/msix/price-and-availability.md#organizational-licensing) page of an app submission. - -Through these settings, you can opt to allow your app to be made available to organizations (business and educational) who acquire and deploy multiple licenses for their users, providing an opportunity to increase your reach to organizations across Windows 10 device types, including PCs, tablets and phones. - -You will also need to allow organizational licensing for any [line-of-business (LOB) apps](distribute-lob-apps-to-enterprises.md) that you publish directly to enterprises. - -> [!NOTE] -> Selections for each of your apps are configured independently from each other. You may change your preferences for an app at any time by creating a new submission, and your changes will take effect after the submission completes the [certification process](publish-your-app/msix/app-certification-process.md). - -> [!IMPORTANT] -> Submissions that use the [Microsoft Store submission API](/windows/uwp/monetize/create-and-manage-submissions-using-windows-store-services) won't be made available to Microsoft Store for Business and Microsoft Store for Education. To make your app available for volume purchases by organizations, you must create and submit your submissions in Partner Center. - - -## Allowing your app to be offered to organizations - -By default, the box labeled **Make my app available to organizations with Store-managed (online) licensing and distribution** is checked. This means that you wish your app to be available for inclusion in catalogs of apps that will be made available to organizations for volume acquisition, with app licenses managed through the Store's online licensing system. - -> [!NOTE] -> This does not guarantee that your app will be made available to all organizations. - -If you prefer not to allow us to offer your app to organizations for volume acquisition, uncheck this box. Note that this change will only take place after the app completes the certification process. If any organizations had previously acquired licenses to your app, those licenses will still be valid, and the people who have the app already can continue to use it. - -> [!TIP] -> To publish line-of-business (LOB) apps exclusively to a specific organization, you can set up an enterprise association and allow the organization to add the apps directly their private store. For more info, see [Distribute LOB apps to enterprises](distribute-lob-apps-to-enterprises.md). - - -## Allowing disconnected (offline) licensing - -Many organizations need apps enabled for offline licensing. For example, some organizations need to deploy apps to devices which rarely or never connect to the internet. If you want to allow your app to be made available to these customers, check the box labeled **Allow organization-managed (offline) licensing and distribution for organizations**. - -Note that this box is **unchecked** by default. You must check the box to allow us to make your app available to verified organizations who will install it using organization-managed (offline) licensing. Organizations must go through additional validation in order to install paid apps to their end users in this way. - -Offline licensing allows organizations to acquire your app on a volume basis, and then install the app without requiring each device to contact the Store's licensing system. The organization is able to download your app's package along with a license which lets them install it to devices (via their own management tools or by preloading apps on OS images) without notifying the Store when a particular license has been used. Enabling this scenario greatly increases deployment flexibility, and it may substantially increase the attractiveness of your app with these customers. - -> [!IMPORTANT] -> Offline licensing is not supported for .xap packages. - - -## Paid app support - -Currently, developer accounts located in certain markets are able to offer paid apps for volume acquisition through Microsoft Store for Business. - -> [!NOTE] -> In some markets, the price shown for an app in Microsoft Store for Business or Microsoft Store for Education may be different than the price shown to retail customers in the Microsoft Store for the same price tier. Payout of proceeds from organizational purchases works just the same as it does for consumer purchases of your app. For more info, see [Getting paid](/partner-center/marketplace-get-paid) and the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905). For a list of markets where Microsoft Store for Business and Microsoft Store for Education are available, see [Microsoft Store for Business and Microsoft Store for Education overview](/windows/manage/windows-store-for-business-overview#supported-markets). - -If your country or region is not listed below, your paid apps currently will not be offered in Microsoft Store for Business and Microsoft Store for Education. If this is the case, the organizational licensing selections you make for your paid apps may be applied at a later time, as we may add support for submissions from additional developer account markets in the future. - -At this time, developers located in the following countries and regions can distribute paid apps to organizational customers via Microsoft Store for Business and Microsoft Store for Education: - -- Austria -- Belgium -- Bulgaria -- Canada -- Croatia -- Cyprus -- Czechia -- Denmark -- Estonia -- Finland -- France -- Germany -- Greece -- Hungary -- Ireland -- Isle of Man -- Italy -- Latvia -- Liechtenstein -- Lithuania -- Luxembourg -- Malta -- Monaco -- Netherlands -- Norway -- Poland -- Portugal -- Romania -- Slovakia -- Slovenia -- Spain -- Sweden -- Switzerland -- United Kingdom -- United States diff --git a/hub/apps/publish/package-and-distribution.md b/hub/apps/publish/package-and-distribution.md new file mode 100644 index 0000000000..9a537731ce --- /dev/null +++ b/hub/apps/publish/package-and-distribution.md @@ -0,0 +1,296 @@ +--- +description: Details of how to package and distribute your app. +title: Package and distribution +ms.assetid: AC3A45E8-7BBD-44E9-B2D3-B74B7C9B2BC9 +ms.date: 10/30/2022 +ms.topic: article +keywords: windows 10, uwp +ms.localizationpriority: medium +--- +# Package and Distribution + +## Generate preinstall packages for OEMs + +If your developer account has been granted the appropriate permissions, you can generate and download preinstall packages so that an OEM can include your app in their OS image. Preinstall permissions are only enabled on developer accounts that are sponsored by OEMs. + +## Important preinstall policy & limitations + +Preinstall apps must be certified through [Partner Center](https://partner.microsoft.com/dashboard) to have the latest Store license so that they are able to connect to the Store and receive app updates. + +Any app that is preinstalled must be and remain free in all markets. + +## Generating preinstall packages + +Once an account has been enabled with preinstall permissions, complete the following steps: + +1. In Partner Center, navigate to the app that is to be preinstalled. +1. In the left navigation menu, expand **App management** and select **Current packages**. +1. In the **Request packages for OS preinstallation** section, select **Enable downloadable packages**. +1. In the confirmation dialog will, select **Enable**. +1. Find the package that you want to download and select the appropriate **Generate package** link. + + > [!NOTE] + > Generation time for preinstall packages will vary depending on the size of the package you have selected. You can leave this page and come back later, or you can leave the page open while your package is being generated. + +1. After the package has been generated, a link to **Download package** will appear. Select this link to download the .zip file. + +You can then provide the .zip file to the OEM for inclusion in their OS image. + +## Support + +If you have further questions about generating preinstall packages, please email . + +## Paid app support + +Currently, developer accounts located in certain markets are able to offer paid apps for volume acquisition through Microsoft Store for Business. + +> [!NOTE] +> In some markets, the price shown for an app in Microsoft Store for Business or Microsoft Store for Education may be different than the price shown to retail customers in the Microsoft Store for the same price tier. Payout of proceeds from organizational purchases works just the same as it does for consumer purchases of your app. For more info, see [Getting paid](/partner-center/marketplace-get-paid) and the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905). For a list of markets where Microsoft Store for Business and Microsoft Store for Education are available, see [Microsoft Store for Business and Microsoft Store for Education overview](/windows/manage/windows-store-for-business-overview#supported-markets). + +If your country or region is not listed below, your paid apps currently will not be offered in Microsoft Store for Business and Microsoft Store for Education. If this is the case, the organizational licensing selections you make for your paid apps may be applied at a later time, as we may add support for submissions from additional developer account markets in the future. + +At this time, developers located in the following countries and regions can distribute paid apps to organizational customers via Microsoft Store for Business and Microsoft Store for Education: + +- Austria +- Belgium +- Bulgaria +- Canada +- Croatia +- Cyprus +- Czechia +- Denmark +- Estonia +- Finland +- France +- Germany +- Greece +- Hungary +- Ireland +- Isle of Man +- Italy +- Latvia +- Liechtenstein +- Lithuania +- Luxembourg +- Malta +- Monaco +- Netherlands +- Norway +- Poland +- Portugal +- Romania +- Slovakia +- Slovenia +- Spain +- Sweden +- Switzerland +- United Kingdom +- United States + +## Package flights + +You can use package flights to distribute specific packages to a limited group of testers. The packages you've already published to the Store will be used for your other customers, so their experience won't be disrupted. + +With package flights, only the packages are different; the Store listing details will be the same for all of your customers. Anyone in your flight group will receive the packages that you include in the package flight, while customers who aren't in the flight group continue to receive your regular (non-flighted) packages. If you later decide that you want to make packages from a package flight available to all your customers, you can easily use those same packages in a non-flighted submission. + +Note that the [certification process](publish-your-app/msix/app-certification-process.md) is applied to package flights just the same as any submission, however some WACK failures are reported as **passing with notes** and will allow submission for flighting. This relaxation of the WACK checks is only while the package is flighting to a limited audience and is intended to assist with package testing and preparation for release. WACK failures must be fixed before general release. + +When you set up package flights, you can specify the people who should get specific packages by adding them to a **known user group** (sometimes referred to as flight group). Anyone in a flight group who is using a device running a version of Windows 10 or Windows 11 that supports package flights (Windows.Desktop build 10586 or later; or Xbox One) will get the packages from the package flight(s) that you designate for that particular group. Anyone who has not been added to one of your flight groups, or is using a device that doesn’t support package flights, will get packages from the non-flighted submission. + +> [!IMPORTANT] +> On desktop devices, people in your flight groups will get the packages in your flight automatically whenever you provide updates. However, **people in your flight groups who are using Xbox devices will need to check for updates manually** in order to get the latest packages, making sure they are signed into their device using their Microsoft account (with the associated email address that you included in your known user group). + +Note that package flights will not be distributed via [Microsoft Store for Business](https://businessstore.microsoft.com/store) and [Microsoft Store for Education](https://educationstore.microsoft.com/store). This is because people in your known user groups must be signed in with their Microsoft accounts in order to receive a package flight. All acquisitions made via Microsoft Store for Business or Microsoft Store for Education will receive your non-flighted packages. + +> [!TIP] +> Package flights offer packages only to the selected customers that you specify. To distribute packages to a random selection of customers in a specified percentage, you can use [gradual package rollout](#gradual-package-rollout). You can also combine rollout with your package flights if you want to gradually distribute an update to one of your flight groups. +> +> Unlike package flights, your gradual package rollout selections do apply to customers who acquire your app via Microsoft Store for Business and Microsoft Store for Education. + +> [!TIP] +> Consider how the people in your package flight will be able to give their input about the app. We suggest [adding a control into your app to launch Feedback Hub](/windows/uwp/monetize/launch-feedback-hub-from-your-app) so that customers can provide their input directly; you can then review their feedback in your app's [Feedback report](feedback-report.md)). + + +## Create a new package flight + +After you have published a submission for your app, you'll see a **Package flights** section on the App overview page. Click **New package flight** to get started. + +If you haven't created any known user groups yet, you'll be prompted to create one before you can proceed. For more info, see [Create known user groups](create-customer-groups.md#create-known-user-groups). You can create a new known user group directly from this page by selecting **Create a flight group**. + +On the package flight creation page, you'll need to enter a name for your flight and specify at least one flight group. Once you've done so, select **Create flight**. You won't be able to change these details later (though if you're not happy with what you've entered, you can delete this flight and create a new one to use instead). + +> [!NOTE] +> If you have more than one package flight, you'll need to assign a rank to each one. For more info, see [Add and rank additional package flights](#add-and-rank-additional-package-flights) below. + + +## Specify packages to include in your package flight + +After you've saved your package flight details, you'll see its overview page. Click **Packages** to specify the packages you'd like to include in the flight. You can include packages targeting any OS version that your app supports. + +You have the option to select packages that were associated with a previous published submission (either a non-flighted submission, or one of your other package flights, if you have more than one). If you need to upload new packages to use for this package flight, you can upload them here (using the [same process as when you upload app packages to a regular non-flighted submission](publish-your-app/msix/upload-app-packages.md)). Click **Save** when you have finished specifying the packages to be included in this package flight. + +If your app supports multiple device families, make sure you include packages to support the same set of device families in your flight. People in your flight groups will **only** be able to get packages from that flight. They won't be able to access packages from other flights, or from your non-flighted submission. + +Also remember that your Store listing info and device family availability is based on your non-flighted submission. Customers in your flight groups will only be able to download the app on a device family that is supported by your non-flighted submission. For more info, see [Device family support](#device-family-support). + +## Configure additional package flight options + +By default, your package flight will be published and made available to your flight group as soon as it completes the certification process. If you'd like to change the [publish date](publish-your-app/msix/price-and-availability.md#publish-date), you can do so in the **Flight options** section. Click **Save** to return to the package flight overview page. + + +## Submit your package flight to the Store + +When you've specified packages and configured any options needed, click **Submit to the Store**. Your package flight will then go through the [app certification process](publish-your-app/msix/app-certification-process.md). + +Note that the [certification process](publish-your-app/msix/app-certification-process.md) is applied to package flights just the same as any submission, however some WACK failures are reported as **passing with notes** and will allow submission for flighting. This relaxation of the WACK checks is only while the package is flighting to a limited audience and is intended to assist with package testing and preparation for release. WACK failures must be fixed before general release. + +People in your flight group(s) associated with that package flight who already have your app will now get an update using the packages you included in your package flight. If those people don’t have your app yet, they’ll get the packages from your package flight when they install it. + +> [!NOTE] +> People who have a package that is only available in a package flight can give the app a star rating and leave reviews, but their ratings and reviews won’t be shown to other customers. You can see ratings and feedback from all customers, including those in your flight groups, in the **Reviews** and **Feedback** reports for the app. + + +## Device family support + +In most cases, you’ll want to include packages that support the same set of device families supported by your non-flighted submission. Device family availability for an app will always be based on the non-flighted submission, whether or not a customer is in a flight group. + +**If your non-flighted submission supports a device family that your package flight doesn’t support**, people in your flight group won’t be able to download the app on that device family. + +**If your package flight supports a device family that your non-flighted submission doesn’t support**, no one will be able to download the app on that device family, whether they’re in your flight group or not. For the best experience for all of your app’s customers, your non-flighted submission should support the same device families as your package flight. + +> [!NOTE] +> Packages added to your package flights can support any OS version (or any build of Windows 10 or Windows 11), but as noted above, people in flight groups running Windows 10 must be using a device running a version that supports package flights (Windows.Desktop build 10586 or laterr) in order to get packages from the package flight. + + +## Update or modify your package flight + +To create a new submission for a package flight you've already published, click **Update** next to the flight name on your App overview page. You can then upload new packages (and remove unneeded packages), just as you would with a non-flighted submission. Make any other needed changes, and then click **Submit to the Store** to send the updated package flight through the [app certification process](publish-your-app/msix/app-certification-process.md). + +To modify an existing flight without creating and submitting a new update, click **Modify** next to the flight name. This lets you change details such as the flight groups, name, and rank, without requiring that the package flight go through the certification process again. Note that if you have an update in progress, or if your package flight hasn’t been published yet, you won’t see the **Modify** option. + + +## Add and rank additional package flights + +You can create multiple package flights for the same app in order to distribute several different packages to different sets of customers. + +Once you have created your first package flight, you create another by following the process outlined above. The only difference is that if you've already created one package flight, you'll need to specify the priority order of all package flights in the **Rank** section. This lets the Store determine which package to give to any individual customer if they are in more than one of your flight groups. People in your flight groups will always get the highest-ranked package flight available to them, even if a lower-ranked package flight contains packages with a higher version number. + +By default, your new package flight will be ranked highest. If you'd like to change its rank, you can move it down (or back up) to place it in the right location among your other package flights. + +Note that your non-flighted submission is always ranked the lowest (#1). That is, people who aren’t in any of your flight groups can only get packages from your non-flighted submission through the Store. People in a flight group will always get packages from the highest-ranked package flight available to them (but never the non-flighted submission, since it has the lowest rank). This gives you flexibility in determining how to distribute your packages to people who may be members of more than one of your flight groups. + +For example, let's say you want to create two package flights in addition to your regular non-flighted submission: one that is relatively stable and ready for testing with a wide audience, and one that you're not so sure about and want to limit to only a few testers. You could create a flight group called Testers and include it in a package flight called Tester Flight, then create a flight group called Enthusiasts with a larger membership and include it in another package flight called Enthusiast Flight. If you rank Tester Flight higher than Enthusiast Flight, you can use packages that you're fairly confident about in Enthusiast Flight, while using riskier packages meant for Testers only in Tester Flight. Members of your Testers group will always get the packages you provide in Tester Flight, even if they also belong to your Enthusiasts group. (Then later, if it turns out that the packages in Tester Flight are performing well, you could update Enthusiast Flight to use the packages originally distributed to Tester Flight—and maybe eventually use those packages in your non-flighted submission.) + + +## Make packages from a package flight available to all your customers + +If you decide that one or more of the packages you included in a published package flight should be made available to customers who aren’t in a flight group, you can update your non-flighted submission to use those packages, without having to upload the same packages all over again. + +When you create your new submission, on the [**Packages**](publish-your-app/msix/upload-app-packages.md) page you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in the non-flighted submission. + +Note that all of the same package validation rules will apply, even when using packages from a previously published submission. + + +## Delete a package flight + +To delete a package flight that you no longer want to support, click its name from the App overview page. On the flight overview page, click **Modify**, then click the **Delete** link to delete the package flight. (If you have an unpublished submission of the package flight in progress, you’ll need to delete that submission first.) It may take up to 30 minutes for this to be completed. + +When you delete a package flight, any customers who have the packages you distributed in that package flight will get an app update if there is a package with a higher version number (or as soon as such a package becomes available). If they uninstall the app and then install it again later, this will be treated as a new acquisition, and they'll get the highest version currently available. + +## Gradual package rollout + +When you publish an update to a submission, you can choose to gradually roll out the updated packages to a percentage of customers who have your package installed on Windows 10 or Windows 11 (including Xbox). This allows you to monitor feedback and analytic data for the specific packages to make sure you’re confident about the update before rolling it out more broadly. You can increase the percentage (or halt the update) any time without having to create a new submission. + +> [!IMPORTANT] +> Your rollout selections apply to all of your packages, but will only apply to your customers running OS versions that support package flights (Windows.Desktop build 10586 or later and Xbox). When using gradual package rollout, customers on earlier OS versions will not get packages from the latest submission until you finalize the package rollout as described below. + +Note that all of your customers will see the Store listing details that you entered with your latest submission. The rollout settings only apply to the packages that customers install, for updates to existing customers. + +> [!TIP] +> Package rollout distributes packages to a random selection of customers who have your package installed +in the percentages that you specify. To distribute specific packages to selected customers that you specify, you can use package flights. You can also combine rollout with your package flights if you want to gradually distribute an update to one of your flight groups. + + +## Setting the rollout percentage + +You can select to roll out your update on the **Packages** page of an updated submission. To do so, check the box that says **Roll out update gradually after this submission is published (to Windows 10 or Windows 11 customers only)**. Then enter the percentage of customers who should get the update when the submission is first published. For example, you might enter 5 if you want to start by rolling the update out to only a small percentage of your app’s existing customers who have already installed this app. + +Click **Update** to save your selections. After your app completes the certification process, the packages will be distributed to existing customers according to the percentage that you specified for updates. + + +## Adjusting the rollout after the submission is published + +To adjust the rollout after the submission has been published, go to your app’s Overview page. You can drag the selector to change the percentage of customers getting the packages from your newest submission. Click **Update** to save your selections. The packages will then start to be distributed to existing customers who have your package installed according to the percentage that you specified for updates. + + +## Completing the rollout + +Before you can create a new submission, you'll need to complete the package rollout. You can **finalize** the rollout and distribute the latest packages to all of your customers, or **halt** the rollout to stop distributing the latest packages. + +If you have confidence in the update and would like to make it available to all of your customers, click **Finalize package rollout** to distribute the newest packages to all of your customers. + +> [!TIP] +> Changing the rollout percentage to 100% does not ensure that all of your customers will get the packages from the latest submissions, because some customers may be on OS versions that don’t support rollout. You must finalize the rollout in order to stop distributing the older packages and update all existing customers to the newer ones. + +If you find that there are problems with the update and you don’t want to distribute it any further, you can click **Halt package rollout** to stop distributing packages from the latest submission. Once you halt a package rollout, those packages will no longer be distributed to any customers; only the packages from the previous submission will be used for any new or updating customers. However, any customers who already had the newer packages will keep those packages; they won’t be rolled back to the previous version. To provide an update to these customers, you’ll need to create a new submission with the packages you’d like them to get. Note that if you use a gradual rollout in your next submission, customers who had the package you halted will be offered the new update in the same order they were offered the halted package. The new rollout will be between your last finalized submission and your newest submission; once you halt a package rollout, those packages will no longer be distributed to any customers. + +## Beta testing and targeted distribution + +No matter how carefully you test your app, there’s nothing like the real-world test of having other people use it. Your testers may discover issues that you’ve overlooked, such as misspellings, confusing app flow, or errors that could cause the app to crash. You’ll then have a chance to fix those problems before you release the submission to the public, resulting in a more polished final product. + +Partner Center gives you several options to let testers try out your app before you offer it to the public. + +Whichever method you choose, here are some things to keep in mind as you beta test your app. + +- You can’t revoke access to the app after a tester has downloaded it. Once they have downloaded the app, they can continue to use it, and they’ll get any updates that you subsequently publish. +- You will need to determine how you’d like to collect feedback from your testers. Consider providing a link that lets your testers easily give feedback via email (or via [Feedback Hub](/windows/uwp/monetize/launch-feedback-hub-from-your-app), if confidentiality is not a concern). +- You can review [analytic reports](analytics.md) for your app, including usage and health reports and any ratings or reviews left by your testers. +- You can include add-ons when you distribute your app to testers. Since you probably don’t want to charge them money for an add-on, you can [generate promotional codes](generate-promotional-codes.md) and distribute them to your testers to let them get the add-on for free, or you can set the price for the add-on to **Free** during testing (then before you make the app available to other customers, create a new submission for the add-on to change its price). Note that each add-on can only be purchased once per Microsoft account, so the same tester won't be able to test the add-on acquisition process more than one time. +- You can give your testers an updated version of your app at any time by creating a new submission with new packages. Your testers will get the update after it goes through the certification process, just like they got the original package, but no one else will be able to get it (unless you make additional changes, such as moving an app from **Private audience** to **Public audience** or changing the membership of groups who can get it). + +## Private audience + +If you want to let testers use your app before it’s available to others, and make sure that no one else can see its listing, use the **Private audience** option under [Visibility](publish-your-app/msix/visibility-options.md) (on the **Pricing and availability** page of your submission). This is the only method that lets you distribute your app to testers while completely preventing anyone else from seeing the app’s Store listing, even if they were able to type in its direct link. + +The **Private audience** option can only be used when you have not already published your app to a public audience. You can use this option with apps targeting any OS version, but your testers must be running Windows 10, version 1607 or later (including Xbox), and must be signed in with the Microsoft account associated with the email address that you provide. + +For more info, see [Private audience](publish-your-app/msix/visibility-options.md#audience). + +## Hiding the app in the Store and using promotional codes + +This option offers another way to limit distribution of an app to only a certain group of testers, while preventing anyone else from discovering your app in the Store (or acquiring it without a promotional code). However, unlike the private audience option, it could be possible for anyone to see your app’s listing if they have the direct link. If confidentiality is critical for your submission, we recommend publishing to a private audience instead. + +Hiding the app and using promotional codes can be used with apps targeting any OS version, but your testers can only get the app if they are running Windows 10 or Windows 11. + +To use this option: + +- In the **Visibility** section of the **Pricing and availability** page, under [Discoverability](publish-your-app/msix/visibility-options.md#discoverability), select **Make this product available but not discoverable in the Store**. Choose the option for **Stop acquisition: Any customer with a direct link can see the product’s Store listing, but they can only download it if they owned the product before, or have a promotional code and are using a Windows 10 or Windows 11 device**. +- After the app passes certification, [generate promotional codes](generate-promotional-codes.md) for the app and distribute them to your testers. You can generate codes that allow up to 1600 redemptions for a single app in a six month period. These codes will give your testers a direct link to the app’s listing, and will allow them to download it for free, even if you have set a price for it when you created your submission. +- When you're ready to make your app available to the public, create a new submission and change the **Visibility** option to **Make this product available and discoverable in the Store** (along with any other changes you'd like). + + +## Targeted distribution with a link to your app's listing + +With this, no customers will be able to find the app by searching or browsing the Store, but anyone with the direct link to its Store listing can download it on a device running on Windows 10 or Windows 11. Keep in mind that in order for your testers to download the app at no cost, you must set its price to **Free**. + +To use this option: +- In the **Visibility** section of the **Pricing and availability** page, under [Discoverability](publish-your-app/msix/visibility-options.md#discoverability), select **Make this product available but not discoverable in the Store**. Choose the option for **Direct link only: Any customer with a direct link to the product’s listing can download it, except on Windows 8.x.**. +- After your product has been published, distribute the link (the **URL** on the [App identity page](view-app-identity-details.md)) to your testers so they can try it out. +- When you're ready to make your app available to the public, create a new submission and change the **Visibility** option to **Make this product available and discoverable in the Store** (along with any other changes you'd like). + +## Microsoft Endpoint Configuration Manager and Microsoft Intune + +If your organization uses Microsoft Endpoint Configuration Manager or Microsoft Intune to manage devices, you can deploy LOB apps using these tools. For more information, see these articles: + +* [Introduction to application management in Configuration Manager](/configmgr/apps/understand/introduction-to-application-management) +* [Overview of the app lifecycle in Microsoft Intune](/intune/apps/app-lifecycle) + +## App Installer + +App Installer enables Windows 10 or Windows 11 apps to be installed by double-clicking an MSIX app package directly, or by double-clicking an .appinstaller file that installs the app package from a web server. This means that users don't need to use PowerShell or other developer tools to install LOB apps. App Installer can also install app packages that include optional packages and related sets. + +App Installer can be downloaded for offline use in the enterprise from Microsoft Store for Business [web portal](https://businessstore.microsoft.com/store/details/app-installer/9NBLGGH4NNS1). For more information about App Installer, see [Install Windows 10 or Windows 11 apps with App Installer](/windows/msix/app-installer/app-installer-root). + +## Sideloading + +Another option for distributing LOB apps directly to users in your organization is sideloading. This option is similar to App Install-based deployment in that it enables users to install MSIX app packages directly. Starting in Windows 10 version 2004, sideloading is enabled by default and users can install apps by double-clicking signed MSIX app packages. On Windows 10 version 1909 and earlier, sideloading requires some additional configuration and the use of a PowerShell script. For more info, see [Sideload LOB apps in Windows 10 or Windows 11](/windows/application-management/sideload-apps-in-windows-10). diff --git a/hub/apps/publish/package-flights.md b/hub/apps/publish/package-flights.md deleted file mode 100644 index 6a9c5d7263..0000000000 --- a/hub/apps/publish/package-flights.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -description: You can use package flights to distribute packages that are only given to a limited test group. -title: Package flights -ms.assetid: 5B094822-A8DE-4EE3-B55D-3E306C04EE79 -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp, flighting -ms.localizationpriority: medium ---- -# Package flights - -You can use package flights to distribute specific packages to a limited group of testers. The packages you've already published to the Store will be used for your other customers, so their experience won't be disrupted. - -With package flights, only the packages are different; the Store listing details will be the same for all of your customers. Anyone in your flight group will receive the packages that you include in the package flight, while customers who aren't in the flight group continue to receive your regular (non-flighted) packages. If you later decide that you want to make packages from a package flight available to all your customers, you can easily use those same packages in a non-flighted submission. - -Note that the [certification process](publish-your-app/msix/app-certification-process.md) is applied to package flights just the same as any submission, however some WACK failures are reported as **passing with notes** and will allow submission for flighting. This relaxation of the WACK checks is only while the package is flighting to a limited audience and is intended to assist with package testing and preparation for release. WACK failures must be fixed before general release. - -When you set up package flights, you can specify the people who should get specific packages by adding them to a **known user group** (sometimes referred to as flight group). Anyone in a flight group who is using a device running a version of Windows 10 or Windows 11 that supports package flights (Windows.Desktop build 10586 or later; or Xbox One) will get the packages from the package flight(s) that you designate for that particular group. Anyone who has not been added to one of your flight groups, or is using a device that doesn’t support package flights, will get packages from the non-flighted submission. - -> [!IMPORTANT] -> On desktop devices, people in your flight groups will get the packages in your flight automatically whenever you provide updates. However, **people in your flight groups who are using Xbox devices will need to check for updates manually** in order to get the latest packages, making sure they are signed into their device using their Microsoft account (with the associated email address that you included in your known user group). - -Note that package flights will not be distributed via [Microsoft Store for Business](https://businessstore.microsoft.com/store) and [Microsoft Store for Education](https://educationstore.microsoft.com/store). This is because people in your known user groups must be signed in with their Microsoft accounts in order to receive a package flight. All acquisitions made via Microsoft Store for Business or Microsoft Store for Education will receive your non-flighted packages. - -> [!TIP] -> Package flights offer packages only to the selected customers that you specify. To distribute packages to a random selection of customers in a specified percentage, you can use [gradual package rollout](gradual-package-rollout.md). You can also combine rollout with your package flights if you want to gradually distribute an update to one of your flight groups. -> -> Unlike package flights, your gradual package rollout selections do apply to customers who acquire your app via Microsoft Store for Business and Microsoft Store for Education. - -> [!TIP] -> Consider how the people in your package flight will be able to give their input about the app. We suggest [adding a control into your app to launch Feedback Hub](/windows/uwp/monetize/launch-feedback-hub-from-your-app) so that customers can provide their input directly; you can then review their feedback in your app's [Feedback report](feedback-report.md)). - - -## Create a new package flight - -After you have published a submission for your app, you'll see a **Package flights** section on the App overview page. Click **New package flight** to get started. - -If you haven't created any known user groups yet, you'll be prompted to create one before you can proceed. For more info, see [Create known user groups](create-known-user-groups.md). You can create a new known user group directly from this page by selecting **Create a flight group**. - -On the package flight creation page, you'll need to enter a name for your flight and specify at least one flight group. Once you've done so, select **Create flight**. You won't be able to change these details later (though if you're not happy with what you've entered, you can delete this flight and create a new one to use instead). - -> [!NOTE] -> If you have more than one package flight, you'll need to assign a rank to each one. For more info, see [Add and rank additional package flights](#add-and-rank-additional-package-flights) below. - - -## Specify packages to include in your package flight - -After you've saved your package flight details, you'll see its overview page. Click **Packages** to specify the packages you'd like to include in the flight. You can include packages targeting any OS version that your app supports. - -You have the option to select packages that were associated with a previous published submission (either a non-flighted submission, or one of your other package flights, if you have more than one). If you need to upload new packages to use for this package flight, you can upload them here (using the [same process as when you upload app packages to a regular non-flighted submission](publish-your-app/msix/upload-app-packages.md)). Click **Save** when you have finished specifying the packages to be included in this package flight. - -If your app supports multiple device families, make sure you include packages to support the same set of device families in your flight. People in your flight groups will **only** be able to get packages from that flight. They won't be able to access packages from other flights, or from your non-flighted submission. - -Also remember that your Store listing info and device family availability is based on your non-flighted submission. Customers in your flight groups will only be able to download the app on a device family that is supported by your non-flighted submission. For more info, see [Device family support](#device-family-support). - - -## Gradual package rollout - -By default, the packages in your submission will be made available to everyone in your flight group at the same time. To change this, you can check the box that says **Roll out update gradually after this submission is published (to Windows 10 or Windows 11 customers only)**. You can choose a percentage of people in your flight group to get the packages from the new submission, so that you can monitor feedback and analytic data to make sure you’re confident about the update before rolling it out more broadly to the rest of the flight group. You can increase the percentage (or halt the update) any time without having to create a new submission for your package flight. - -> [!IMPORTANT] -> When gradually rolling out packages in a package flight, the people who aren't included in the percentage that gets your new packages will get the packages from the previous package flight submission (unless there is a higher-ranked flight available to them). - -For more info, see [Gradual package rollout](gradual-package-rollout.md). - - -## Configure additional package flight options - -By default, your package flight will be published and made available to your flight group as soon as it completes the certification process. If you'd like to change the [publish date](publish-your-app/msix/price-and-availability.md#publish-date), you can do so in the **Flight options** section. Click **Save** to return to the package flight overview page. - - -## Submit your package flight to the Store - -When you've specified packages and configured any options needed, click **Submit to the Store**. Your package flight will then go through the [app certification process](publish-your-app/msix/app-certification-process.md). - -Note that the [certification process](publish-your-app/msix/app-certification-process.md) is applied to package flights just the same as any submission, however some WACK failures are reported as **passing with notes** and will allow submission for flighting. This relaxation of the WACK checks is only while the package is flighting to a limited audience and is intended to assist with package testing and preparation for release. WACK failures must be fixed before general release. - -People in your flight group(s) associated with that package flight who already have your app will now get an update using the packages you included in your package flight. If those people don’t have your app yet, they’ll get the packages from your package flight when they install it. - -> [!NOTE] -> People who have a package that is only available in a package flight can give the app a star rating and leave reviews, but their ratings and reviews won’t be shown to other customers. You can see ratings and feedback from all customers, including those in your flight groups, in the **Reviews** and **Feedback** reports for the app. - - -## Device family support - -In most cases, you’ll want to include packages that support the same set of device families supported by your non-flighted submission. Device family availability for an app will always be based on the non-flighted submission, whether or not a customer is in a flight group. - -**If your non-flighted submission supports a device family that your package flight doesn’t support**, people in your flight group won’t be able to download the app on that device family. - -**If your package flight supports a device family that your non-flighted submission doesn’t support**, no one will be able to download the app on that device family, whether they’re in your flight group or not. For the best experience for all of your app’s customers, your non-flighted submission should support the same device families as your package flight. - -> [!NOTE] -> Packages added to your package flights can support any OS version (or any build of Windows 10 or Windows 11), but as noted above, people in flight groups running Windows 10 must be using a device running a version that supports package flights (Windows.Desktop build 10586 or laterr) in order to get packages from the package flight. - - -## Update or modify your package flight - -To create a new submission for a package flight you've already published, click **Update** next to the flight name on your App overview page. You can then upload new packages (and remove unneeded packages), just as you would with a non-flighted submission. Make any other needed changes, and then click **Submit to the Store** to send the updated package flight through the [app certification process](publish-your-app/msix/app-certification-process.md). - -To modify an existing flight without creating and submitting a new update, click **Modify** next to the flight name. This lets you change details such as the flight groups, name, and rank, without requiring that the package flight go through the certification process again. Note that if you have an update in progress, or if your package flight hasn’t been published yet, you won’t see the **Modify** option. - - -## Add and rank additional package flights - -You can create multiple package flights for the same app in order to distribute several different packages to different sets of customers. - -Once you have created your first package flight, you create another by following the process outlined above. The only difference is that if you've already created one package flight, you'll need to specify the priority order of all package flights in the **Rank** section. This lets the Store determine which package to give to any individual customer if they are in more than one of your flight groups. People in your flight groups will always get the highest-ranked package flight available to them, even if a lower-ranked package flight contains packages with a higher version number. - -By default, your new package flight will be ranked highest. If you'd like to change its rank, you can move it down (or back up) to place it in the right location among your other package flights. - -Note that your non-flighted submission is always ranked the lowest (#1). That is, people who aren’t in any of your flight groups can only get packages from your non-flighted submission through the Store. People in a flight group will always get packages from the highest-ranked package flight available to them (but never the non-flighted submission, since it has the lowest rank). This gives you flexibility in determining how to distribute your packages to people who may be members of more than one of your flight groups. - -For example, let's say you want to create two package flights in addition to your regular non-flighted submission: one that is relatively stable and ready for testing with a wide audience, and one that you're not so sure about and want to limit to only a few testers. You could create a flight group called Testers and include it in a package flight called Tester Flight, then create a flight group called Enthusiasts with a larger membership and include it in another package flight called Enthusiast Flight. If you rank Tester Flight higher than Enthusiast Flight, you can use packages that you're fairly confident about in Enthusiast Flight, while using riskier packages meant for Testers only in Tester Flight. Members of your Testers group will always get the packages you provide in Tester Flight, even if they also belong to your Enthusiasts group. (Then later, if it turns out that the packages in Tester Flight are performing well, you could update Enthusiast Flight to use the packages originally distributed to Tester Flight—and maybe eventually use those packages in your non-flighted submission.) - - -## Make packages from a package flight available to all your customers - -If you decide that one or more of the packages you included in a published package flight should be made available to customers who aren’t in a flight group, you can update your non-flighted submission to use those packages, without having to upload the same packages all over again. - -When you create your new submission, on the [**Packages**](publish-your-app/msix/upload-app-packages.md) page you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in the non-flighted submission. - -Note that all of the same package validation rules will apply, even when using packages from a previously published submission. - - -## Delete a package flight - -To delete a package flight that you no longer want to support, click its name from the App overview page. On the flight overview page, click **Modify**, then click the **Delete** link to delete the package flight. (If you have an unpublished submission of the package flight in progress, you’ll need to delete that submission first.) It may take up to 30 minutes for this to be completed. - -When you delete a package flight, any customers who have the packages you distributed in that package flight will get an app update if there is a package with a higher version number (or as soon as such a package becomes available). If they uninstall the app and then install it again later, this will be treated as a new acquisition, and they'll get the highest version currently available. diff --git a/hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md b/hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md index eb84eab13d..e2c7ba0c5a 100644 --- a/hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md +++ b/hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md @@ -41,9 +41,7 @@ Note that some permissions cannot be set for add-ons. This is either because the | **Permission name** | **Read only** | **Read/write** | **Read only (Add‑on)** | **Read‑write (Add‑on)** | | ---------- | ---------- | ---------- |----------|----------| | **Promotional codes** | Can view promotional code orders and usage info for the product and its add-ons, and can view usage info. | Can view, manage, and create promotional code orders for the product and its add-ons, and can view usage info. | N/A (settings for parent product apply to all add-ons) | N/A (settings for parent product apply to all add-ons) | -| **Targeted offers** | Can view targeted offers for the product. | Can view, manage and create targeted offers for the product. | N/A | N/A | -| **Contact customer** | Can view responses to customer feedback and responses to customer reviews, as long as the **Customer feedback** permission has been granted as well. Can also view targeted notifications that have been created for the product. | Can respond to customer feedback and respond to customer reviews, as long as the **Customer feedback** permission has been granted as well. Can also create and send targeted notifications for the product. | N/A | N/A | -| **Experimentation** | Can view experiments (A/B testing) and view experimentation data for the product. | Can create, manage, and view experiments (A/B testing) for the product, and view experimentation data. | N/A | N/A | +| **Targeted offers** | Can view targeted offers for the product. | Can view, manage and create targeted offers for the product. | N/A | N/A |\ | **Store sale events** *| Can view sale event status for the product. | Can add the product to sale events and configure discounts. | Can view sale event status for the product. |Can add the product to sale events and configure discounts. | ## Publishing diff --git a/hub/apps/publish/partner-center/assign-roles-to-account-users.md b/hub/apps/publish/partner-center/assign-roles-to-account-users.md index 2ae548905d..5e4ddbcfa7 100644 --- a/hub/apps/publish/partner-center/assign-roles-to-account-users.md +++ b/hub/apps/publish/partner-center/assign-roles-to-account-users.md @@ -21,7 +21,7 @@ Unless you opt to define [custom permissions](overview-of-custom-permissions-for | Developer | Can upload packages and submit apps and add-ons, and can view the [Usage report](../usage-report.md) for telemetry details. Can access [Cross-Device Experiences](https://developer.microsoft.com/windows/project-rome) functionality. Can’t view financial info or account settings. | | Business Contributor | Can view [Health](../health-report.md) and [Usage](../usage-report.md) reports. Can't create or submit products, change account settings, or view financial info. | | Finance Contributor | Can view [payout reports](/partner-center/payout-statement), financial info, and acquisition reports. Can’t make any changes to apps, add-ons, or account settings. | -| Marketer | Can [respond to customer reviews](../respond-to-customer-reviews.md) and view non-financial [analytic reports](../analytics.md). Can’t make any changes to apps, add-ons, or account settings. | +| Marketer | Can view non-financial [analytic reports](../analytics.md). Can’t make any changes to apps, add-ons, or account settings. | The table below shows some of the specific features available to each of these roles (and to the account owner). diff --git a/hub/apps/publish/app-management-and-services.md b/hub/apps/publish/product-management.md similarity index 64% rename from hub/apps/publish/app-management-and-services.md rename to hub/apps/publish/product-management.md index 87716a6c67..92eb139e37 100644 --- a/hub/apps/publish/app-management-and-services.md +++ b/hub/apps/publish/product-management.md @@ -1,15 +1,15 @@ --- description: Manage and view details related to each of your apps in Partner Center, and configure services such as A/B testing and maps. -title: App management and services +title: Product management ms.assetid: 99DA2BC1-9B5D-4746-8BC0-EC723D516EEF ms.date: 10/30/2022 ms.topic: article keywords: windows 10, uwp ms.localizationpriority: medium --- -# App management and services +# Product Management -You can manage and view details related to each of your apps in [Partner Center](https://partner.microsoft.com/dashboard), and configure services such as notifications, A/B testing, and maps. +You can manage and view details related to each of your apps in [Partner Center](https://partner.microsoft.com/dashboard), and configure services such as notifications, and maps. When working with an app in Partner Center, you'll see sections in the left navigation menu for **Services** and **App management**. You can expand these sections to access the functionality described below. @@ -21,13 +21,7 @@ The **Services** section lets you manage several different services for your app If you are publishing a game, you can enable the [Xbox Live Creators Program](https://www.xbox.com/developers/creators-program) on this page. This lets you start configuring and testing Xbox Live features, and eventually publish your Xbox Live Creators Program game. -For more info, see [Get started with the Xbox Live Creators Program](/gaming/xbox-live/get-started-with-creators/get-started-with-xbox-live-creators) and [Create a new Xbox Live Creators Program title and publish to the test environment](/gaming/xbox-live/get-started-with-creators/create-and-test-a-new-creators-title). - -## Experimentation - -Use the **Experimentation** page to create and run experiments for your Universal Windows Platform (UWP) apps with A/B testing. In an A/B test, you measure the effectiveness of feature changes (or variations) in your app on some customers before you enable the changes for everyone. - -For more info, see [Run app experiments with A/B testing](/windows/uwp/monetize/run-app-experiments-with-a-b-testing). +For more info, see [Xbox services overview](/gaming/gdk/docs/services/fundamentals/live-xbl-overview). ## Maps @@ -70,18 +64,7 @@ This page lets you view details related to all of your published packages. The name, version, and architecture of each package is shown. Click **Details** to show additional info such as supported language, app capabilities, and file sizes. The info you see for each package may vary depending on its targeted operating system and other factors. -Developers with OEM permissions can also [generate preinstall packages](generate-preinstall-packages-for-oems.md) from the **Current packages** page. - -## WNS/MPNS - -The **WNS/MPNS** section provides options to help you create and send notifications to your app's customers. - -> [!TIP] -> For UWP apps, we suggest using the **Notifications** feature in Partner Center. This feature lets you send notifications to all of your app's customers, or to a targeted subset of your Windows 10 or Windows 11 customers who meet the criteria you’ve defined in a [customer segment](create-customer-segments.md). For more info, see [Send notifications to your app's customers](send-push-notifications-to-your-apps-customers.md). - -Depending on your app's package type and its specific requirements, you can also use one of the following options: - -- **Windows Push Notification Services (WNS)** lets you send toast, tile, badge, and raw updates from your own cloud service. For more info, see [Windows Push Notification Services (WNS) overview](/windows/apps/design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview). +Developers with OEM permissions can also [generate preinstall packages](package-and-distribution.md) from the **Current packages** page.   diff --git a/hub/apps/publish/product-page-experiments.md b/hub/apps/publish/product-page-experiments.md index 24a0f5daa8..1a92cba219 100644 --- a/hub/apps/publish/product-page-experiments.md +++ b/hub/apps/publish/product-page-experiments.md @@ -13,7 +13,7 @@ Icons and screenshots occupy up to 50% of the surface area on a Microsoft Store To conduct a product page experiment, start by signing in to Partner Center and selecting your app. This new overview page in Partner Center consolidates all app actions and information in one place. The console also contextually prioritizes information cards based on your app's status. > [!NOTE] -> We are using the Goodnotes for Windows app in Microsoft Store as an example in the following images. +> We are using the Meerkat Photo Lab in Microsoft Store as an example in the following images. :::image type="content" source="publish-your-app/msix/images/submit-product-page-experiment.png" lightbox="publish-your-app/msix/images/submit-product-page-experiment.png" alt-text="A screenshot showing how to create product page experiment for your app from the application overview page."::: diff --git a/hub/apps/publish/publish-your-app/add-on/visibility-options.md b/hub/apps/publish/publish-your-app/add-on/visibility-options.md index 38dfb7ca2d..239deb965b 100644 --- a/hub/apps/publish/publish-your-app/add-on/visibility-options.md +++ b/hub/apps/publish/publish-your-app/add-on/visibility-options.md @@ -25,16 +25,16 @@ By default, your app’s Store listing will be visible to a **Public audience**. ### Private audience -If you want your app’s listing to be visible only to selected people that you specify, choose **Private audience**. With this option, the app will not be discoverable or available to anyone other than people in the group(s) you specify. This option is often used for [beta testing](../../beta-testing-and-targeted-distribution.md), as it lets you distribute your app to testers without anyone else being able to get the app, or even see its Store listing (even if they were able to type in its Store listing URL). +If you want your app’s listing to be visible only to selected people that you specify, choose **Private audience**. With this option, the app will not be discoverable or available to anyone other than people in the group(s) you specify. This option is often used for [beta testing](../../package-and-distribution.md), as it lets you distribute your app to testers without anyone else being able to get the app, or even see its Store listing (even if they were able to type in its Store listing URL). -When you choose **Private audience**, you’ll need to specify at least one group of people who should get your app. You can choose from an existing [known user group](../../create-known-user-groups.md), or you can select **Create a new group** to define a new group. You’ll need to enter the email addresses associated with the Microsoft account of each person you’d like to include in the group. For more info, see [Create known user groups](../../create-known-user-groups.md). +When you choose **Private audience**, you’ll need to specify at least one group of people who should get your app. You can choose from an existing [known user group](../../create-customer-groups.md#create-known-user-groups), or you can select **Create a new group** to define a new group. You’ll need to enter the email addresses associated with the Microsoft account of each person you’d like to include in the group. For more info, see [Create known user groups](../../create-customer-groups.md#create-known-user-groups). After your submission is published, the people in the group you specify will be able to view the app’s listing and download the app, as long as they are signed in with the Microsoft account associated with the email address that you entered and are running Windows 10, version 1607 or later (including Xbox One). However, people who aren’t in your private audience won’t be able to view the app’s listing or download the app, regardless of what OS version they’re running. You can publish updated submissions to the private audience, which will be distributed to members of those audience in the same way as a regular app update (but still won’t be available to anyone who’s not in of your private audience, unless you change your audience selection). If you plan to make the app available to a public audience at a certain date and time, you can select the box labeled **Make this product public on** when creating your submission. Enter the date and time (in UTC) when you’d like the product to become available to the public. Keep in mind the following: - The date and time that you select will apply to all markets. If you want to customize the release schedule for different markets, don’t use this box. Instead, create a new submission that changes your setting to **Public audience**, then use the [Schedule](./schedule-pricing-changes.md#configure-precise-release-scheduling) options to specify your release timing. -- Entering a date for **Make this product public on** does not apply to the Microsoft Store for Business and/or Microsoft Store for Education. To allow us to offer your app to these customers through organizational licensing, you’ll need to create a new submission with **Public audience** selected (and [organizational licensing](../../organizational-licensing.md) enabled). +- Entering a date for **Make this product public on** does not apply to the Microsoft Store for Business and/or Microsoft Store for Education. To allow us to offer your app to these customers through organizational licensing, you’ll need to create a new submission with **Public audience** selected. - After the date and time that you select, all future submissions will use **Public audience**. If you don’t specify a date and time to make your app available to a public audience, you can always do so later by creating a new submission and changing your audience setting from **Private audience** to **Public audience**. When you do so, keep in mind that your app may go through an additional certification process, so be prepared to address any new certification issues that may arise. @@ -45,7 +45,7 @@ Here are some important things to keep in mind when choosing to distribute your - Unless you choose an option in **Discoverability** that prevents it, people in your private audience will be able to find your app by searching within the Microsoft Store app. However, the web listing will not be discoverable via search, even to people in that audience. - You won’t be able to [configure release dates in the Schedule section](./schedule-pricing-changes.md#configure-precise-release-scheduling) of the **Pricing and availability page**, since your app won’t be released to customers outside of your private audience. - Other selections you make will apply to people in this audience. For example, if you choose a price other than **Free**, people in your private audience will have to pay that price in order to acquire the app. -- If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-flights.md) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight. +- If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-and-distribution.md#package-flights) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight. - You can edit the membership of the known user group(s) in your private audience. However, keep in mind that if you remove someone who was in the group and previously downloaded your app, they will still be able to use the app, but they won’t get any updates that you provide (unless you choose **Public audience** at a later date). - Your app won't be available through the Microsoft Store for Business and/or Microsoft Store for Education, regardless of your organizational licensing settings, even to people in your private audience. - While the Store will ensure that your app is only visible and available to people signed in with a Microsoft account that you’ve added to your private audience, we can’t prevent those people from sharing info or screenshots outside of your private audience. When confidentiality is critical, be sure that your private audience only includes people whom you trust not to share details about your app with others. diff --git a/hub/apps/publish/publish-your-app/msix/images/analyse-product-page-experiment-results.png b/hub/apps/publish/publish-your-app/msix/images/analyse-product-page-experiment-results.png index 5aea304284..73ee3d0e26 100644 Binary files a/hub/apps/publish/publish-your-app/msix/images/analyse-product-page-experiment-results.png and b/hub/apps/publish/publish-your-app/msix/images/analyse-product-page-experiment-results.png differ diff --git a/hub/apps/publish/publish-your-app/msix/images/configure-product-page-experiment.png b/hub/apps/publish/publish-your-app/msix/images/configure-product-page-experiment.png index 12195efc54..92a68e6738 100644 Binary files a/hub/apps/publish/publish-your-app/msix/images/configure-product-page-experiment.png and b/hub/apps/publish/publish-your-app/msix/images/configure-product-page-experiment.png differ diff --git a/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-in-certification.png b/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-in-certification.png index 9804f00396..6cfef84d41 100644 Binary files a/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-in-certification.png and b/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-in-certification.png differ diff --git a/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-live-in-store.png b/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-live-in-store.png index 80b545754b..554f3e2a08 100644 Binary files a/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-live-in-store.png and b/hub/apps/publish/publish-your-app/msix/images/product-page-experiment-live-in-store.png differ diff --git a/hub/apps/publish/publish-your-app/msix/images/submit-product-page-experiment.png b/hub/apps/publish/publish-your-app/msix/images/submit-product-page-experiment.png index 70245457a9..15912b95e2 100644 Binary files a/hub/apps/publish/publish-your-app/msix/images/submit-product-page-experiment.png and b/hub/apps/publish/publish-your-app/msix/images/submit-product-page-experiment.png differ diff --git a/hub/apps/publish/publish-your-app/msix/price-and-availability.md b/hub/apps/publish/publish-your-app/msix/price-and-availability.md index dd828ad1be..d609737479 100644 --- a/hub/apps/publish/publish-your-app/msix/price-and-availability.md +++ b/hub/apps/publish/publish-your-app/msix/price-and-availability.md @@ -77,12 +77,6 @@ If you want to offer your app at a reduced price for a limited period of time, y For more info, see [Put apps and add-ons on sale](../../put-apps-and-add-ons-on-sale.md). -## Organizational licensing - -By default, your app may be offered to organizations to purchase in volume. You can indicate whether and how your app can be offered in this section. - -For more info, see [Organizational licensing options](../../organizational-licensing.md). - ## Publish date Previously, the **Publish date** section appeared on this page. This functionality can now be found on the [Submission options](./manage-submission-options.md) page, in the **Publishing hold options** section. diff --git a/hub/apps/publish/publish-your-app/msix/upload-app-packages.md b/hub/apps/publish/publish-your-app/msix/upload-app-packages.md index 94f799ad79..21a3de394c 100644 --- a/hub/apps/publish/publish-your-app/msix/upload-app-packages.md +++ b/hub/apps/publish/publish-your-app/msix/upload-app-packages.md @@ -23,7 +23,7 @@ To upload packages, drag them into the upload field or click to browse your file > [!IMPORTANT] > For Windows 10 and above, we recommend uploading the .msixupload or .appxupload file here rather than .msix, .appx, .msixbundle, or .appxbundle. For more info about packaging UWP apps for the Store, see [Packaging a UWP app with Visual Studio](/windows/msix/package/packaging-uwp-apps). -If you have created any [package flights](../../package-flights.md) for your app, you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in this submission. +If you have created any [package flights](../../package-and-distribution.md#package-flights) for your app, you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in this submission. If we detect errors with a package while validating it, we'll display a message to let you know what's wrong. You'll need to remove the package, fix the issue, and then try uploading it again. You may also see warnings to let you know about issues that may cause problems but won't block you from continuing with your submission. @@ -43,7 +43,7 @@ When we detect that you have redundant packages, we'll provide an option to remo If your submission is an update to a previously published app, you'll see a checkbox that says **Roll out update gradually after this submission is published (to Windows 10 or Windows 11 customers only)**. This allows you to choose a percentage of customers who will get the packages from the submission so that you can monitor feedback and analytic data to make sure you’re confident about the update before rolling it out more broadly. You can increase the percentage (or halt the update) any time without having to create a new submission. -For more info, see [Gradual package rollout](../../gradual-package-rollout.md). +For more info, see [Gradual package rollout](../../package-and-distribution.md#gradual-package-rollout). ### Mandatory update diff --git a/hub/apps/publish/publish-your-app/msix/visibility-options.md b/hub/apps/publish/publish-your-app/msix/visibility-options.md index 4cec5ea9a5..2e4026a920 100644 --- a/hub/apps/publish/publish-your-app/msix/visibility-options.md +++ b/hub/apps/publish/publish-your-app/msix/visibility-options.md @@ -27,16 +27,16 @@ By default, your app’s Store listing will be visible to a **Public audience**. ### Private audience -If you want your app’s listing to be visible only to selected people that you specify, choose **Private audience**. With this option, the app will not be discoverable or available to anyone other than people in the group(s) you specify. This option is often used for [beta testing](../../beta-testing-and-targeted-distribution.md), as it lets you distribute your app to testers without anyone else being able to get the app, or even see its Store listing (even if they were able to type in its Store listing URL). +If you want your app’s listing to be visible only to selected people that you specify, choose **Private audience**. With this option, the app will not be discoverable or available to anyone other than people in the group(s) you specify. This option is often used for [beta testing](../../package-and-distribution.md#beta-testing-and-targeted-distribution), as it lets you distribute your app to testers without anyone else being able to get the app, or even see its Store listing (even if they were able to type in its Store listing URL). -When you choose **Private audience**, you’ll need to specify at least one group of people who should get your app. You can choose from an existing [known user group](../../create-known-user-groups.md), or you can select **Create a new group** to define a new group. You’ll need to enter the email addresses associated with the Microsoft account of each person you’d like to include in the group. For more info, see [Create known user groups](../../create-known-user-groups.md). +When you choose **Private audience**, you’ll need to specify at least one group of people who should get your app. You can choose from an existing [known user group](../../create-customer-groups.md#create-known-user-groups), or you can select **Create a new group** to define a new group. You’ll need to enter the email addresses associated with the Microsoft account of each person you’d like to include in the group. For more info, see [Create known user groups](../../create-customer-groups.md#create-known-user-groups). After your submission is published, the people in the group you specify will be able to view the app’s listing and download the app, as long as they are signed in with the Microsoft account associated with the email address that you entered and are running Windows 10, version 1607 or later (including Xbox One). However, people who aren’t in your private audience won’t be able to view the app’s listing or download the app, regardless of what OS version they’re running. You can publish updated submissions to the private audience, which will be distributed to members of those audience in the same way as a regular app update (but still won’t be available to anyone who’s not in of your private audience, unless you change your audience selection). If you plan to make the app available to a public audience at a certain date and time, you can select the box labeled **Make this product public on** when creating your submission. Enter the date and time (in UTC) when you’d like the product to become available to the public. Keep in mind the following: - The date and time that you select will apply to all markets. If you want to customize the release schedule for different markets, don’t use this box. Instead, create a new submission that changes your setting to **Public audience**, then use the [Schedule](./schedule-pricing-changes.md#configure-precise-release-scheduling) options to specify your release timing. -- Entering a date for **Make this product public on** does not apply to the Microsoft Store for Business and/or Microsoft Store for Education. To allow us to offer your app to these customers through organizational licensing, you’ll need to create a new submission with **Public audience** selected (and [organizational licensing](../../organizational-licensing.md) enabled). +- Entering a date for **Make this product public on** does not apply to the Microsoft Store for Business and/or Microsoft Store for Education. To allow us to offer your app to these customers through organizational licensing, you’ll need to create a new submission with **Public audience** selected. - After the date and time that you select, all future submissions will use **Public audience**. If you don’t specify a date and time to make your app available to a public audience, you can always do so later by creating a new submission and changing your audience setting from **Private audience** to **Public audience**. When you do so, keep in mind that your app may go through an additional certification process, so be prepared to address any new certification issues that may arise. @@ -47,9 +47,8 @@ Here are some important things to keep in mind when choosing to distribute your - Unless you choose an option in **Discoverability** that prevents it, people in your private audience will be able to find your app by searching within the Microsoft Store app. However, the web listing will not be discoverable via search, even to people in that audience. - You won’t be able to [configure release dates in the Schedule section](./schedule-pricing-changes.md#configure-precise-release-scheduling) of the **Pricing and availability page**, since your app won’t be released to customers outside of your private audience. - Other selections you make will apply to people in this audience. For example, if you choose a price other than **Free**, people in your private audience will have to pay that price in order to acquire the app. -- If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-flights.md) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight. +- If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-and-distribution.md#package-flights) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight. - You can edit the membership of the known user group(s) in your private audience. However, keep in mind that if you remove someone who was in the group and previously downloaded your app, they will still be able to use the app, but they won’t get any updates that you provide (unless you choose **Public audience** at a later date). -- Your app won't be available through the Microsoft Store for Business and/or Microsoft Store for Education, regardless of your organizational licensing settings, even to people in your private audience. - While the Store will ensure that your app is only visible and available to people signed in with a Microsoft account that you’ve added to your private audience, we can’t prevent those people from sharing info or screenshots outside of your private audience. When confidentiality is critical, be sure that your private audience only includes people whom you trust not to share details about your app with others. - Make sure to let your testers know how to give you their feedback. You probably won’t want them to leave feedback in Feedback Hub, because any other customer could see that feedback. Consider including a link for them to send email or provide feedback in some other way. - Any reviews written by people in your private audience will be available for you to view. However, these reviews won’t be published in your app’s Store listing, even after your submission is moved to **Public audience**. You can read reviews written by your private audience by viewing the [Reviews report](../../reviews-report.md), but you can't download this data or use the [Microsoft Store analytics API](/windows/uwp/monetize/access-analytics-data-using-windows-store-services) to programmatically access these reviews. diff --git a/hub/apps/publish/publish-your-app/pwa/price-and-availability.md b/hub/apps/publish/publish-your-app/pwa/price-and-availability.md index 4d1051400b..eb14b9dad9 100644 --- a/hub/apps/publish/publish-your-app/pwa/price-and-availability.md +++ b/hub/apps/publish/publish-your-app/pwa/price-and-availability.md @@ -77,12 +77,6 @@ If you want to offer your app at a reduced price for a limited period of time, y For more info, see [Put apps and add-ons on sale](../../put-apps-and-add-ons-on-sale.md). -## Organizational licensing - -By default, your app may be offered to organizations to purchase in volume. You can indicate whether and how your app can be offered in this section. - -For more info, see [Organizational licensing options](../../organizational-licensing.md). - ## Publish date Previously, the **Publish date** section appeared on this page. This functionality can now be found on the [Submission options](./manage-submission-options.md) page, in the **Publishing hold options** section. diff --git a/hub/apps/publish/publish-your-app/pwa/upload-app-packages.md b/hub/apps/publish/publish-your-app/pwa/upload-app-packages.md index 0b2ae76d92..d7fc014e40 100644 --- a/hub/apps/publish/publish-your-app/pwa/upload-app-packages.md +++ b/hub/apps/publish/publish-your-app/pwa/upload-app-packages.md @@ -18,7 +18,7 @@ The **Packages** page of the [app submission process](./create-app-submission.md To upload packages, drag them into the upload field or click to browse your files. The **Packages** page will let you upload .msix, .msixupload, .msixbundle, .appx, .appxupload, and/or .appxbundle files. -If you have created any [package flights](../../package-flights.md) for your app, you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in this submission. +If you have created any [package flights](../../package-and-distribution.md#package-flights) for your app, you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in this submission. If we detect errors with a package while validating it, we'll display a message to let you know what's wrong. You'll need to remove the package, fix the issue, and then try uploading it again. You may also see warnings to let you know about issues that may cause problems but won't block you from continuing with your submission. @@ -38,7 +38,7 @@ When we detect that you have redundant packages, we'll provide an option to remo If your submission is an update to a previously published app, you'll see a checkbox that says **Roll out update gradually after this submission is published (to Windows 10 or Windows 11 customers only)**. This allows you to choose a percentage of customers who will get the packages from the submission so that you can monitor feedback and analytic data to make sure you’re confident about the update before rolling it out more broadly. You can increase the percentage (or halt the update) any time without having to create a new submission. -For more info, see [Gradual package rollout](../../gradual-package-rollout.md). +For more info, see [Gradual package rollout](../../package-and-distribution.md#gradual-package-rollout). ### Mandatory update diff --git a/hub/apps/publish/publish-your-app/pwa/visibility-options.md b/hub/apps/publish/publish-your-app/pwa/visibility-options.md index b3aa7bcb8d..3a4dca48a8 100644 --- a/hub/apps/publish/publish-your-app/pwa/visibility-options.md +++ b/hub/apps/publish/publish-your-app/pwa/visibility-options.md @@ -27,16 +27,15 @@ By default, your app’s Store listing will be visible to a **Public audience**. ### Private audience -If you want your app’s listing to be visible only to selected people that you specify, choose **Private audience**. With this option, the app will not be discoverable or available to anyone other than people in the group(s) you specify. This option is often used for [beta testing](../../beta-testing-and-targeted-distribution.md), as it lets you distribute your app to testers without anyone else being able to get the app, or even see its Store listing (even if they were able to type in its Store listing URL). +If you want your app’s listing to be visible only to selected people that you specify, choose **Private audience**. With this option, the app will not be discoverable or available to anyone other than people in the group(s) you specify. This option is often used for [beta testing](../../package-and-distribution.md#beta-testing-and-targeted-distribution), as it lets you distribute your app to testers without anyone else being able to get the app, or even see its Store listing (even if they were able to type in its Store listing URL). -When you choose **Private audience**, you’ll need to specify at least one group of people who should get your app. You can choose from an existing [known user group](../../create-known-user-groups.md), or you can select **Create a new group** to define a new group. You’ll need to enter the email addresses associated with the Microsoft account of each person you’d like to include in the group. For more info, see [Create known user groups](../../create-known-user-groups.md). +When you choose **Private audience**, you’ll need to specify at least one group of people who should get your app. You can choose from an existing [known user group](../../create-customer-groups.md#create-known-user-groups), or you can select **Create a new group** to define a new group. You’ll need to enter the email addresses associated with the Microsoft account of each person you’d like to include in the group. For more info, see [Create known user groups](../../create-customer-groups.md#create-known-user-groups). After your submission is published, the people in the group you specify will be able to view the app’s listing and download the app, as long as they are signed in with the Microsoft account associated with the email address that you entered and are running Windows 10, version 1607 or later (including Xbox One). However, people who aren’t in your private audience won’t be able to view the app’s listing or download the app, regardless of what OS version they’re running. You can publish updated submissions to the private audience, which will be distributed to members of those audience in the same way as a regular app update (but still won’t be available to anyone who’s not in of your private audience, unless you change your audience selection). If you plan to make the app available to a public audience at a certain date and time, you can select the box labeled **Make this product public on** when creating your submission. Enter the date and time (in UTC) when you’d like the product to become available to the public. Keep in mind the following: - The date and time that you select will apply to all markets. If you want to customize the release schedule for different markets, don’t use this box. Instead, create a new submission that changes your setting to **Public audience**, then use the [Schedule](./schedule-pricing-changes.md#configure-precise-release-scheduling) options to specify your release timing. -- Entering a date for **Make this product public on** does not apply to the Microsoft Store for Business and/or Microsoft Store for Education. To allow us to offer your app to these customers through organizational licensing, you’ll need to create a new submission with **Public audience** selected (and [organizational licensing](../../organizational-licensing.md) enabled). - After the date and time that you select, all future submissions will use **Public audience**. If you don’t specify a date and time to make your app available to a public audience, you can always do so later by creating a new submission and changing your audience setting from **Private audience** to **Public audience**. When you do so, keep in mind that your app may go through an additional certification process, so be prepared to address any new certification issues that may arise. @@ -47,7 +46,7 @@ Here are some important things to keep in mind when choosing to distribute your - Unless you choose an option in **Discoverability** that prevents it, people in your private audience will be able to find your app by searching within the Microsoft Store app. However, the web listing will not be discoverable via search, even to people in that audience. - You won’t be able to [configure release dates in the Schedule section](./schedule-pricing-changes.md#configure-precise-release-scheduling) of the **Pricing and availability page**, since your app won’t be released to customers outside of your private audience. - Other selections you make will apply to people in this audience. For example, if you choose a price other than **Free**, people in your private audience will have to pay that price in order to acquire the app. -- If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-flights.md) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight. +- If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-and-distribution.md#package-flights) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight. - You can edit the membership of the known user group(s) in your private audience. However, keep in mind that if you remove someone who was in the group and previously downloaded your app, they will still be able to use the app, but they won’t get any updates that you provide (unless you choose **Public audience** at a later date). - Your app won't be available through the Microsoft Store for Business and/or Microsoft Store for Education, regardless of your organizational licensing settings, even to people in your private audience. - While the Store will ensure that your app is only visible and available to people signed in with a Microsoft account that you’ve added to your private audience, we can’t prevent those people from sharing info or screenshots outside of your private audience. When confidentiality is critical, be sure that your private audience only includes people whom you trust not to share details about your app with others. diff --git a/hub/apps/publish/put-apps-and-add-ons-on-sale.md b/hub/apps/publish/put-apps-and-add-ons-on-sale.md index db3e12bd62..658664bcb0 100644 --- a/hub/apps/publish/put-apps-and-add-ons-on-sale.md +++ b/hub/apps/publish/put-apps-and-add-ons-on-sale.md @@ -50,7 +50,7 @@ Sales are scheduled as part of the submission for an app or add-on. If you want > [!IMPORTANT] > If you select **Owners of**, the sale will only be visible to customers on Windows 10, version 1607 or later. - - **Known user group**: The sale will be offered to the people in the [known user group](create-known-user-groups.md) you select. You must already have created the known user group in order for this option to be available. + - **Known user group**: The sale will be offered to the people in the [known user group](create-customer-groups.md#create-known-user-groups) you select. You must already have created the known user group in order for this option to be available. 6. Enter the date and time for the start and end of the sale period. Choose one of the following time zone options: - **UTC**: The time you select will be Universal Coordinated Time (UTC) time, so that the sale occurs at the same time everywhere. - **Local**: The time you select will be the used in each time zone associated with a market. (Note that for markets that include more than one time zone, only one time zone in that market will be used. For the United States, the Eastern time zone is used.) diff --git a/hub/apps/publish/respond-to-customer-feedback.md b/hub/apps/publish/respond-to-customer-feedback.md deleted file mode 100644 index 0e05baed32..0000000000 --- a/hub/apps/publish/respond-to-customer-feedback.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Respond to customer feedback -description: You can respond directly to feedback that your customers leave in Feedback Hub. -ms.date: 10/30/2022 -ms.topic: article -keywords: windows 10, uwp -ms.assetid: 04983b80-2a18-4ace-93d3-e8c33c04bfb9 -ms.localizationpriority: medium ---- -# Respond to customer feedback - -You can use the [Feedback report](feedback-report.md) to review the feedback that your Windows 10 or Windows 11 customers have left about your app in Feedback Hub, and then respond directly to that feedback. You can post your responses in Feedback Hub for everyone to see (either as individual comments, or by updating the status of a piece of feedback and adding a description) to tell customers about new features or bug fixes, or to ask for more specific feedback on how to improve your app. You can also send your response as an email directly to the customer who left the feedback. - -> [!TIP] -> You can encourage customers to leave feedback by using the Feedback API in the [Microsoft Store Services SDK](https://marketplace.visualstudio.com/items?itemName=AdMediator.MicrosoftStoreServicesSDK) to add a control that lets customers directly [launch Feedback Hub from your UWP app](/windows/uwp/monetize/launch-feedback-hub-from-your-app). Keep in mind that any customer who has downloaded your app on a Windows 10 or Windows 11 device that supports Feedback Hub has the ability to leave feedback for it directly through the Feedback Hub app. Because of this, you may see customer feedback in this report, even if you have not specifically requested feedback from within your app. - -To provide a response to any piece of feedback, click the **Respond to feedback** link that appears by the piece of feedback in your **Feedback report**. - -[Partner Center](https://partner.microsoft.com/dashboard) supports three options for responding to customers who provide feedback about your app. Regardless of which option you choose, keep in mind that there is a 1000-character limit for each response. - -## Public comments in Feedback Hub - -By default, the radio button for **Comment** is selected after you click **Respond to feedback**. To post a public response to the customer’s feedback, leave this button selected. Enter your comment in the box, and then click **Submit**. - -The comment you entered will be displayed as a comment in the Feedback Hub, along with the comments submitted by other customers. Your publisher name and app name will be displayed with your comment to identify you as the developer. There is no limit on the number of comments you can write for a piece of feedback, but note that you can’t edit or delete comments after you submit them. The five most recent comments to a piece of feedback will be shown in your **Feedback report** (as well as in Feedback Hub). When there are more than five comments, you can click **Show all comments** to see all of them in Feedback Hub. - - -## Private responses via email - -If you’d prefer not to post a public response, you can check the **Send comment as email** box to send a private response directly to the customer (if they have provided an email address and haven’t opted out of receiving responses via email). When you do so, Microsoft sends an email to the customer on your behalf. The email will contain their original feedback as well as the response you write. - -After you check the **Send comment as email** box, enter your comment and then click **Submit**. Note that you must provide an email address in the **Support contact email** field when using this option. By default, we use the email address that you provided in your account contact info. If you prefer to use a different email address, you can update the **Support contact email** field to use a different one. The customer who receives your response will be able to reply directly to this email address. - - -## Public status updates and descriptions in Feedback Hub - -A third option for a public response is to set the status on a piece of feedback to let your customers that you’re working on the issue, or have fixed it. When you update the status of a piece of feedback, it is displayed along with the feedback in the Feedback Hub. - -To use this option, select the **Update status** radio button. Then select one of the following options: - -- **Investigating**: You’re aware of an issue and you’re looking into it. -- **Working on it**: You’re in the process of fixing a problem or adding a requested feature. -- **Completed**: You’ve published an update to fix the issue or add the requested feature. - -Along with updating the status, you can enter a comment to provide more info, such as an estimate for when you think it a problem will be fixed, or more info about the latest changes. This description will be displayed at the top of the list of comments (and the Feedback report will display the current status and description). - -Using the **Update status** option allows you to change the status whenever you want (along with providing updated descriptions for each status change). Whenever you change the status of a piece of feedback, the status will be updated in Feedback Hub so that customers viewing your response will see the latest status. - - -## Guidelines for responses - -No matter which method you use to respond to a customer’s feedback, you must follow these guidelines for all responses. -- Responses must be no longer than 1000 characters. -- You may not offer any type of compensation, including digital app items, to users for their public comments. -- Don’t include any marketing content or ads in your response. Remember, the person who left feedback is already your customer. -- Don’t promote other apps or services in your response. -- Your response should be directly related to the specific app and feedback. -- Don’t include any profane, aggressive, personal, or malicious comments in your response. Always be polite and keep in mind that happy customers will likely be your app’s biggest promoters. - -> [!NOTE] -> Customers can report a developer to Microsoft if they receive an inappropriate feedback response. They can also opt out of receiving feedback responses by email. - -Your relationship with your customers is your own. Microsoft doesn’t get involved in disputes between developers and customers. However, if you think that the content of a customer’s feedback on your product is inappropriate, please submit a [support ticket](https://developer.microsoft.com/windows/support). diff --git a/hub/apps/publish/respond-to-customer-reviews.md b/hub/apps/publish/respond-to-customer-reviews.md index 7beadef71f..6d1fc007d4 100644 --- a/hub/apps/publish/respond-to-customer-reviews.md +++ b/hub/apps/publish/respond-to-customer-reviews.md @@ -9,8 +9,7 @@ ms.localizationpriority: medium --- # Respond to customer reviews - -You can respond to reviews of your app to let customers know you’re listening to their feedback. With a review response, you can tell customers about the features you’ve added or bugs you’ve fixed based on their comments, or get more specific feedback on how to improve your app. Your responses will be displayed in the Microsoft Store for all Windows 10 and 11 customers to see. You can also choose to send your response by email to the customer (if they haven’t opted out and are using a device running Windows 10, version 1803 or later). +You can respond to reviews of your app to let customers know you’re listening to their feedback. With a review response, you can tell customers about the features you’ve added or bugs you’ve fixed based on their comments, or get more specific feedback on how to improve your app. Your responses will be displayed in the Microsoft Store for all Windows 10 and 11 customers to see. You can also choose to send your response by email to the customer (if they haven’t opted out and are using a device running Windows 10, version 1803 or later). To view your app's reviews and provide responses, select Insights in [Partner Center](https://partner.microsoft.com/dashboard). In the left navigation menu, click **Reviews** found under **Apps and games** to display the [Reviews report](reviews-report.md). Select **Respond to review** to provide your response. @@ -21,7 +20,7 @@ By default, your response will be posted in the Store, directly below the origin If you don't want your response to appear in the Store, and instead want to respond only via email to the customer, uncheck the **Make this response public** box. Note that you will not be able to uncheck this box if the customer has opted out of receiving email responses and/or if they are using a device that is not running Windows 10, version 1803 or later. -## Guidelines for responses +## Guidelines for review responses When responding to a customer's review, you must follow these guidelines. These apply to all responses, whether they are public or not. @@ -46,3 +45,9 @@ Your relationship with your customers is your own. Microsoft doesn’t get invol ## Use customer reviews to improve your app Listening and responding to your customers is only the beginning. Acting on their feedback is also critical. If you make significant improvements, showcase them in the Store with confidence by [creating a new submission](publish-your-app/create-app-submission.md?pivots=store-installer-msix) to update your app. + +## Private responses via email + +If you’d prefer not to post a public response, you can uncheck the **Make this response public** box to send a private response directly to the customer (if they have provided an email address and haven’t opted out of receiving responses via email). When you do so, Microsoft sends an email to the customer on your behalf. The email will contain their original feedback as well as the response you write. + +After you uncheck the **Make this response public** box, enter your comment and then click **Send reply**. Note that you must provide an email address in the **Support contact email** field when using this option. By default, we use the email address that you provided in your account contact info. If you prefer to use a different email address, you can update the **Support contact email** field to use a different one. The customer who receives your response will be able to reply directly to this email address. \ No newline at end of file diff --git a/hub/apps/publish/send-push-notifications-to-your-apps-customers.md b/hub/apps/publish/send-push-notifications-to-your-apps-customers.md index bd48a842df..61c3dc7284 100644 --- a/hub/apps/publish/send-push-notifications-to-your-apps-customers.md +++ b/hub/apps/publish/send-push-notifications-to-your-apps-customers.md @@ -14,8 +14,6 @@ ms.localizationpriority: medium Engaging with your customers at the right time and with the right message is key to your success as an app developer. Notifications can encourage your customers to take an action, such as rating an app, buying an add-on, trying a new feature, or downloading another app (perhaps for free with a [promotional code](generate-promotional-codes.md) that you provide). -[Partner Center](https://partner.microsoft.com/dashboard) provides a data-driven customer engagement platform you can use to send notifications to all of your app's customers, or only targeted to a subset of your app's Windows 10 or Windows 11 customers who meet the criteria you’ve defined in a [customer segment](create-customer-segments.md). You can also create a notification to be sent to customers of more than one of your apps. - > [!IMPORTANT] > These notifications can only be used with UWP apps. @@ -33,7 +31,6 @@ When considering the content of your notifications, keep in mind: At a high-level, you need to do three things to use notifications to engage with your customers. 1. **Register your app to receive push notifications.** You do this by adding a reference to the Microsoft Store Services SDK in your app and then adding a few lines of code that registers a notification channel between Partner Center and your app. We’ll use that channel to deliver your notifications to your customers. For details, see [Configure your app for targeted push notifications](/windows/uwp/monetize/configure-your-app-to-receive-dev-center-notifications). -2. **Decide which customers to target.** You can send your notification to all of your app's customers, or (for notifications created for a single app) to a group of customers called a *segment*, which you can define based on demographic or revenue criteria. For more info, see [Create customer segments](create-customer-segments.md). 3. **Create your notification content and send it out.** For example, you might create a notification that encourages new customers to rate your app, or send a notification promoting a special deal to purchase an add-on. @@ -48,7 +45,7 @@ Follow these steps to create a notification in Partner Center and send it to a p 2. On the **Notifications** page, select **New notification**. 3. In the **Select a template** section, choose the [type of notification](#notification-template-types) you want to send and then click **OK**. 4. On the next page, use the drop-down menu to choose either a **Single app** or **Multiple apps** for which you want to generate a notification. You can only select apps that have been [configured to receive notifications using the Microsoft Store Services SDK](/windows/uwp/monetize/configure-your-app-to-receive-dev-center-notifications). -5. In the **Notification settings** section, choose a **Name** for your notification and, if applicable, choose the **Customer group** to which you want to send the notification. (Notifications sent to multiple apps can only be sent to all customers of those apps.) If you wish to use a segment that you haven't created already, select **Create new customer group**. Note that it takes 24 hours before you can use a new segment for notifications. For more info, see [Create customer segments](create-customer-segments.md). +5. In the **Notification settings** section, choose a **Name** for your notification and, if applicable, choose the **Customer group** to which you want to send the notification. (Notifications sent to multiple apps can only be sent to all customers of those apps.) If you wish to use a segment that you haven't created already, select **Create new customer group**. 6. If you want to specify when to send the notification, clear the **Send notification immediately** checkbox and choose a specific date and time (in UTC for all customers, unless you specify to use each customer's local time zone). 7. If you want the notification to expire at some point, clear the **Notification never expires** checkbox and choose a specific expiration date and time (in UTC). 8. **For notifications to a single app:** If you want to filter the recipients so that your notification is only delivered to people who use certain languages or are in specific time zones, check the **Use filters** checkbox. You can then specify the language and/or time zone options you want to use. diff --git a/hub/apps/publish/store-submission-api.md b/hub/apps/publish/store-submission-api.md index 637f819a35..efe97677c1 100644 --- a/hub/apps/publish/store-submission-api.md +++ b/hub/apps/publish/store-submission-api.md @@ -180,140 +180,6 @@ Fetches metadata in each module (listings, properties or availability) under cur | website | String | | | whatsNew | String | | -**Sample Response** - -```json -{ - "isSuccess": true, - "errors": [{ - "code": "badrequest", - "message": "Error Message 1", - "target": "listings" - }, { - "code": "warning", - "message": "Warning Message 1", - "target": "properties" - }], - "responseData": { - "availability":{ - "markets": ["US"], - "discoverability": "DISCOVERABLE", - "enableInFutureMarkets": true, - "pricing": "PAID", - "freeTrial": "NO_FREE_TRIAL" - }, - "properties":{ - "isPrivacyPolicyRequired": true, - "privacyPolicyUrl": "http://contoso.com", - "website": "http://contoso.com", - "supportContactInfo": "http://contoso.com", - "certificationNotes": "Certification Notes", - "category": "DeveloperTools", - "subcategory": "Database", - "productDeclarations": { - "dependsOnDriversOrNT": false, - "accessibilitySupport": false, - "penAndInkSupport": false - }, - "isSystemFeatureRequired": [ - { - "isRequired": true, - "isRecommended": false, - "hardwareItemType": "Touch" - }, - { - "isRequired": true, - "isRecommended": false, - "hardwareItemType": "Keyboard" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "Mouse" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "Camera" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "NFC_HCE" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "NFC_Proximity" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "Bluetooth_LE" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "Telephony" - }, - { - "isRequired": false, - "isRecommended": false, - "hardwareItemType": "Microphone" - } - ], - "systemRequirementDetails": [ - { - "minimumRequirement": "1GB", - "recommendedRequirement": "4GB", - "hardwareItemType": "Memory" - }, - { - "minimumRequirement": "", - "recommendedRequirement": "", - "hardwareItemType": "DirectX" - }, - { - "minimumRequirement": "", - "recommendedRequirement": "", - "hardwareItemType": "Video_Memory" - }, - { - "minimumRequirement": "", - "recommendedRequirement": "", - "hardwareItemType": "Processor" - }, - { - "minimumRequirement": "", - "recommendedRequirement": "", - "hardwareItemType": "Graphics" - } - ] - }, - "listings":[{ - "language": "en-us", - "description": "Description", - "whatsNew": "What's New", - "productFeatures": ["Feature 1"], - "shortDescription": "Short Description", - "searchTerms": ["Search Ter 1"], - "additionalLicenseTerms": "License Terms", - "copyright": "Copyright Information", - "developedBy": "Developer Details", - "sortTitle": "Product 101", - "requirements": [ - { - "minimumHardware": "Pentium4", - "recommendedHardware": "Corei9" - } - ], - "contactInfo": "contactus@contoso.com" - }], - "listingLanguages": [{"language":"en-us", "isComplete": true}] - } -} -``` - ### Update Current Draft Submission Metadata API Updates metadata in each Module under draft submission. The API checks @@ -396,252 +262,6 @@ In the case of Patch Module Update API – only fields which are to be updated n | listingsToAdd | Array of strings | See list of languages below | | listingsToRemove | Array of strings | See list of languages below | -**Markets** - -| Market | Abbreviation | -|--------|--------------| -| Afghanistan | AF | -| Albania | AL | -| Algeria | DZ | -| American Samoa | AS | -| Andorra | AD | -| Angola | AO | -| Anguilla | AI | -| Antarctica | AQ | -| Antigua and Barbuda | AG | -| Argentina | AR | -| Armenia | AM | -| Aruba | AW | -| Australia | AU | -| Austria | AT | -| Azerbaijan | AZ | -| Bahamas | BS | -| Bahrain | BH | -| Bangladesh | BD | -| Barbados | BB | -| Belarus | BY | -| Belgium | BE | -| Belize | BZ | -| Benin | BJ | -| Bermuda | BM | -| Bhutan | BT | -| Bolivarian Republic of Venezuela | VE | -| Bolivia | BO | -| Bonaire | BQ | -| Bosnia and Herzegovina | BA | -| Botswana | BW | -| Bouvet Island | BV | -| Brazil | BR | -| British Indian Ocean Territory | IO | -| British Virgin Islands | VG | -| Brunei | BN | -| Bulgaria | BG | -| Burkina Faso | BF | -| Burundi | BI | -| Cambodia | KH | -| Cameroon | CM | -| Canada | CA | -| Cabo Verde | CV | -| Cayman Islands | KY | -| Central African Republic | CF | -| Chad | TD | -| Chile | CL | -| China | CN | -| Christmas Island | CX | -| Cocos (Keeling) Islands | CC | -| Colombia | CO | -| Comoros | KM | -| Congo | CG | -| Congo (DRC) | CD | -| Cook Islands | CK | -| Costa Rica | CR | -| Croatia | HR | -| Curaçao | CW | -| Cyprus | CY | -| Czech Republic | CZ | -| Côte d'Ivoire | CI | -| Denmark | DK | -| Djibouti | DJ | -| Dominica | DM | -| Dominican Republic | DO | -| Ecuador | EC | -| Egypt | EG | -| El Salvador | SV | -| Equatorial Guinea | GQ | -| Eritrea | ER | -| Estonia | EE | -| Ethiopia | ET | -| Falkland Islands | FK | -| Faroe Islands | FO | -| Fiji | FJ | -| Finland | FI | -| France | FR | -| French Guiana | GF | -| French Polynesia | PF | -| French Southern and Antarctic Lands | TF | -| Gabon | GA | -| Gambia | GM | -| Georgia | GE | -| Germany | DE | -| Ghana | GH | -| Gibraltar | GI | -| Greece | GR | -| Greenland | GL | -| Grenada | GD | -| Guadeloupe | GP | -| Guam | GU | -| Guatemala | GT | -| Guernsey | GG | -| Guinea | GN | -| Guinea-Bissau | GW | -| Guyana | GY | -| Haiti | HT | -| Heard Island and McDonald Islands | HM | -| Vatican City | VA | -| Honduras | HN | -| Hong Kong SAR | HK | -| Hungary | HU | -| Iceland | IS | -| India | IN | -| Indonesia | ID | -| Iraq | IQ | -| Ireland | IE | -| Israel | IL | -| Italy | IT | -| Jamaica | JM | -| Japan | JP | -| Jersey | JE | -| Jordan | JO | -| Kazakhstan | KZ | -| Kenya | KE | -| Kiribati | KI | -| Korea | KR | -| Kuwait | KW | -| Kyrgyzstan | KG | -| Laos | LA | -| Latvia | LV | -| Lebanon | LB | -| Lesotho | LS | -| Liberia | LR | -| Libya | LY | -| Liechtenstein | LI | -| Lithuania | LT | -| Luxembourg | LU | -| Macao SAR | MO | -| North Macedonia | MK | -| Madagascar | MG | -| Malawi | MW | -| Malaysia | MY | -| Maldives | MV | -| Mali | ML | -| Malta | MT | -| Isle of Man | IM | -| Marshall Islands | MH | -| Martinique | MQ | -| Mauritania | MR | -| Mauritius | MU | -| Mayotte | YT | -| Mexico | MX | -| Micronesia | FM | -| Moldova | MD | -| Monaco | MC | -| Mongolia | MN | -| Montenegr - ME | -| Montserrat | MS | -| Morocco | MA | -| Mozambique | MZ | -| Myanmar | MM | -| Namibia | NA | -| Nauru | NR | -| Nepal | NP | -| Netherlands | NL | -| New Caledonia | NC | -| New Zealand | NZ | -| Nicaragua | NI | -| Niger | NE | -| Nigeria | NG | -| Niue | NU | -| Norfolk Island | NF | -| Northern Mariana Islands | MP | -| Norway | NO | -| Oman | OM | -| Pakistan | PK | -| Palau | PW | -| Palestinian Authority | PS | -| Panama | PA | -| Papua New Guinea | PG | -| Paraguay | PY | -| Peru | PE | -| Philippines | PH | -| Pitcairn Islands | PN | -| Poland | PL | -| Portugal | PT | -| Qatar | QA | -| Reunion | RE | -| Romania | RO | -| Russia | RU | -| Rwanda | RW | -| Saint Barthélemy | BL | -| Saint Helena, Ascension and Tristan da Cunha | SH | -| Saint Kitts and Nevis | KN | -| Saint Lucia | LC | -| Saint Martin (French Part) | MF | -| Saint Pierre and Miquelon | PM | -| Saint Vincent and the Grenadines | VC | -| Samoa | WS | -| San Marino | SM | -| Saudi Arabia | SA | -| Senegal | SN | -| Serbia | RS | -| Seychelles | SC | -| Sierra Leone | SL | -| Singapore | SG | -| Sint Maarten (Dutch Part) | SX | -| Slovakia | SK | -| Slovenia | SI | -| Solomon Islands | SB | -| Somalia | SO | -| South Africa | ZA | -| South Georgia and the South Sandwich Islands | GS | -| Spain | ES | -| Sri Lanka | LK | -| Suriname | SR | -| Svalbard and Jan Mayen | SJ | -| Swaziland | SZ | -| Sweden | SE | -| Switzerland | CH | -| São Tomé and Príncipe | ST | -| Taiwan | TW | -| Tajikistan | TJ | -| Tanzania | TZ | -| Thailand | TH | -| Timor-Leste | TL | -| Tog - TG | -| Tokelau | TK | -| Tonga | TO | -| Trinidad and Tobag - TT | -| Tunisia | TN | -| Türkiye | TR | -| Turkmenistan | TM | -| Turks and Caicos Islands | TC | -| Tuvalu | TV | -| U.S. Minor Outlying Islands | UM | -| U.S. Virgin Islands | VI | -| Uganda | UG | -| Ukraine | UA | -| United Arab Emirates | AE | -| United Kingdom | GB | -| United States | US | -| Uruguay | UY | -| Uzbekistan | UZ | -| Vanuatu | VU | -| Vietnam | VN | -| Wallis and Futuna | WF | -| Yemen | YE | -| Zambia | ZM | -| Zimbabwe | ZW | -| Åland Islands | AX | - **Categories and Sub-categories** | Category | Subcategories | diff --git a/hub/apps/publish/toc.yml b/hub/apps/publish/toc.yml index fe291eae3e..7901c2c395 100644 --- a/hub/apps/publish/toc.yml +++ b/hub/apps/publish/toc.yml @@ -257,23 +257,13 @@ items: href: product-page-experiments.md - name: Use Microsoft Store Web Installer to distribute apps href: ../distribute-through-store/how-to-use-store-web-installer-for-distribution.md - - name: App management and services - href: app-management-and-services.md + - name: Product management + href: product-management.md items: - name: View product identity details href: view-app-identity-details.md - - name: Generate preinstall packages for OEMs - href: generate-preinstall-packages-for-oems.md - - name: Organizational Licensing options - href: organizational-licensing.md - - name: Package Flights - href: package-flights.md - - name: Gradual Package Rollout - href: gradual-package-rollout.md - - name: Beta testing and targeted distribution - href: beta-testing-and-targeted-distribution.md - - name: Distribute LOB apps to enterprises - href: distribute-lob-apps-to-enterprises.md + - name: Package and distribution + href: package-and-distribution.md - name: Attract and promote href: attract-customers-and-promote-your-apps.md items: @@ -296,17 +286,8 @@ items: items: - name: Create customer groups href: create-customer-groups.md - items: - - name: Create customer segments - href: create-customer-segments.md - - name: Create known user groups - href: create-known-user-groups.md - name: Respond to customer reviews href: respond-to-customer-reviews.md - - name: Respond to customer feedback - href: respond-to-customer-feedback.md - - name: Send notifications to your app's customers - href: send-push-notifications-to-your-apps-customers.md - name: Use targeted offers href: use-targeted-offers-to-maximize-engagement-and-conversions.md - name: Microsoft Store Developer CLI (preview)