Update Leverage developer tools section #5467
Open
+386
−1,154
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Learn Build status updates of commit 6ba659f:
|
|
Learn Build status updates of commit e8ccb50:
|
|
Learn Build status updates of commit 346809f:
|
@microsoft-github-policy-service agree company="southworks" |
|
@FedericoBernal : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
apps/subsvc
Change sent to author
windows-app-sdk/svc
labels
|
Learn Build status updates of commit 860e1cd:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| hub/apps/publish/send-push-notifications-to-your-apps-customers.md | Details | ||
| .openpublishing.redirection.json | ✅Succeeded | ||
| hub/apps/publish/app-management-and-services.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/beta-testing-and-targeted-distribution.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-a-custom-app-promotion-campaign.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-groups.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-segments.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-known-user-groups.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/distribute-lob-apps-to-enterprises.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/engage-with-your-customers.md | ✅Succeeded | ||
| hub/apps/publish/generate-preinstall-packages-for-oems.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-promotional-codes.md | ✅Succeeded | ||
| hub/apps/publish/gradual-package-rollout.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/organizational-licensing.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/package-and-distribution.md | ✅Succeeded | ||
| hub/apps/publish/package-flights.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md | ✅Succeeded | ||
| hub/apps/publish/product-management.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/visibility-options.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/price-and-availability.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/upload-app-packages.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/visibility-options.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/pwa/price-and-availability.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/pwa/upload-app-packages.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/pwa/visibility-options.md | ✅Succeeded |
This comment lists only the first 25 files in the pull request.
hub/apps/publish/send-push-notifications-to-your-apps-customers.md
- Line 51, Column 467: [Warning: file-not-found - See documentation]
Invalid file link: 'create-customer-segments.md'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
| @@ -15,5 +15,93 @@ To view and create customer groups, expand **Engage** in the left navigation men | |||
|
|
|||
| Currently, two types of customer groups are supported: | |||
|
|
|||
| - **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). | |||
| - **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). | |||
There was a problem hiding this comment.
Can we remove link to send-push-notifications-to-your-app-customers page? The notifications feature is already deprecated. We can link this directly to Microsoft Azure notification hub
| 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. |
There was a problem hiding this comment.
Same comment as above. Let's not add a link to deprecated feature - Notifications page mentions that the feature is deprecated
| - **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). | ||
| - **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). | ||
|
|
||
| ## Create customer segments |
There was a problem hiding this comment.
Have we validated if this feature is available in Partner Center? I checked and couldn't find this. Can we please confirm
There was a problem hiding this comment.
couldn't find it so I removed the section
|
|
||
| ## 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 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. |
There was a problem hiding this comment.
Same comment, we shouldn't include link to push notifications page since it is deprecated
| @@ -75,7 +75,7 @@ Run experiments in your apps to measure the effectiveness of feature changes bef | |||
|
|
|||
| 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) | |||
| [Get feedback](respond-to-customer-reviews.md#respond-to-customer-feedback) | |||
There was a problem hiding this comment.
Feedback report is deprecated - https://learn.microsoft.com/en-us/partner-center/insights/feedback-report which means responding to feedback is not supported. Can we remove this section completely?
| @@ -42,7 +42,7 @@ Note that some permissions cannot be set for add-ons. This is either because the | |||
| | ---------- | ---------- | ---------- |----------|----------| | |||
| | **Promotional codes** | Can view <a href="..\generate-promotional-codes.md">promotional code</a> orders and usage info for the product and its add-ons, and can view usage info. | Can view, manage, and create <a href="..\generate-promotional-codes.md">promotional code</a> 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 <a href="..\use-targeted-offers-to-maximize-engagement-and-conversions.md">targeted offers</a> for the product. | Can view, manage and create <a href="..\use-targeted-offers-to-maximize-engagement-and-conversions.md">targeted offers</a> for the product. | N/A | N/A | | |||
| | **Contact customer** | Can view <a href="..\respond-to-customer-feedback.md">responses to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">responses to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also view <a href="..\send-push-notifications-to-your-apps-customers.md">targeted notifications</a> that have been created for the product. | Can <a href="..\respond-to-customer-feedback.md">respond to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">respond to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also <a href="..\send-push-notifications-to-your-apps-customers.md">create and send targeted notifications</a> for the product. | N/A | N/A | | |||
| | **Contact customer** | Can view <a href="..\respond-to-customer-reviews.md">responses to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">responses to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also view <a href="..\send-push-notifications-to-your-apps-customers.md">targeted notifications</a> that have been created for the product. | Can <a href="..\respond-to-customer-reviews.md">respond to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">respond to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also <a href="..\send-push-notifications-to-your-apps-customers.md">create and send targeted notifications</a> for the product. | N/A | N/A | | |||
There was a problem hiding this comment.
Please remove sections on push notifications and customer segments since these are not available in Partner Center
|
Learn Build status updates of commit fda71d2:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| hub/apps/publish/send-push-notifications-to-your-apps-customers.md | Details | ||
| .openpublishing.redirection.json | ✅Succeeded | ||
| hub/apps/publish/app-management-and-services.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/beta-testing-and-targeted-distribution.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-a-custom-app-promotion-campaign.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-groups.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-segments.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-known-user-groups.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/distribute-lob-apps-to-enterprises.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/engage-with-your-customers.md | ✅Succeeded | ||
| hub/apps/publish/generate-preinstall-packages-for-oems.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-promotional-codes.md | ✅Succeeded | ||
| hub/apps/publish/gradual-package-rollout.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/organizational-licensing.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/package-and-distribution.md | ✅Succeeded | ||
| hub/apps/publish/package-flights.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md | ✅Succeeded | ||
| hub/apps/publish/partner-center/assign-roles-to-account-users.md | ✅Succeeded | ||
| hub/apps/publish/product-management.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/visibility-options.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/price-and-availability.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/upload-app-packages.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/visibility-options.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/pwa/price-and-availability.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/pwa/upload-app-packages.md | ✅Succeeded |
This comment lists only the first 25 files in the pull request.
hub/apps/publish/send-push-notifications-to-your-apps-customers.md
- Line 51, Column 467: [Warning: file-not-found - See documentation]
Invalid file link: 'create-customer-segments.md'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
| @@ -42,7 +42,7 @@ Note that some permissions cannot be set for add-ons. This is either because the | |||
| | ---------- | ---------- | ---------- |----------|----------| | |||
| | **Promotional codes** | Can view <a href="..\generate-promotional-codes.md">promotional code</a> orders and usage info for the product and its add-ons, and can view usage info. | Can view, manage, and create <a href="..\generate-promotional-codes.md">promotional code</a> 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 <a href="..\use-targeted-offers-to-maximize-engagement-and-conversions.md">targeted offers</a> for the product. | Can view, manage and create <a href="..\use-targeted-offers-to-maximize-engagement-and-conversions.md">targeted offers</a> for the product. | N/A | N/A | | |||
| | **Contact customer** | Can view <a href="..\respond-to-customer-feedback.md">responses to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">responses to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also view <a href="..\send-push-notifications-to-your-apps-customers.md">targeted notifications</a> that have been created for the product. | Can <a href="..\respond-to-customer-feedback.md">respond to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">respond to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also <a href="..\send-push-notifications-to-your-apps-customers.md">create and send targeted notifications</a> for the product. | N/A | N/A | | |||
| | **Contact customer** | Can view <a href="..\respond-to-customer-reviews.md">responses to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">responses to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also view <a href="..\send-push-notifications-to-your-apps-customers.md">targeted notifications</a> that have been created for the product. | Can <a href="..\respond-to-customer-reviews.md">respond to customer feedback</a> and <a href="..\respond-to-customer-reviews.md">respond to customer reviews</a>, as long as the **Customer feedback** permission has been granted as well. Can also <a href="..\send-push-notifications-to-your-apps-customers.md">create and send targeted notifications</a> for the product. | N/A | N/A | | |||
| | **Experimentation** | Can view <a href="\windows\uwp\monetize\run-app-experiments-with-a-b-testing">experiments (A/B testing)</a> and view experimentation data for the product. | Can create, manage, and view <a href="\windows\uwp\monetize\run-app-experiments-with-a-b-testing">experiments (A/B testing)</a> for the product, and view experimentation data. | N/A | N/A | | |||
There was a problem hiding this comment.
Experimentation is also not supported anymore, can you please remove this?
| 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. | ||
|
|
There was a problem hiding this comment.
Same as above, please remove reference to a/b testing
|
|
||
| ## 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). | ||
| > 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-groups.md). For more info, see [Send notifications to your app's customers](send-push-notifications-to-your-apps-customers.md). |
There was a problem hiding this comment.
Please remove reference to notification and customer segment
|
|
||
| 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 (and [organizational licensing](../../package-and-distribution.md#organizational-licensing) enabled). |
There was a problem hiding this comment.
Microsoft store for business or education is deprecated. can we remove any reference to it?
| ms.assetid: 96AA2108-E793-4DD0-8CDA-0D115423C68D | ||
| ms.date: 10/30/2022 | ||
| ms.topic: article | ||
| keywords: windows 10, uwp, responding, responses, review | ||
| ms.localizationpriority: medium | ||
| --- | ||
| # Respond to customer reviews | ||
| # Respond to customer reviews and feedback |
There was a problem hiding this comment.
Let's remove the section on responding to customer feedback
| @@ -9,14 +9,14 @@ 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*. | |||
| In addition to running [ad campaign](/windows/uwp/monetize/index) within Windows apps, you can promote your app through other channels, such as third-party marketing providers or social media links. These are called custom campaigns. | |||
There was a problem hiding this comment.
Ad campaigns inside Windows app is not supported anymore. Can we remove this redirection link
| @@ -47,7 +47,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. | |||
There was a problem hiding this comment.
Please remove reference to store for business or education
|
|
||
| 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 (and [organizational licensing](../../package-and-distribution.md#organizational-licensing) enabled). |
There was a problem hiding this comment.
Same comment as above
| @@ -1,14 +1,15 @@ | |||
| --- | |||
| description: You can respond directly to reviews of your app to let customers know you’re listening to their feedback. | |||
| title: Respond to customer reviews | |||
| title: Respond to customer reviews and feedback | |||
There was a problem hiding this comment.
Please remove any reference to responding to customer feedback
|
|
||
| ## 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. |
There was a problem hiding this comment.
Have we checked if this feature is supported where developer can respond to a user thru private response?
There was a problem hiding this comment.
this feature is supported but it has changed a bit so I updated the document.
|
Learn Build status updates of commit 0b84eeb:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| hub/apps/publish/engage-with-your-customers.md | Details | ||
| hub/apps/publish/package-and-distribution.md | Details | ||
| hub/apps/publish/publish-your-app/add-on/visibility-options.md | Details | ||
| hub/apps/publish/publish-your-app/msix/price-and-availability.md | Details | ||
| hub/apps/publish/publish-your-app/pwa/price-and-availability.md | Details | ||
| hub/apps/publish/send-push-notifications-to-your-apps-customers.md | Details | ||
| hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md | 💡Suggestion | Details | |
| .openpublishing.redirection.json | ✅Succeeded | ||
| hub/apps/publish/app-management-and-services.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/beta-testing-and-targeted-distribution.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-a-custom-app-promotion-campaign.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-groups.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-segments.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-known-user-groups.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/distribute-lob-apps-to-enterprises.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-preinstall-packages-for-oems.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-promotional-codes.md | ✅Succeeded | ||
| hub/apps/publish/gradual-package-rollout.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/organizational-licensing.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/package-flights.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/partner-center/assign-roles-to-account-users.md | ✅Succeeded | ||
| hub/apps/publish/product-management.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/upload-app-packages.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/visibility-options.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/pwa/upload-app-packages.md | ✅Succeeded |
This comment lists only the first 25 files in the pull request.
hub/apps/publish/engage-with-your-customers.md
- Line 24, Column 1: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'.
hub/apps/publish/package-and-distribution.md
- Line 205, Column 238: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/add-on/visibility-options.md
- Line 37, Column 305: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/msix/price-and-availability.md
- Line 84, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/pwa/price-and-availability.md
- Line 84, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/send-push-notifications-to-your-apps-customers.md
- Line 17, Column 297: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'. - Line 36, Column 279: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'. - Line 51, Column 467: [Warning: file-not-found - See documentation]
Invalid file link: 'create-customer-segments.md'.
hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md
- Line 41, Column 1: [Suggestion: table-syntax-invalid - See documentation]
Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 543ccf6:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| hub/apps/publish/engage-with-your-customers.md | Details | ||
| hub/apps/publish/package-and-distribution.md | Details | ||
| hub/apps/publish/publish-your-app/add-on/visibility-options.md | Details | ||
| hub/apps/publish/publish-your-app/msix/price-and-availability.md | Details | ||
| hub/apps/publish/publish-your-app/pwa/price-and-availability.md | Details | ||
| hub/apps/publish/send-push-notifications-to-your-apps-customers.md | Details | ||
| hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md | 💡Suggestion | Details | |
| .openpublishing.redirection.json | ✅Succeeded | ||
| hub/apps/publish/app-management-and-services.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/beta-testing-and-targeted-distribution.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-a-custom-app-promotion-campaign.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-groups.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-segments.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-known-user-groups.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/distribute-lob-apps-to-enterprises.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-preinstall-packages-for-oems.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-promotional-codes.md | ✅Succeeded | ||
| hub/apps/publish/gradual-package-rollout.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/organizational-licensing.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/package-flights.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/partner-center/assign-roles-to-account-users.md | ✅Succeeded | ||
| hub/apps/publish/product-management.md | ✅Succeeded | ||
| hub/apps/publish/product-page-experiments.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/images/analyse-product-page-experiment-results.png | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/images/configure-product-page-experiment.png | ✅Succeeded |
This comment lists only the first 25 files in the pull request.
hub/apps/publish/engage-with-your-customers.md
- Line 24, Column 1: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'.
hub/apps/publish/package-and-distribution.md
- Line 205, Column 238: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/add-on/visibility-options.md
- Line 37, Column 305: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/msix/price-and-availability.md
- Line 84, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/pwa/price-and-availability.md
- Line 84, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/send-push-notifications-to-your-apps-customers.md
- Line 17, Column 297: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'. - Line 36, Column 279: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'. - Line 51, Column 467: [Warning: file-not-found - See documentation]
Invalid file link: 'create-customer-segments.md'.
hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md
- Line 41, Column 1: [Suggestion: table-syntax-invalid - See documentation]
Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 66d74d4:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| hub/apps/publish/engage-with-your-customers.md | Details | ||
| hub/apps/publish/package-and-distribution.md | Details | ||
| hub/apps/publish/publish-your-app/add-on/visibility-options.md | Details | ||
| hub/apps/publish/publish-your-app/msix/price-and-availability.md | Details | ||
| hub/apps/publish/publish-your-app/pwa/price-and-availability.md | Details | ||
| hub/apps/publish/send-push-notifications-to-your-apps-customers.md | Details | ||
| hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md | 💡Suggestion | Details | |
| .openpublishing.redirection.json | ✅Succeeded | ||
| hub/apps/publish/app-management-and-services.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/beta-testing-and-targeted-distribution.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-a-custom-app-promotion-campaign.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-groups.md | ✅Succeeded | ||
| hub/apps/publish/create-customer-segments.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/create-known-user-groups.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/distribute-lob-apps-to-enterprises.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-preinstall-packages-for-oems.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/generate-promotional-codes.md | ✅Succeeded | ||
| hub/apps/publish/gradual-package-rollout.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/msstore-dev-cli/overview.md | ✅Succeeded | ||
| hub/apps/publish/organizational-licensing.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/package-flights.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/partner-center/assign-roles-to-account-users.md | ✅Succeeded | ||
| hub/apps/publish/product-management.md | ✅Succeeded | ||
| hub/apps/publish/product-page-experiments.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/images/analyse-product-page-experiment-results.png | ✅Succeeded |
This comment lists only the first 25 files in the pull request.
hub/apps/publish/engage-with-your-customers.md
- Line 24, Column 1: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'.
hub/apps/publish/package-and-distribution.md
- Line 205, Column 238: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/add-on/visibility-options.md
- Line 37, Column 305: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/msix/price-and-availability.md
- Line 84, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/publish-your-app/pwa/price-and-availability.md
- Line 84, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#organizational-licensing' in 'apps/publish/package-and-distribution.md'.
hub/apps/publish/send-push-notifications-to-your-apps-customers.md
- Line 17, Column 297: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'. - Line 36, Column 279: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#create-customer-segments' in 'apps/publish/create-customer-groups.md'. - Line 51, Column 467: [Warning: file-not-found - See documentation]
Invalid file link: 'create-customer-segments.md'.
hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md
- Line 41, Column 1: [Suggestion: table-syntax-invalid - See documentation]
Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 1bf5548: 💡 Validation status: suggestions
This comment lists only the first 25 files in the pull request. hub/apps/publish/partner-center/assign-product-level-custom-permissions-to-account-users.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
PRMerger Results
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes included
Note: Changes are still pending in Store CLI section as well as some screenshot updates in Product page experiments.